---
title: "Event Staff Messaging and Incident Reporting Software"
description: "You email or text just the crew who need to know and see who got it. Anyone on your team logs an incident in seconds, and serious ones reach your safety lead."
canonical: "https://www.ticketfairy.com/event-operating-system/show-day/team-messages-and-incidents"
---

[Show day](https://www.ticketfairy.com/event-operating-system/show-day)

# Keep your crew informed and every incident on record

You message the right teams from a template or a draft by Fai, your AI teammate, and serious incidents reach your safety lead fast.

A small team that works like a big one.

  [Get started free](https://manage.ticketfairy.com/registration) [Book a demo](https://www.ticketfairy.com/event-ticketing/book-a-demo)

- No credit card required
- The [Event Operating System](https://www.ticketfairy.com/event-operating-system) on every plan, Free included
- Unlimited events with no monthly fee

     ![Ticket Fairy Messages section with a scheduled weather hold and a sent gate change, each showing who it went to and how many it reached](https://www.ticketfairy.com/embeds/posters/marketing-event-messages--messages.png)

- The right crew told in minutes
- Serious incidents reach your safety lead at once
- Who was told and what was done, recorded

## Send your message only to the people who need to know

You tick the groups a message is for: departments, people on the rota, all crew, volunteers, performers' teams, traders, press, sponsors or the people who answered one of your forms.

You can narrow each group by status, role, day, team or shift, so a gate change goes to Saturday's gate stewards and nobody else. A person in two groups gets the message once.

The teams working on your event are already in the dashboard, so you have no list to export and no group chat to keep up to date. You can narrow the people who answered a form by your decision or by one of their answers, such as the volunteer applicants you accepted, or everyone who chose the bar team.

- **Who gets it**: all the teams working on your event, ready to tick
- **Narrow each group**: by status, role, day, team or shift
- **People who answered a form**: narrowed by your decision or by one answer

- [Message the crew, volunteers and traders working on your event](https://www.ticketfairy.com/guides/message-the-people-working-on-your-event)

     ![Ticket Fairy Message people dialog with the groups to choose from, email or text message, quick show-day messages, a box to ask Fai for a draft and the message fields](https://www.ticketfairy.com/embeds/posters/marketing-event-messages--message-people.png)

## Get the message out fast with templates and Fai's drafts

You can start from a quick show-day message such as Weather hold, Gate change, Set time change, Running late or All clear, or tell Fai what you want to say and she drafts it in your brand's voice.

You add each person's first name, shift time, team, role or stage so the message feels personal, and send it by email, by text or both.

In the middle of a show, you start from a template in the words event teams use, with gaps marked for the gate, the time or the stage. Fai's draft gives you a starting point you can change before anything goes. When you tick a form's group, you can drop in each person's answer to one of its questions, such as the day they arrive.

When a set time on the run of show moves by a quarter of an hour or more, Fai suggests an email to the affected teams on the event's Today page. Nothing goes until someone on your team approves it.

- **Quick show-day messages**: weather hold, gate change, running late and more
- **Ask Fai for a draft**: you say what you need and check her words
- **Each person's details**: first name, shift time, team, role or stage
- **Email and text**: one channel or both in the same message

## Check who gets it, then send now or later

Before anything goes, you see who gets it by email and by text, and who is left out and why, such as a missing mobile number or a number that replied STOP.

You send it straight away or schedule it in the event's time zone, and can cancel a scheduled message any time before it goes. On show day, you also find Message people at the top of the show-day view.

If the group changes between your check and your send, such as new volunteers joining the rota, you see the new count and check again. The number you agreed to is the number that goes. When you schedule the next morning's briefing the night before, your crew get it at breakfast while you sleep.

- **Check before sending**: each person who gets it, by channel
- **Send later**: at the time you choose, in the event's time zone
- **Cancel**: a scheduled message, until it goes

## See who got each message and resend to the rest

Each message shows each person as sent, opened, on the way or not sent, and you can narrow it to the people who did not get it.

Once it has finished sending, you can send it again to only those people. Each crew member's page shows all the messages you sent them about the event.

When a steward says they never heard about the gate change, you can see what you sent them, when, and whether it reached them. Email replies go to your brand's email address, so a trader's reply reaches the people who can answer it.

- **Delivery**: sent, opened, on the way or not sent for each person
- **Send again**: only to the people who did not get it
- **Messages to one person**: everything you sent them about the event

      ![Ticket Fairy message panel showing who a gate change reached, who opened it and who it did not reach](https://www.ticketfairy.com/embeds/posters/marketing-event-messages--delivery.png)

## Email your rota and lists to the team on schedule

You can send the rota, run of show, advancing status, rooming list or pickups to the right people every day or every week, at the day and time you choose.

Each person gets an email with a link and signs in to download the file, made from the list as it is at that moment. You can make a file now whenever you need one, and pause or stop a schedule at any time.

The rota goes to the security lead, the rooming list to the travel team and the pickups to the transport manager, with no Monday spreadsheet run. Lists that hold people's names go only to owners and admins, and each file and download is recorded. If nobody you chose can still see a list, Ticket Fairy pauses the schedule and tells the owners and admins.

- **Send regularly**: every day or every week, at your time
- **Saved lists**: rota, run of show, advancing, rooming list and pickups
- **Signed-in downloads**: a link to the file, never an attachment

- [Send your event lists to your team on a schedule](https://www.ticketfairy.com/guides/send-your-event-lists-to-your-team-on-a-schedule)

     ![Ticket Fairy dialog to send the rota regularly, with how often, the day and time, who gets the email, the schedule already set and the latest file](https://www.ticketfairy.com/embeds/posters/marketing-event-logistics--send-regularly.png)

## Log an incident in seconds

Once you enter what happened, where, and how serious it is, the report is in. The time is now and the reporter is you unless you change them, and you can pick the spot on your site map.

The people involved go under more details, kept apart from what happened, where only your safety team can see them. Anyone on your event's team can also ask Fai from their phone to log an incident or add an update, and she waits for their yes first.

Each level of seriousness has a plain description, so a steward knows that danger to life is critical and a minor knock noted for the record is low. When you mark a report sensitive, only your safety team and the person who reported it see it in full. Everyone else sees only that something happened, when and how serious it is. Medical, safeguarding and welfare incidents start sensitive, and each time someone opens a sensitive incident it is recorded.

- **Three answers**: what happened, where and how serious it is
- **Pick on the map**: the spot on your site plan
- **Sensitive**: on from the start for medical, safeguarding and welfare
- **Report through Fai**: for anyone on your event's team

- [Report and handle incidents at your event](https://www.ticketfairy.com/guides/report-and-handle-incidents-at-your-event)

     ![Ticket Fairy Report an incident dialog with what happened, where, how serious it is and the Sensitive switch](https://www.ticketfairy.com/embeds/posters/marketing-event-staffing--report-incident.png)

## Tell your safety lead the moment something serious happens

When someone reports an incident as high or critical, or raises it to either later, Fai emails your safety lead and the event's owners and admins straight away.

The email gives how serious it is, the type, where and when, and a link to the incident. It never says what happened or who was involved. If a critical incident is still open later, they get a second email and your team sees an urgent task to chase it.

Fai also checks your incident log every hour for patterns. When several incidents of the same kind happen in the same place close together, such as medical calls at the main bar, she drafts an email to your safety lead asking whether the area needs more cover. If you have not named a safety lead, she drafts a task instead, for your team to approve.

- **Safety alerts**: for each high or critical report
- **Raised later**: an incident made more serious alerts them too
- **Patterns**: the same kind of incident in the same place

- [Run your whole site from one live control log](https://www.ticketfairy.com/event-operating-system/event-control-and-safety/event-control-room)

## Let Fai sort each report while your team decides

Fai suggests each report's type and how serious it is, and the person dealing with it takes her suggestion with one button or keeps their own.

You name who is dealing with it, move the incident from new to Being handled, then to resolved and closed, and add updates as things happen. Each step joins its timeline with who took it and when. Updates are added, never overwritten, so the record is ready for your debrief and your licensing officer.

The log puts what needs attention first, most serious at the top, with counts by status, so your duty manager sees at a glance what is open. Incidents are never deleted: you close one logged by mistake with a note, and you can reopen a closed incident. When you no longer need them, you can remove an incident's personal details. The people involved and the text of each update are cleared, while the record of who did what and when stays complete.

Each incident also helps you plan the next event. Fai looks at the incidents at your brand's earlier events when she drafts a risk register, so a kind of incident that keeps happening shows up on next year's register with the count beside it.

- **Fai suggests**: the type and how serious it is
- **Next step**: Start handling, Mark resolved, Close or Reopen
- **What's happened so far**: each step and update with who and when
- **Remove personal details**: the people and updates cleared, the record kept

- [Plan for weather and keep your risk register current](https://www.ticketfairy.com/event-operating-system/event-control-and-safety/weather-and-risk)

     ![Ticket Fairy incident panel for a crowd surge, with its seriousness, the next step, Fai's suggestion, the people involved and what has happened so far](https://www.ticketfairy.com/embeds/posters/marketing-event-staffing--incident.png)

## How you can keep everyone informed and safe

- ### A weather hold at an open-air festival

  Lightning is forecast at four. The site manager texts the Weather hold template to the stewards and bar volunteers on Saturday's rota and to the traders, checks who it will reach, and sends All clear to the same people an hour later.
- ### A gate change at a stadium show

  Gate C closes after a burst pipe, and the gate stewards on that shift get a text with their first name and the new gate.

  The message panel shows two people who did not get it, and the supervisor sends it again to only those two.
- ### A busy night at a club

  Stewards log three fainting cases near the front bar within the hour. Fai spots the pattern and drafts an email to the safety lead, who adds a welfare officer and water at the bar before the headliner.
- ### A conference with volunteers

  The rota goes to the volunteer coordinator every morning at seven, and accepted volunteer applicants get their first-day briefing scheduled the night before.

  On the day, a volunteer at registration logs a lost-badge incident through Fai from a phone.
- ### A market with many traders

  The market organizer texts each trader, with their first name filled in, to say the power hook-ups go live an hour early.

  A first aider logs a slip on the wet ground with a pin on the site map and closes it with an update.

[Get started free](https://manage.ticketfairy.com/registration) [Book a demo](https://www.ticketfairy.com/event-ticketing/book-a-demo)

## See it in your dashboard

- ![Ticket Fairy incident log for a festival, with counts by status and the incidents that need attention, most serious first](https://www.ticketfairy.com/embeds/posters/marketing-event-staffing--incidents.png)
  *Your incident log puts what needs attention first, most serious at the top.*
- ![Ticket Fairy list of all the messages one crew member was sent about the event](https://www.ticketfairy.com/embeds/posters/marketing-event-messages--person-messages.png)
  *Each crew member's page shows the messages you sent them about the event, and how each one went.*

## Set it up step by step

- [Message the crew, volunteers and traders working on your event](https://www.ticketfairy.com/guides/message-the-people-working-on-your-event)
- [Send your event lists to your team on a schedule](https://www.ticketfairy.com/guides/send-your-event-lists-to-your-team-on-a-schedule)
- [Report and handle incidents at your event](https://www.ticketfairy.com/guides/report-and-handle-incidents-at-your-event)

## Questions about Team Messages and Incidents

### Messages & incidents

#### Who can send messages and see the incident log?

The event's owners, admins and producers can, from Messages and Incidents on the event's Operations page, once your brand and account are verified for messaging. Any member of your event's team can ask Fai to log an incident or add an update, and Fai waits for their yes first.

#### How many people can I message?

One message can go to up to 2,000 people. Your team can message up to 10,000 people a day and send 20 messages an hour. A text can be up to 480 characters, and numbers that replied STOP are left out.

#### When can a scheduled message go?

You can schedule a message from 5 minutes to 60 days ahead, in the event's time zone. You cannot take a message back once it is sent.

#### Where do replies go?

Email replies go to your brand's email address. Replies to a text get an automatic answer and are not collected, so ask people to reply by email or phone.

#### Can I message ticket holders here?

No. Messages is for the people working on the event. Email or text your ticket buyers from the event's Messaging page.

#### Who can get a scheduled list?

Up to 10 people from your event team can get each scheduled list. The rota, rooming list and pickups hold people's names, so only owners and admins can schedule and receive them. Each file lasts 7 days.

#### Who gets the alert about a serious incident?

Your safety lead, named with their email in Rota rules, and the event's owners and admins get it, up to 20 people. They get it once each time an incident rises to high or critical. If a critical incident is still open 30 minutes after it was reported, Fai chases it again at her next hourly check.

#### What counts as a pattern?

A pattern is three or more incidents of the same type in the same place within two hours. Fai drafts an email to your safety lead, or a task if Rota rules name none, and your safety lead decides what to do.

#### Can I delete an incident logged by mistake?

No. Incidents are never deleted, so the record stays complete. Close it with a note saying it was logged by mistake. You cannot undo removing personal details.

#### Where do I find the incident log?

You find it on the event's Operations page, under Incidents. On sports events and food and drink festivals you see it from the start. On any other event, open it from More sections. The log refreshes every 20 seconds.

## More of the Event Operating System

- Show day

  ### [Run of show](https://www.ticketfairy.com/event-operating-system/show-day/run-of-show-and-show-calling)

  You start the run of show from Fai's draft and fix clashes and late finishes before show day. Your team calls cues live, catches a late stage up in one step, and gives each team its day sheet, backstage TV and calendar.
- Control & safety

  ### [Control room](https://www.ticketfairy.com/event-operating-system/event-control-and-safety/event-control-room)

  Your site runs from one live control log, and each job goes to the right team and channel. You see which pass holders are in each zone and when each went in, and your medical and welfare log stays private.
- Control & safety

  ### [Weather & risk](https://www.ticketfairy.com/event-operating-system/event-control-and-safety/weather-and-risk)

  You see your venue's forecast, official weather warnings and what your date is usually like, months before a forecast exists. Fai drafts a risk register, and your team keeps it current.
- Crew & volunteers

  ### [Rota & hours](https://www.ticketfairy.com/event-operating-system/crew-and-volunteers/staff-rota-and-shifts)

  Each team and hour gets covered: you fill gaps with people who fit, find drop-outs the day before and approve hours from your crew's check-ins.

       [Back to **Show day**](https://www.ticketfairy.com/event-operating-system/show-day) [Previous **Run of show**](https://www.ticketfairy.com/event-operating-system/show-day/run-of-show-and-show-calling)

See how the Ticket Fairy [online ticketing system](https://www.ticketfairy.com/event-ticketing/) helps you sell more tickets, with every feature, the pricing and the support you get.

Get started free and plan your next event today, or book a demo to see it on an event like yours.

## Start free with the Event Operating System

Sign up and plan your next event, from the first advance to show day.

The Event Operating System on every plan, Free included

Unlimited events with no monthly fee

Fai drafts the admin, and you approve it

   [Get started free](https://manage.ticketfairy.com/registration)

No credit card required

The Ticket Fairy, Inc. is a fintech company and technology platform. The Ticket Fairy, Inc. is not a bank, financial institution, or regulated financial services provider. Vault banking services are provided through regulated banking partners. Ticket Fairy Capital financing is provided by third-party private credit partners. The Ticket Fairy, Inc. does not make credit decisions, and all funding terms, approvals and conditions are determined by those lending partners.

Ticket Fairy is not a direct lender and does not make credit decisions. Ticket Fairy acts solely as a technology provider, connecting event businesses with third-party lending partners. All funding decisions, terms, and conditions are determined by the respective lending partners.

---

This page is on Ticket Fairy, a ticketing, marketing and operations platform for live events and the venues that host them: festivals, club nights, concerts, conferences and tours, and night clubs, beach clubs and concert venues. It grows revenue with fan rewards that turn an audience into a sales channel, and runs the money side with payments and payouts, Vault business banking, and working capital advanced against ticket sales. [How Ticket Fairy ticketing works](https://www.ticketfairy.com/event-ticketing) · [Ticket Fairy for AI assistants](https://www.ticketfairy.com/llms.txt)
