Email your team when a visitor reaches a flow step

Send your team an email when a visitor reaches a particular point in your flow. You can include the answers they've just given, the page they're on, and their email address when it's known.

For example, put an Email step after an NPS question and a written-feedback question. Your team gets the score and the visitor's own words together, rather than having to open each response to see what needs attention. RightMessage sends these notifications from our servers; you don't need to set up a sending action in your connected email platform.

Add the Email step where you need it

1. Open your flow and select Build.
2. Drag Email from Actions to the point where the notification should send.
3. In Send email notification, set To to the people who should receive it. Separate addresses with commas. You can include up to 20 recipients.

To starts with the email address of the person signed in. Replace it if the notification belongs with someone else. Recipients are fixed addresses: you can't use Liquid or a visitor variable in this field. Recipient addresses aren't included in the public website tag.

Put the step after the questions whose answers you want to include, and before an offer, form, or other step that ends that path. To send after a form is submitted, add it to the form's post-submit path, before the final message or redirect. Email steps also work in flow A/B test variants.

The flow continues immediately after this step. Visitors don't wait for delivery and don't see the notification on your website.

Enlarge

Send email notification drawer with team@example.com as the recipient, Subject and Body variables, Send once per visitor enabled, and the notification limitOriginalOriginal

Write the subject and include answers

Subject starts as New response from {{ currentpage.title }}. You can keep it or write something more specific, such as “New customer feedback.” Both Subject and Body support Liquid variables.

The starter Body includes {{ visitor.email }} and {{ currentpage.url }}, followed by a reminder to add your content. Replace that reminder with the details your team needs.

To insert an answer without looking up its Liquid name:

1. Put your cursor where the answer should appear in Body.
2. Click the + button labeled Insert variable.
3. In Available Variables, choose the question you want. Rows show the question text or a description of the value, rather than Liquid code.
4. Repeat for the other answers you want to include. For an NPS notification, add a label such as “Score:” before the NPS answer and “Feedback:” before the written answer.

The Visitor section appears first. Choose Visitor's email address (blank until they're identified) to insert {{ visitor.email }}. This uses the email identified by your connected email platform, otherwise an email captured from a form or an ?email= link. It stays blank if the visitor hasn't been identified.

Enlarge

Available Variables picker opened from Email Body, with Visitor first and flow variables labeled by their questionsOriginalOriginal

Choose whether to send again

Send once per visitor is on by default. Leave it on when you want one notification from this step for each visitor, rather than another email every time they reach it.

Turn it off if your team needs a notification each time a visitor reaches the step. The project's hourly limit still applies.

What your team receives

Recipients get your subject and body, with the visitor's available answers inserted. Visitor answers are inserted as text, with links removed.

Every notification ends with a footer naming the flow and site. It also includes the visitor's email address when known and a View visitor in RightMessage link, so your team can open their profile for more context.

Each project can send up to 30 notifications an hour. Beyond that, notifications may arrive late or not at all. If you need a higher rate limit, contact support@rightmessage.com.

Check the path before going live

Use Preview on your site to follow each relevant path and check that it reaches the Email step. Preview and on-site debugger sessions never send email notifications. The debugger shows: “Not sent. The debugger never sends email notifications.”

Check the recipient addresses and the order of your questions before you publish your changes. To check actual delivery, reach the step as a visitor on the published site outside a debugger session, using recipients who expect the notification. If Send once per visitor is enabled, remember that a visitor who already triggered that step won't send another notification.

For more ways to check the flow before publishing, see testing your changes.