Automation · Sales and quoting

Log the WhatsApp lead in HighLevel and move its opportunity to the right stage

An AI agent logs in HighLevel whoever writes on WhatsApp, tags them and moves their opportunity to the right pipeline stage.

Show me this with my own operation See every automation

How do I make every person who writes on WhatsApp land in HighLevel and move along the pipeline without copying them by hand?

A Met connected to HighLevel looks the person up among the sub-account's contacts and creates them if they are missing; if they exist, it updates them without a duplicate. It adds the tags your team uses to segment, checks the pipelines and looks for an open opportunity. If there is one, it moves it to the stage that matches what the person asked for, and reviews their tasks so it does not promise something the team already scheduled. If there is no opportunity, it does not make one up: the official server cannot create them, so it leaves the contact tagged for your team to open one.

What starts it

When the customer writes

It starts when a prospect writes on WhatsApp asking about your products or services. There is no trigger to configure: the Met assigned to the sales 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 prospects

Sales team

This is not a named, seeded Met. It is the Met that answers the sales line, with HighLevel connected. Its work ends when the prospect is in the sub-account exactly once, with their tags, and their opportunity, if there is one, sits in the right stage.

Run by the lead qualification Met

Channels: WhatsApp

What you need connected

HighLevel Sell and serve

6 steps · 7 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 the person up in the sub-account

The Met checks the HighLevel contact list with the details the person gave in the conversation. That tells it whether this is someone new or a contact your team already knows.
- contacts_get_contacts HighLevel
2
Create or update the contact without duplicates

With the name, phone number and request, the Met creates the contact or, if it exists, updates it. Creating or updating in a single step keeps the same person from appearing twice in the sub-account.
- contacts_upsert_contact HighLevel
3
Tag based on what they asked for

The Met adds the tags your team defined in the skill, for example the product they are interested in or their city. Those tags are what your campaigns and filters use later in HighLevel.
- contacts_add_tags HighLevel
4
Find the pipeline and the opportunity

The Met checks the pipelines and their stages and looks for an open opportunity for the person. Reading the stages before moving it keeps it from sending the opportunity to a stage your pipeline does not have.
- opportunities_get_pipelines HighLevel
- opportunities_search_opportunity HighLevel
5
Move the opportunity to the right stage

If the opportunity exists, the Met moves it to the stage that matches the conversation, for example from "interested" to "asked for a quote". If it does not exist, it does not create one: it marks the contact with a tag so someone on the team opens it.
- opportunities_update_opportunity HighLevel
6
Review the contact's pending tasks

Before saying goodbye, the Met reviews the contact's tasks so it does not promise a call that is already scheduled, or so it can tell the person when they will be contacted.
- contacts_get_all_tasks HighLevel

Before you start

What you need ready

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

A HighLevel sub-account with a pipeline

Your team has the HighLevel sub-account with the sales pipeline and its stages, and the tags it uses to segment prospects.
HighLevel connected with the writes you need

In Met, open Connections → HighLevel → Connect and authorize the sub-account. The admin leaves contact create or update, tags and opportunity updates switched on.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers the sales line. The conversation happens there; HighLevel remains the prospect's record.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not create new opportunities. HighLevel's official server has no such tool, so someone on the team opens the opportunity once the Met leaves the contact tagged.
It does not book the sales meeting. It can read calendar events, but booking still happens in HighLevel or through another scheduling integration.
It does not ask for confirmation in the chat before creating the contact or moving the opportunity: if the action is on, it runs it. The admin decides which writes stay on.
It does not qualify with rules you did not give it. What each tag and each stage means is written by your team in the Met's skill.

FAQ

Questions about this automation

The Met finds them in the search and updates that same contact instead of creating another. Their tags and opportunity are worked on the existing record.

Because HighLevel's official server offers no tool to create one. The Met leaves the contact tagged so your team opens it, and from there it can move it between stages.

Yes. In the Met's skill you write which conversation matches which stage of your pipeline, and the Met checks the real stages before moving the opportunity.

Keep going