Notes from building customer conversations
What we have learned shipping AI agents on WhatsApp and in-product chat: what the platform actually bills you for, where automation earns its place, and the engineering that keeps it boring in production.
How to move a customer support workflow from n8n to RoutMe
A step-by-step migration of a WhatsApp support workflow from n8n to RoutMe Flows: node mapping, the agent step, connectors and a checklist to cut over safely.
Jesbin James
Engineering
- Product5 min read
n8n vs RoutMe for customer conversations: when to use which
n8n is a general workflow engine and RoutMe is built for customer conversations. Here is when each is the right tool, and how teams use both together.
VRVinita Rathi
Product and conversation design
- Playbooks5 min read
Do you still need Zapier for WhatsApp customer support?
Probably not for the support part. See what a Zap does in a WhatsApp support setup, what RoutMe Flows cover instead, and where Zapier is still the right tool.
VRVinita Rathi
Product and conversation design
- WhatsApp5 min read
WhatsApp without Twilio: how the Cloud API connection works
You can run WhatsApp support without your own Twilio account. Learn how Embedded Signup connects the Cloud API directly, and what a BSP adds that you may not need.
SMSushma Madan
WhatsApp platform
- WhatsApp5 min read
Twilio WhatsApp alternatives: Cloud API, BSP or managed agent
Three ways to run WhatsApp support besides your own Twilio build: the direct Cloud API, another BSP, or a managed agent platform. Pros, cons and who each suits.
SMSushma Madan
WhatsApp platform
- Playbooks5 min read
Replace the Zap: a where-is-my-order automation, no glue code
Build a where-is-my-order WhatsApp flow without Zapier or glue code. Trigger, order lookup tool, reply, and a fallback to a person, step by step in RoutMe Flows.
VRVinita Rathi
Product and conversation design
- Engineering5 min read
The hidden maintenance cost of a self-hosted n8n WhatsApp bot
A self-hosted n8n WhatsApp bot works on day one. Here is the ongoing work it creates: hosting, upgrades, webhooks, templates, retries, monitoring and prompt safety.
JJJesbin James
Engineering
- Playbooks5 min read
Appointment reminders and follow-ups without Zapier
Send WhatsApp appointment reminders and follow-ups with RoutMe Flows: an external event trigger, an approved template, wait steps and a reply path. No Zapier needed.
VRVinita Rathi
Product and conversation design
- Playbooks5 min read
From DIY chatbot stack to managed agent: a migration checklist
Moving off an OpenAI, n8n and Twilio chatbot stack? This checklist covers inventory, WhatsApp number, templates, data access, prompts, handoff, testing and cutover.
JJJesbin James
Engineering
- Engineering5 min read
Connect your systems without glue code: MCP, APIs, databases
How RoutMe reaches your data without glue code: MCP servers, your own APIs and read-only database views. What each is, when to use it and how to keep it safe.
JJJesbin James
Engineering
- Playbooks2 min read
Where-is-my-order is a lookup problem, not a conversation
Most where-is-my-order tickets ask for a fact that already exists in a system. That makes them the best first job for an AI assistant, if the lookup is safe.
VRoutMe team
Product and engineering
- Engineering1 min read
Read-only is a property of credentials, not of prompts
Telling a model not to change anything is a request. Giving it credentials that cannot change anything is a guarantee. Here is how to build the second.
VRoutMe team
Product and engineering
- Product1 min read
Adding AI chat to a Shopify store without an app
RoutMe has no Shopify app, so the pattern is a script snippet in your theme plus your own read-only tools. Here is what that involves and what it does not.
VRoutMe team
Product and engineering
- WhatsApp3 min read
WhatsApp per-message pricing, explained without the spin
Meta bills WhatsApp per message, not per conversation. Here is what that changed, what became chargeable in October 2026, and how to estimate a bill before you send anything.
SMSushma Madan
WhatsApp platform
- Playbooks3 min read
Decision trees don't survive contact with customers
Every scripted bot works in the demo and falls over in production. The failure is structural, not a matter of adding more branches, and the fix is narrower than replacing the whole thing with an LLM.
VRVinita Rathi
Product and conversation design
- Engineering3 min read
Giving a support agent your data without giving it your database
An agent that cannot read your systems can only apologise. Here is how to expose real data through MCP tools with a boundary you can actually defend in a security review.
JJJesbin James
Engineering
- WhatsApp3 min read
Why your WhatsApp templates keep getting rejected
Template review failures are boringly predictable. The same handful of mistakes account for most of them, and all are fixable before you submit.
SMSushma Madan
WhatsApp platform
- Playbooks3 min read
The handoff is the part everyone gets wrong
Most AI support deployments are judged on the conversations the agent could not finish. A good handoff is a design problem, not a fallback.
VRVinita Rathi
Product and conversation design
- Engineering3 min read
Your webhook will be delivered twice. Plan for it.
Duplicate deliveries, out-of-order events, and the 20-second timeout are not edge cases on the WhatsApp Cloud API. They are Tuesday. Here is the handling that keeps them boring.
JJJesbin James
Engineering
Who writes here
- V
RoutMe team
Product and engineering
Practical guides from the people who build RoutMe, with every product claim checked against what is live today.
- JJ
Jesbin James
Engineering
Writes about integrations, agent tooling, and the parts of the WhatsApp Cloud API that only show up in production.
- VR
Vinita Rathi
Product and conversation design
Writes about where automation belongs in a support conversation, and where it does not.
- SM
Sushma Madan
WhatsApp platform
Writes about templates, pricing, and getting things approved on the WhatsApp Business Platform.