Automation · Customer service and scheduling
Escalate a WhatsApp case to your team in Slack and bring back their answer
An AI agent hands your team in Slack the WhatsApp case that needs a person, with its context, and brings the thread's answer back to the customer.
How do I pass my team in Slack a WhatsApp question the agent cannot solve?
A Met connected to Slack first searches public channels to see whether your team already answered that same question. If not, it finds the support channel and the person in charge, checks whether they are available, posts a message with a summary of the case and the customer's phone number, and tells the person someone on the team will look into it. When the customer writes again, the Met reads that message's thread in Slack and brings back the answer your team left, without anyone copying it over to WhatsApp. The case stays in Slack, where your team already works.
What starts it
When the customer writes
It starts when a customer writes on WhatsApp about something the Met cannot solve alone, such as a warranty, a complaint or a technical question, or writes again to learn the answer. There is no trigger to configure: the Met assigned to the line handles it in 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 escalates to Slack
Customer service team
This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with Slack connected. Its work ends when the case reached the right channel with its context, and when the customer gets the answer the team gave.
Run by the customer support Met
Channels: WhatsApp
What you need connected
- Slack Automate and collaborate
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
Search whether the team answered this before
Before escalating, the Met searches Slack's public channels for messages about the same product or issue. If it finds a clear answer from the team, it uses it with the customer and does not open another case for something already solved.
- 2
Find the channel and the person in charge
The Met finds the channel the skill names, for example the warranty channel, and the person who handles that kind of case, to mention them in the message. That way the case does not sit in a channel nobody reads.
- 3
Check whether the person in charge is available
Before mentioning them, the Met reads the person's Slack profile. If their status says they are on vacation or off shift, it mentions the backup the skill names, so the case does not wait for someone who will not see it.
- 4
Post the case with its context
The Met sends the channel a message with a summary of what happened, the customer's phone number, what was already tried and a mention of the person in charge. It keeps the message ID to read its thread later.
- 5
Bring the thread's answer to the customer
When the customer writes again, the Met reads the thread of the message it posted. If the team already replied, it passes that answer on in plain words; if not yet, it says the case is still under review and does not make up a solution.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
An approved Slack app from your company
You create an internal app at api.slack.com with Met's return URL and copy its Client ID and Client Secret. If your workspace requires app approval, the Slack administrator approves it.
-
Slack connected with messages on
In Met, open Connections → Slack → Connect, paste the Client ID and the Client Secret and authorize with the support team's account. The admin leaves sending messages switched on.
-
A WhatsApp line with the Met assigned
The business connects its WhatsApp Business API line and assigns the Met that answers customers. The conversation stays on WhatsApp; Slack remains where the team works.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not alert the customer the moment the team replies: there is no Slack trigger in this procedure. The Met reads the thread when the customer writes again.
-
It does not solve the case: it hands it over with context and brings back the answer. A warranty, a refund or an exchange is still your team's decision.
-
It does not ask for confirmation in the chat before posting in Slack: if sending is on, the message goes out. The admin decides which actions stay on.
-
It does not search private channels or direct messages without the authorizing person's consent. In this procedure the first search stays within public channels.
-
It does not post as a bot: messages go out with the Slack account that authorized the connection, so a team account works better than a personal one.
-
It does not upload to Slack the photo the customer sent on WhatsApp: the message carries the summary and the phone number, and the team asks for the file if they need it.
FAQ
Questions about this automation
The Met tells the customer the case is still under review each time they ask, without making up an answer. The skill should say how long to wait before offering another channel.
No. The Met reads the thread and tells the customer what is meant for them. If the team discusses something internal in the thread, the skill should ask the Met to pass on only the final answer.
Yes. The skill says which channel gets warranties, which one payments and which one technical support, and the Met finds the right one before posting.
Because Slack only lets registered apps that are internal to your workspace or published in its directory use its MCP server. The app is yours and your administrator controls it.
Keep going
Other automations built on the same tools
Orders and fulfillment
Alert Slack about every order that comes in on WhatsApp
How do I connect WhatsApp to Slack so orders reach my team's channel?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 7 real tools
- Needs:
- Slack
Customer service and scheduling
Open a Linear issue from a customer report on WhatsApp and tell them how it is going
How do I make customer reports on WhatsApp arrive in Linear as issues?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 6 real tools
- Needs:
- Linear
Customer service and scheduling
Open a Freshdesk ticket from WhatsApp and tell where it stands
How do I turn a complaint that arrives on WhatsApp into a Freshdesk ticket without copying it by hand?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 10 real tools
- Needs:
- Freshdesk
Customer service and scheduling
Open a Gorgias ticket from WhatsApp and escalate it to the team that solves it
How do I move a complaint that arrives on WhatsApp into Gorgias without copying it by hand or losing what the customer said?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 7 real tools
- Needs:
- Gorgias
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.