We added WhatsApp to our AI receptionist this week. The integration was the easy bit.

Spending too much time with our UK customers has led me to this conclusion.

Nine times out of ten when you call a plumber or electrician in this area they will say Send me a WhatsApp. Salons use WhatsApp to verify appointments. quotes. Instead of using email contractors are hashed out on WhatsApp. Additionally WhatsApp is the source of half of the invoices we see in the wild.

That is the current state of British service companies. With over 40 million users in the UK WhatsApp is essentially the business inbox for owner-operators.

In spite of this practically all of the AI receptionists that we face are voice-only. Numa Rosie Goodcall and Smith Dot AI. Make a call and stop. The thousand is the next layer that lies beneath them. Every week voice-agent platforms are shipped (youve all seen the threads for Vapi Retell Synthflow and Bland).

Jodie and I never intended for that to happen. From the beginning our goal was to become the complete inbound and response layer for small businesses rather than just another voice agent. calls first since thats the location. The majority of jobs are still either dead or alive. Then all the other channels that a customer actually uses such as LinkedIn Facebook Messenger SMS WhatsApp and email.

Replacing the receptionist is the goal. One thing unites the lead chaser the email triage and the WhatsApp respondent. We therefore launched WhatsApp into Jodies private beta this week.

The business API integration was simple. I honestly didnt anticipate the difficult part until we were actually in it.

Every call has an end. Chat does not.

You can tell a phone call is finished when it ends. They both hang up the transcript is final and the agent completes its end-of-call procedures. Thanks see you Tuesday. Schedule the event. Fire it. SMS verification. Write to the CRM. Send the owner a ping. a spotless line.

There is none of that in a WhatsApp thread.

When a customer messages What do you charge to unblock a sink? Jodie responds. After seven minutes of silence they ask Okay and how soon could you?. Come. The same dialogue? They become silent for an hour. Two days later is the conversation still the same? The same talk or a new position?

When then does Jodie? Determine whether the lead is qualified and schedule it. Please send the confirmation. Refresh the CRM. escalate the matter to the owner. Give up politely and return the next day.

The decision tree is essentially free for a voice agent. Every one of those steps in chat requires a clear policy because the conversation never truly ends.

Things we are now. handling. Timeout-driven state transitions: what should be done after N minutes of silence? Every new message (continuation or new job) is intended to be reclassified. Partial-information reservations (we have a name and a general job description but we dont yet know the address do we still have the slot? Soft escalation rules (theyve asked for a price three times its time to annoy the owner). Cross-channel deduping (one or two customers DM us on WhatsApp and then call the same number ten minutes later).

The casual async drip-feed style of customer behavior that makes WhatsApp so great for service businesses is precisely what makes the agent layer significantly inferior. tougher than calls. fewer natural endpoints a larger surface area and more states to monitor.

Were currently working through it with customers in the private beta. If you own a UK service company and would like to participate DM me or leave a comment with your trade and location.

From the IH perspective there are a few things Im interested in.

How are you handling when has this thread ended if youve shipped chat agents (proper agents not just bots)? Is it due to pure timeouts intent classifiers or a combination of the two? misfires more frequently than Id like.

particularly the founders of the UK. What percentage of your incoming calls are going to WhatsApp phone or email these days? Based on my intuition WhatsApp has surpassed phone for service-oriented SMBs. last two years but aside from what I see in our data I have nothing to support that.

Aside from voice WhatsApp SMS email Messenger and LinkedIn is there another load-bearing inbound channel that were missing? Im curious if theres a vertical-specific one. dozing off.

Building Jodie at heyjodie.com if anyone wants a look. Im always willing to exchange notes with those developing multi-channel agents.