Automation · Customer service and scheduling

Add whoever asks for your news on WhatsApp to your Sender list

An AI agent adds people who ask for your news on WhatsApp to your Sender list, without duplicates, and removes them if they ask later.

Show me this with my own operation See every automation

How do I add customers who ask on WhatsApp to my Sender email list?

When a customer asks on WhatsApp to receive your news by email, a Met connected to Sender asks for their email, checks whether they are already a subscriber and, if not, creates them in the group your team named. If they already existed, it adds the group instead of duplicating them, and if they had unsubscribed it reactivates them because they asked. If later they write that they no longer want emails, the Met unsubscribes them, as long as the admin turned that action on. Campaigns still go out from Sender.

What starts it

When the customer writes

It starts when a customer writes on WhatsApp that they want to receive offers or news by email, or that they no longer want them. 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 the list

Social team

It is the Met that already answers the business's WhatsApp, with Sender connected. Its work ends when the person is in the right Sender group with the email they gave, or unsubscribed if they asked for it.

Run by the customer support Met

Channels: WhatsApp

What you need connected

Sender Create and promote

6 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
Check whether they are a subscriber

The Met asks the customer for their email and searches Sender for a subscriber with that email or with the conversation's phone number, so it does not create a repeated record.
- get_subscriber Sender
2
Find the right group

The Met lists the Sender groups and takes the one your team named in the skill, for example "WhatsApp customers". If it cannot find it, it does not invent one and alerts the team.
- list_groups Sender
3
Create the new subscriber

If they did not exist, the Met creates them with their name, email and the group, and confirms in the chat that they will receive your news.
- create_subscriber Sender
4
Add the group to an existing one

If they were already a subscriber, the Met adds the group without touching the rest of their data, so your team knows they came through WhatsApp.
- update_subscriber Sender
5
Reactivate whoever comes back

If the person had unsubscribed from email and now asks to come back, the Met reactivates them on that channel, because they are the one asking in the conversation.
- subscribe_subscribers Sender
6
Unsubscribe when they ask

If the customer writes that they no longer want emails, the Met unsubscribes them on that channel. This action starts turned off: if the admin did not turn it on, the Met alerts the team to do it in Sender.
- unsubscribe_subscribers Sender

Before you start

What you need ready

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

A Sender account with a WhatsApp group

Create in Sender the group where customers coming from WhatsApp should go, and give the Met its name in the skill.
Sender connected with the writes you need

In Met, open Connections → Sender → Connect and authorize with a user who can edit subscribers. To unsubscribe from the chat, the admin turns that action on.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers customers. The sign up happens inside that conversation.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not send the campaign or the welcome email. The Sender MCP does not send campaigns; what the subscriber receives is decided by your workflow or campaign in Sender.
It does not check that the email exists. The Met saves the email the customer writes; if it is misspelled, it stays misspelled.
It does not ask for confirmation in the chat before creating or changing the subscriber: if the action is on, it runs it. The admin decides which writes stay on.
It does not unsubscribe while that action is still off. In that case the Met alerts the team and the unsubscribe is done in Sender.