Automation

Send the right push or WhatsApp message to each user automatically, based on what they do in your app.

An automation is a flow of steps that each user moves through on their own: wait a day, send a push, check whether they signed up, send a WhatsApp message if they didn't. You build it once in Engage → Journeys, set it live, and notifySphere runs it for every user who matches the entry rule.

How an automation works#

Every automation has:

  • Entry rules: who starts it. Either users in an audience segment, or users who perform a custom event, such as signup or booking_started.
  • Steps: messages and flow steps, connected on a canvas.
  • Exit rules: when a user leaves early, for example as soon as they complete a booking.
  • Re-entry rules and a schedule.

Each step on the canvas shows how many users are on it, so you can see where people are and where they leave.

Steps you can add#

FieldTypeDescription
Push NotificationMessageSends a push using one of your push templates. You can send a test push to a test subscriber first.
WhatsAppMessageSends an approved WhatsApp template (marketing or utility; authentication templates are not available here). You can send a test message to a number first.
WaitFlowPauses the user for a set time: minutes, hours, days, weeks, months or years.
ConditionFlowA yes/no branch. See below.
TagFlowAdds tags (key and value) to the user, for example stage: nudged, so you can use them in segments.

Yes/No branch (Condition)#

A condition sends each user down the Yes or the No path. It can check one of three things:

  • Custom event: has the user performed this event since entering the automation? Add a Wait before the condition so they have time to do it.
  • Previous message behavior: for an earlier message in the same automation, was it sent (has been received / has not been received) and, for push, was it tapped (has been clicked / has not been clicked).
  • Segment membership: is the user in the chosen segment right now?

Settings#

Entry rules#

  • Audience Segment: users in the chosen segments start the automation. Turn on Future additions only to skip users who are already in the segment and only include users who join it after the automation goes live.
  • Custom Event: a user starts the automation when your app sends that event. Events come from the SDK (postEvent) and from automatic install and signup tracking; see Events. Event names are not case-sensitive.

Goals#

Set the metric you want to judge the automation by: entered, exited early, or completed. Each message step can also have its own goal, such as delivered or clicks.

Exit rules#

Users always exit when they reach the end. You can also make them exit early when:

  • they become active in your app,
  • a custom event happens, for example booking_completed,
  • they no longer match the audience conditions, or
  • they enter a segment.

An event exit takes effect as soon as the event arrives, so a user who books doesn't get the next reminder. You can also add tags to users who exit early.

Re-entry rules#

Choose once only, or let users re-enter after a certain amount of time if they match the entry rules again.

Schedule#

Start immediately when you set it live, or at a date and time. Run forever, or stop at a date and time.

Build and launch an automation#

  1. Create it

    Go to Engage → Journeys and create a new journey. Open Journey Settings and set the entry rule.

  2. Add steps

    Add messages and flow steps between the entrance and the exit. Pick a template for each message and send yourself a test.

  3. Set exit and re-entry rules

    Decide what should stop the flow for a user, and whether they can go through it again.

  4. Set it live

    Setting live runs pre-launch checks and lists anything that still needs fixing. After launch, watch the user counts on each step. Every change is recorded in the audit log.

Examples#

Abandoned booking recovery#

  1. Entry: custom event booking_started.
  2. Wait 1 hour, then send a push: “Your booking is waiting”.
  3. Wait 1 day. Condition: custom event booking_completed?
  4. No: send a WhatsApp template with a link back to the booking. Yes: exit.
  5. Exit rule: custom event booking_completed, so anyone who books leaves at once.

Payment reminder that stops after payment#

  1. Entry: custom event invoice_created.
  2. Wait 2 days, send a push reminder. Wait 3 more days, send a WhatsApp utility template.
  3. Exit rule: custom event payment_completed. A user who pays never gets the next reminder.

Installed but didn't sign up#

  1. Entry: custom event install (tracked automatically by the SDK).
  2. Wait 1 day, send a push. Wait 1 more day.
  3. Condition: custom event signup? No: send a WhatsApp message. Yes: exit.

The yes/no check is what keeps people who already signed up from getting “don't forget to sign up”.

Push first, WhatsApp only if needed#

  1. Send a push.
  2. Wait 1 day. Condition: previous message behavior, the push has not been clicked?
  3. Yes: send the WhatsApp version. No: exit.

WhatsApp marketing messages are charged per message, so sending them only to people who ignored the push keeps the bill down.

Stuck or something unclear? Contact us and we'll help.