DocumentationHelp CenterCommunicationSending Messages

Sending Messages to Attendees

You can email announcements, updates, or reminders to your attendees directly from Hi.Events, without exporting a list to another mail tool.

How to Get There

  1. Open your event
  2. Click Messages in the left sidebar (under Guest Management)

Before You Can Send

Two things have to be in place before the message form appears in the compose window:

  • Your account email must be verified
  • Your account must be verified by connecting a Stripe account. Until then you’ll see a Connect Stripe to enable messaging notice with a Connect Stripe button that takes you to your organizer’s payout settings

Sending a Message

  1. Click Compose
  2. For recurring events, optionally pick an Occurrence. Leave it empty to send to all occurrences
  3. Choose your Recipients:
    • Attendees with a specific ticket — then select the tickets
    • All attendees of this event
    • Order owners with a specific product — then select the products, and which Order statuses to include (Completed, which is selected by default, and Awaiting offline payment)
  4. Write your Subject and Message
  5. Choose Send now or Schedule for later
  6. Tick I confirm this is a transactional message related to this event. The send button stays disabled until you do
  7. Click Send Message (or Schedule Message if you’re scheduling it)

Messages are delivered as emails to the people matching your criteria. Each email address gets one copy. Messages to ticket holders or all attendees only reach active tickets, so cancelled tickets and tickets still awaiting offline payment are skipped. To reach orders awaiting offline payment, choose Order owners with a specific product and include Awaiting offline payment.

You can also message a single person directly: use Message buyer in an order’s actions on the Orders page, or Message attendee in an attendee’s actions on the Attendees page. To message everyone holding one ticket type, open the actions menu on that ticket in Tickets & Products and click Message Attendees. The compose window opens set to message ticket holders: pick the ticket in Message attendees with specific tickets before you send.

Team members with the Viewer role can read sent messages but can’t compose or cancel them (see Managing Your Team).

Scheduling, Test Sends and Copies

Switch to Schedule for later to pick a preset (1 week before event, 1 day before event, 1 hour before event, 1 day after start date, and 1 day after end date if the event has an end date) or Custom date and time. Only presets that are still in the future are shown, and for a recurring event they’re based on the occurrence you picked. Scheduled times are shown in the event’s timezone. To cancel a scheduled message before it goes out, open it on the Messages page and click Cancel.

The dropdown arrow next to the send button has two extra options:

  • Send as test — sends the message to you so you can check the formatting. A test always goes out straight away, even if Schedule for later is selected. This only keeps it to you when the recipients are Attendees with a specific ticket or All attendees of this event. For Order owners with a specific product, or a message to a single buyer, it also goes to the real recipients
  • Send me a copy — sends you a copy alongside the real recipients

Sending Limits

Every account is on a messaging tier that limits:

  • how many messages you can send in a 24-hour period
  • how many recipients a single message can have
  • on lower tiers, whether your messages can contain links at all

New accounts start on the lowest tier, which allows a few messages a day, a limited number of recipients per message, and no links. Your tier doesn’t go up on its own. If you exceed a limit the send is rejected and the dialog tells you which limit you hit. Contact support (the address is shown in the compose window) if you need your limits raised.

Checking Who Received a Message

Open a sent message from the Messages page and click the recipient label next to To: to open Recipients. It lists everyone the message went to, each with a delivery status:

StatusWhat it means
SentThe email has left Hi.Events and is on its way
DeliveredThe recipient’s mail provider accepted the email
BouncedThe email couldn’t be delivered, usually because the address is wrong or the mailbox no longer exists. Check the address with the attendee and correct it on their order or attendee record
Marked as spamThe recipient reported the email as spam. Only message them again if you need to, and make sure every message is clearly about their booking
FailedHi.Events couldn’t send the email at all

Recipients only appear once a message has gone out. Until then, for example on a scheduled message or one waiting for review, the label is greyed out, and hovering it shows “Recipients are available after the message is sent”.

Message Review

To prevent spam, some messages are held for a quick manual review before they’re sent — this mainly affects newer accounts and newer events (for example, before you’ve connected Stripe, before your first paid order, or within the first 24 hours of creating the event). If your message is held, its status shows PENDING_REVIEW and it’s delivered once approved. A scheduled message approved before its time still goes out at the scheduled time. Review only applies on the lowest messaging tier, so once your tier has been raised, messages aren’t held.

Messages must be transactional — related to an event the recipient has a ticket for. Promotional email may result in account suspension.

When to Use Messages

  • Event updates — time changes, venue changes, or other logistics
  • Reminders — a day-before reminder with what to bring or how to get there
  • Post-event follow-up — thank attendees and share photos, surveys, or future event links
  • Targeted communications — send different messages to different ticket types (e.g. VIP-only updates)

Tips

  • Keep messages concise and relevant
  • Use the subject line wisely — it determines whether attendees open the email
  • You can view sent messages, and who received them, from the Messages page

Last updated