Field notes
from the inbox.
Playbooks, comparisons, and the occasional strong opinion — from the team building the AI employee that answers at 3 a.m. Written for the people who actually run the shift.
How to move WhatsApp support from reactive to operational
Most teams bolt WhatsApp on top of their helpdesk and call it a day. That's the expensive way. Here's the playbook we use with 40-location retail groups to turn it into the highest-SLA channel they have.
All notes.
Showing 15 of 15Lead follow-up on WhatsApp: how to stay in touch without being pushy
Most leads aren't lost to a competitor. They're lost to silence. How to follow up on WhatsApp without being pushy, within Meta's rules, and without a salesperson remembering to do it.
How car dealerships should answer WhatsApp leads at 11 p.m.
Ad enquiries arrive at 11 p.m., on four channels, in three languages. The dealerships that win them aren't faster salespeople — they've redesigned the first five minutes.
12 customer service reply templates written for chat
Twelve reply templates for the conversations every support team has every day — complaints, delays, refunds, thank-yous — written for chat, not email, with notes on when not to use them.
WhatsApp template messages and pricing in India: the 2026 guide
Since July 2025 WhatsApp charges per message, not per conversation. Here's how template categories, the free windows, India's rates and the INR billing deadline actually work.
WhatsApp Business app vs. API: which one does your business need?
The free app runs a shop. The API runs a team. Here's where the line falls, what coexistence changed in 2025, and how to tell which side of it your business is on.
AI vs. human support staff: what actually saves money
The usual pitch says AI replaces headcount. The evidence says something narrower and more useful. Here's how to price an AI agent against a hire, using public numbers you can check.
How to automate customer support with AI, without annoying anyone
Automating support isn't about replacing your team with a bot. It's about deciding which conversations a machine should own, which it should hand off, and how to tell the difference. A practical guide.
Writing system prompts your customers won’t notice
The best AI agent is the one nobody writes a complaint tweet about. A practical template for voice, guardrails, and when to hand off.
Unified inbox vs. a pile of Slack channels
An honest look at when a helpdesk is overkill, when Slack falls apart, and the threshold (roughly 40 conversations/day) where a unified inbox pays for itself in a week.
We audited 1.2M support conversations. 68% were routine.
A breakdown of what actually happens in customer support inboxes — by intent, by channel, by hour — and what that means for where to point the automation.
A month with an AI employee: one retailer’s unvarnished diary
Week one was rough. Week three surprised everyone. A candid operator’s log from a 42-location automotive group during their first month on Cloodot.
How we route the messy messages to a human
The handoff is the hardest part. A peek at our confidence model, the phrases that always escalate, and why politeness is a terrible signal.
Multilingual by default: designing for 40+ scripts
RTL is easy. Indic shaping, cultural register, and Malayalam nuance are not. Lessons from shipping in Kochi for the rest of the world.
The six integrations to wire up in week one
Shopify, Salla, HubSpot, Attio, your order API, and whatever holds inventory. A practical order-of-operations for new Cloodot deployments.
Against the chatbot. For the team member.
A short essay on why 'chatbot' is the wrong mental model — and why framing AI as a teammate, not a tool, changes how everyone builds with it.
A short letter.
Every other Thursday.
One piece on conversational AI, one operator's playbook, and something from the build. No newsletter-industrial-complex. Unsubscribe in one click.