Keep the conversation going

Open the site's Email workspace and select Inbox. Incoming replies also go to the site owner's email.

The app displays readable message text. Attachments are not part of the current inbox feature.

1. Select Refresh if a new message has not appeared.
2. Open the message by its subject.
3. Check the sender, subject, and received time.
4. Use Previous or Next to find older messages.

The reply editor addresses the sender of the open message. The subject starts with Re: where appropriate.

Reply personalization is off: write the actual message instead of using campaign placeholders.

1. Read the full message and check the recipient.
2. Write the response.
3. Preview it before sending.
4. Select Send reply.
5. Check the Reply queued confirmation and then Activity.

Queued is not delivered. Check Activity for subsequent status. Direct replies still respect bounce and complaint suppression.

An accepted incoming reply stops the contact's current form sequences. This prevents later automated follow-ups from continuing over the conversation.

A message that fails sender authentication shows a warning and does not stop the sequence automatically.

1. Check any sender-authentication warning before replying.
2. Verify an unexpected request through a known contact channel.
3. Review the relevant flow if an automation should be paused for everyone.

Do not treat an email's display name as proof of who sent it.

Check the site's Sender status and receiving records first. A website domain connection is not enough to receive email.

1. Confirm the message went to the connected sender address.
2. Check the receiving MX record shown in Sender.
3. Refresh Inbox and check the owner's inbox and spam folder.
4. Use Help with the message time and safe sender details if the issue continues.

• Sender setup