Skip to content

Automation · Customer service and scheduling

Sign up on WhatsApp for your OneSignal alerts by email or SMS, or unsubscribe

An AI agent signs up in OneSignal whoever asks for your alerts on WhatsApp, by email or SMS, with their tags, and handles opt-outs.

How do I make whoever asks for alerts on WhatsApp get signed up in OneSignal by email or SMS, and unsubscribe just as easily?

A Met connected to OneSignal confirms which OneSignal app it works in, looks the person up by the alias your team uses and, if they do not exist, creates them. It adds the subscription they asked for, email or SMS, and sets the tags your team uses to segment, for example the category they care about. If the person later asks to stop getting email, the Met unsubscribes that address, as long as the admin turned that action on, since it starts switched off. The Met does not send alerts in this procedure: your OneSignal campaigns send them.

What starts it

When the customer writes

It starts when someone writes on WhatsApp asking to be alerted by email or SMS, for example about new arrivals, or asking not to be written to anymore. There is no trigger to configure: the Met assigned to the line runs the procedure inside that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Support Met that manages subscriptions

Customer service team

This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with OneSignal connected. Its work ends when the person is signed up to the channel they asked for, with their tags, or unsubscribed if that is what they asked.

Run by the customer support Met

Channels: WhatsApp

What you need connected

5 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Confirm the OneSignal app

    The Met lists the apps the connected account can access and uses the one the skill names. One connection can see several apps, and this keeps it from signing anyone up in the wrong one.

  2. 2

    Look the person up by alias

    The Met looks for the user by the alias your team uses, for example the customer ID. If they exist, it works on that user and does not create another.

  3. 3

    Create them if they do not exist

    If they do not show up, the Met creates the user with basic properties, such as their language, so your alerts reach them in the right language.

  4. 4

    Add the subscription and the tags

    The Met adds the email or SMS subscription they asked for and updates their tags, for example "interest: shoes". Those tags are what your segments use later.

  5. 5

    Unsubscribe the email if they ask

    If the person writes that they no longer want emails, the Met unsubscribes that address. This action starts switched off: if the admin did not turn it on, the Met tells them someone on the team will do it.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

A push subscription is created by the app on the person's phone. Over WhatsApp, the Met signs up email or SMS, which only need the address or the number.

The Met finds them by alias and updates that user: it adds the missing subscription or changes the tags, without creating a repeated user.

Because unsubscribing an email starts switched off. If the admin does not turn it on, the Met does not do it and tells the person someone on the team will handle it.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.