WABridges
Guide

WhatsApp support,
built into your backend.

Customers message you on WhatsApp. Your backend receives the conversation as webhooks and replies via API. Own the entire flow — no third-party inbox, no per-agent fees.

Start free → View API docs

Most support tools charge per seat, per conversation, or both. WA Bridges is different: you own the WhatsApp layer, and you build the handling logic in your own backend — or plug it into any helpdesk you already use.

Receive every customer message as a webhook POST. Reply with a single API call. Run it on your infrastructure, with your data, at your scale.

How it works

1
Provision a support bridge
Create a bridge for your support channel. You'll get a customer_ref (e.g. "support") you use in every API call.
2
Set a webhook URL
Configure the URL where WA Bridges should POST inbound messages. Every message your customers send hits that endpoint as JSON.
3
Process and reply
Parse the webhook payload, look up the customer, route to an agent or bot, and reply via the send API. The whole loop is under your control.
4
Scale across products
Provision multiple bridges — one per product, one per region, one per support tier. All route to the same webhook or different ones.

What you can build

💬
Inbound support
  • Customer sends a question
  • Webhook hits your backend
  • Bot or agent replies
  • Full thread history in your DB
🤖
AI-assisted support
  • Pipe messages to GPT/Claude
  • Auto-triage by intent
  • Draft replies for agents
  • Auto-resolve common questions
🔔
Proactive outreach
  • Follow-up after ticket closed
  • NPS survey via WhatsApp
  • Renewal reminders
  • Onboarding check-ins
📊
Multi-number routing
  • One bridge per product line
  • One bridge per region
  • Route by customer_ref
  • Shared handler or separate

Paste into Claude, ChatGPT, or any AI assistant

Copy this prompt → paste into any AI assistant → get working code in your language.
I'm building a WhatsApp customer support channel using WA Bridges.

My stack: [Express/Node.js — update this to your language/framework]
My setup:
- WA_API_KEY env var has my WA Bridges API key
- WA_WEBHOOK_SECRET env var has my webhook signing secret
- Bridge customer_ref is "support"

I need:
1. A POST /webhook endpoint that receives inbound customer messages
2. Verify the webhook signature using the X-Wa-Signature header
3. Send an immediate acknowledgement back to the customer by name if possible
4. Store the message for later handling (console.log is fine for now)

Please read the WA Bridges API docs and webhook reference before writing:
https://wabridges.com/docs.txt

Write production-quality code with error handling and signature verification.

Why WA Bridges