Update a DICE event and message ticket holders

1. Sign in to MIO, open the event and edit the times, venue or line-up; DICE's terms ask promoters to make scheduling, venue and line-up changes in MIO without undue delay.
2. Open MIO Connect and write one message to the fans attending, limited to what they need to know about this event.
3. For a new date, reschedule the event: DICE then marks it on the tickets, emails all ticket holders and updates the app once the new date is confirmed.
4. Expect refund requests after a reschedule, because DICE fans who cannot make the new date can ask for their money back, and the promoter funds those refunds.
5. Under time pressure the edit and the message drift apart: the app says 21:00 while the message says 20:00, or a line-up note goes out with a plug for next month's show, which MIO Connect does not allow.

Doors for Club Night moved from 22:00 to 20:00. Update the event and tell everyone with a ticket that their ticket is still valid.

1. 01

   Tell a change from a reschedule

   get_event shows the current date, times, venue and line-up. A move to another day is a reschedule with refund consequences, so the agent stops and asks you before touching the date. Same-day time, room or line-up changes go ahead.

2. 02

   Edit only what changed

   update_event receives just the changed fields, for example start moved from 22:00 to 20:00 in the venue's time zone. The agent reads the event back and compares it with your request before any message is drafted.

3. 03

   Write one operational message

   The draft states the change, the new time or place and that tickets stay valid. The agent cuts anything MIO Connect forbids, such as discounts, other events, merch, surveys or prompts to update marketing preferences, and tells you what it cut.

4. 04

   Send once, with your OK

   message_attendees waits for your confirmation and cannot be unsent. After a timeout the agent checks the result instead of sending again, so no fan gets the same notice twice.

5. 05

   Report for the venue

   The run ends with what changed, the exact message and the number of ticket holders it reached, ready to forward to the venue manager and the door team.

Club Night, 14 Nov, The Warehouse.
Changed: start 22:00 to 20:00. End 04:00 unchanged. Read back and matched.
Message sent with MIO Connect after your OK to 182 ticket holders: "Doors now open at 20:00. Your ticket is still valid."
Cut from your draft: "Grab early bird for our NYE party" (MIO Connect is for event information only).
Date unchanged, so DICE sends no reschedule email.

• DICE's MIO user guidelines limit MIO Connect to operational messages about the event the fan is attending, and forbid discounts, vouchers, other events, surveys and requests to update marketing preferences.
• When a DICE event is officially rescheduled, the fan's ticket stays valid for the new date, DICE emails all ticket holders, and fans who cannot attend can request a refund.
• Under DICE's terms the promoter pays the refunds due after a cancellation or reschedule; DICE sets them off against sales proceeds or asks for the money within 48 hours.
• When a DICE event is cancelled, fans are refunded automatically to the original card once the organiser returns the ticket proceeds, and that refund cannot be reversed.
• DICE's terms make the promoter reimburse any costs DICE incurs in advertising or notifying fans of changes to an event.

update_event and message_attendees ask for your OK by default. To run it on a schedule without you, switch confirmation off for those tools in your dashboard.

Sources: Make It On DICE: User Guidelines · DICE Self Sign-Up Terms and Conditions USA · DICE Help: What to do if an event is cancelled, postponed or rescheduled · DICE Help: When are you entitled to a refund?

curl https://cotlet.dev/api/v1/dice/message_attendees \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_id":"ev_48213","message":"Doors now open at 20:00. Your ticket is still valid."}'

{
  "event_id": "ev_48213",
  "status": "sent",
  "recipients": 182,
  "sent_at": "2026-11-14T12:00:00+00:00"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is dice_message_attendees. Example data.

• Get a weekly DICE ticket sales report with returns and transfers
• Create a DICE event draft with ticket types
• Add a new DICE ticket release when early bird sells out
• DICE API and MCP server: every tool
• All use cases