Inbox

Your event sends many emails, and people answer them with questions. The Inbox keeps all of it in one place, grouped by person. Your whole team sees what each person received and wrote, and answers from the event rather than a personal mailbox.

How it works

Everything the event emails, in one place

Open Communication → Inbox. It records every email the event sends, and every reply people send back. This includes automated emails, meeting emails, campaigns, announcements sent by email, and your team's replies. Test sends are not included.

One conversation per person

Emails are grouped by email address. Everything one person was sent and everything they wrote back reads as one conversation.

The list has two parts:

  • Replies — people who wrote to the event, most recent first.
  • Sent by the event — conversations that only hold emails the event sent.

So a campaign sent to everyone never pushes a waiting reply down the list. Each row shows the person, the number of emails, the subject, and what the latest email was, such as Replied, You replied or Campaign.

Use the All, Replies and Unread filters, or search by name, address or subject.

Unread conversations

A conversation with a new reply is highlighted until you open it. Unread is tracked for each team member, so opening it clears it for you only.

The number of unread conversations is shown beside Inbox in the Communication menu. Unread chats are shown beside Messages.

Reading a conversation

A conversation reads like a mail client. The latest email is open and older ones are one line each. Click one to open it. A long conversation folds its middle part.

An open email shows who sent it, who received it, and what kind of email it was. If it was not delivered normally, it shows a status:

Captured — not delivered The email was recorded but not sent. This is normal on test environments and sandbox events.

Not sent The email could not be sent.

Bounced The address is wrong or the mailbox is full.

Spam The reply was marked as spam. It does not count as unread.

Attachments people sent are listed for download. If the address belongs to an attendee, View attendee opens their record.

How replies reach the Inbox

Every event email has the event's own address as its reply address. When someone presses Reply, their answer arrives here.

If you set Replies go to to Another address in Communication → Settings, replies go to that mailbox instead. They then do not appear in the Inbox.

Good to know

  • Account Owners and Super Users can open the Inbox. So can Users with Can send emails on this event.
  • A message carrying a virus is dropped and never shown.
  • The Inbox is kept for as long as the event exists, and is deleted with it.

Step by step

Read and answer a reply

Open Communication → Inbox.

Choose Replies or Unread to see who is waiting for an answer.

Click a conversation to read it.

Click Reply on the email you are answering.

A compose window opens with To and the subject filled in. Reply all also copies the people the person copied.

Add anyone under Cc or Bcc if needed, then write your answer.

The earlier email is quoted under your text. Click × to send without it.

Click Send.

It goes out from the event's sender address and appears in the conversation with your name, so colleagues see who answered.

What attendees see

In attendee emails

Nothing changes for attendees. They press Reply on an event email as usual. Your team's answer reaches them as an ordinary reply from the event's sender address.

Tips

  • Keep Replies go to on Event inbox unless someone watches another mailbox all day. Otherwise replies are split between two places.
  • Check Unread every morning before the event, and often on event day. People reply to confirmations with questions.
  • When you see Bounced, correct the attendee's email before the next important message.