Route WhatsApp customer chats into dedicated Telegram threads

Each WhatsApp customer gets their own Telegram thread, so your team can reply from Telegram and it reaches them on WhatsApp.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig>"customer sends whatsapp message"]:::trig s0["check for existing thread"]:::task s1["deliver message to thread"]:::task s2(("agent replies in telegram")):::human s3["send reply to whatsapp"]:::svc trig --> s0 s1 --> s2 s2 --> s3 gx{"× does thread already exist"}:::gate s0 --> gx p00["use existing thread"]:::task gx -->|"existing customer"| p00 p10["create thread"]:::task gx -->|"new customer"| p10 p11["save mapping"]:::task p10 --> p11 jn{"○ continue to thread"}:::gate p00 --> jn p11 --> jn jn --> s1 out[/"organized per customer chat threads"/]:::out pay{{"no lost or mixed up conversations"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceA personOne path onlyPaths rejoinResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
Knowledge Base & RAGE-commerce & ProductMessaging & NotificationsSpreadsheet & Database OpsCustomer Support & Ticketing
Connects
WhatsAppTelegramSupabase

The problem it solves

When customer messages come in on WhatsApp faster than your team can organize them, conversations get mixed up, replies land in the wrong thread, and context gets lost. Handling a high volume of chats without a proper system means dropped conversations and frustrated customers.

Who it fits

A customer support team or e-commerce operation handling a high volume of WhatsApp conversations.

How it works

  1. A customer sends a message on WhatsApp
  2. The system checks if that customer already has a dedicated Telegram thread
  3. If not, it creates one and saves the connection between the customer and the thread
  4. The message appears in that customer's Telegram thread for your team to answer
  5. When an agent replies in Telegram, the customer receives it back on WhatsApp
What you get

Customer replies that reach WhatsApp without switching apps

You get every WhatsApp customer routed to their own Telegram thread, so your team can reply from Telegram and reach them instantly.

What you get

A dedicated, organized Telegram thread per customer, with replies delivered back to WhatsApp automatically.

What you need

A WhatsApp Business API account, a Telegram bot in a supergroup with topics enabled, and a Supabase database.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook