Automation · Sales and quoting

Add the B2B prospect who writes on WhatsApp to a Reply.io sequence

An AI agent checks in Reply.io whether the prospect writing on WhatsApp exists, adds them to your sequence and leaves the call as a task.

Show me this with my own operation See every automation

How do I move the prospect who writes on WhatsApp into my Reply.io sequence without loading them by hand?

A Met connected to Reply.io looks the prospect up by the work email they leave on WhatsApp and, if they exist, checks their activity so it does not repeat what they already got. If they are new, it creates them in your account. Then it finds the sequence your team uses for that kind of prospect, enrolls them and, if the person asked for a call, creates a call task for the salesperson. The three actions that write arrive turned off because Reply marks them as destructive: the admin turns them on in Connections before using this automation. The sequence runs in Reply with the steps you already built.

What starts it

When the customer writes

It starts when someone from a company writes on WhatsApp asking for information or a demo and leaves their work email. There is no trigger to set up: 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

Met that receives and qualifies B2B prospects

Sales team

It has no seeded name: it is the Met that answers the sales line of a company that sells to other companies, with Reply.io connected. Its work ends when the prospect is in the right sequence and, if they asked for a call, there is a task for the salesperson.

Run by the lead qualification Met

Channels: WhatsApp

What you need connected

Reply.io Sell and serve

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
Look up the prospect by email

The Met searches Reply for a contact with the exact email the person gave in the chat. If it exists, it keeps that contact and does not create another one.
- reply_search_contacts Reply.io
2
Check what they already received

If the contact exists, the Met pulls their activity: sends, opens, replies and calls. That way it knows whether they are already in a sequence or already talked to someone on the team.
- reply_get_contact_activity Reply.io
3
Create them if they are new

If they do not show up, the Met creates the contact with their name and email. This action starts turned off because Reply marks it as destructive; the admin has to turn it on.
- reply_create_contact Reply.io
4
Find the right sequence

The Met searches for the sequence by the name its instructions give, for example the inbound demo one, and confirms it is not archived.
- reply_search_sequences Reply.io
5
Enroll them in the sequence

The Met enrolls the contact in that sequence. This action also starts turned off; if the admin turns it on, the sequence emails go out from the mailboxes in your Reply account.
- reply_add_contact_to_sequence Reply.io
6
Leave the call as a task

If the person asked for a call, the Met creates a call task in Reply for the right salesperson. Creating tasks starts turned off, like the other actions that write.
- reply_create_task Reply.io

Before you start

What you need ready

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

The Reply.io ready connector with three actions on

In Met, open Connections → Reply.io → Connect and paste your API key, found in Reply under Settings → API Key. Then turn on creating contacts, enrolling in sequences and creating tasks.
An active sequence with a connected mailbox

The sequence the prospect joins is built in Reply, with its steps and the sending mailbox. The Met does not write those emails: it only enrolls the contact.
A WhatsApp line with the Met assigned

You connect your WhatsApp Business API line in Met and assign the sales Met. Reply remains the outreach tool; the conversation happens on WhatsApp.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not work with the default actions. Creating the contact, enrolling it and creating the task arrive turned off because Reply marks them as destructive.
It does not ask anyone for confirmation before enrolling. If the action is on, the Met adds the contact with what the person said in the chat.
It does not start the sequence. This automation does not use the start sequence action: keeping the sequence active and sending is up to your team in Reply.
It does not search by name with precision. The exact lookup is by email or LinkedIn profile; without an email, the automation cannot confirm whether the prospect already exists.

FAQ

Questions about this automation

The Met sees it in their activity in the second step. What it does next depends on its instructions: for example, not enrolling them again and only creating the task for the salesperson.

No. The sequence steps and copy are built by your team in Reply; the Met only enrolls the contact in it.

Reply accepts up to 100 contacts per call. In this automation the Met enrolls one: the person writing on WhatsApp.

The Reply page includes the action to reply to a thread, which arrives turned off. This automation does not use it: the conversation with the person stays on WhatsApp.

Keep going