Case study

Chat that converts, measured.

A WhatsApp CRM case study

A business running Click-to-WhatsApp ads needed more than a chat app. Sales closed in conversations, the team was growing, and Ads Manager could not see which chats came from ads. This is the system I built for them, phase by phase.

Client details kept private. No names, screenshots or numbers.

Delivered in phases06
Channels connected03
Calls required00
Everything in writing100

The problem

Three things were holding the business back at once.

01

Chats were not attributed

Sales closed in WhatsApp, but Ads Manager had no way to know which conversations started from an ad, so the ad spend could not be judged.

02

One number, a whole team

Several agents needed to handle the same WhatsApp number, with no clear way to split, tag or track who handled which lead.

03

Nothing was measured

There was no record of response times, lead sources or outcomes, so the business was running on guesses.

What I built, phase by phase

Delivered in stages, each one tested and signed off before the next began.

I

Attribution foundation

Captured ctwa_clid from the first message of every ad-driven chat and stored it with the lead, so later sales could be tied back to the ad.

II

Conversions API events

Sent Purchase events to Meta through the Conversions API for business messaging, with the right action source, channel and dataset, verified with test events.

III

Shared team panel

A custom Cloud API panel with a shared inbox, lead tags, status, replies to specific messages and a clear view of each conversation.

IV

Lead automation

New chats became leads automatically, matched to the right record, with duplicate numbers prevented and ad leads linked to their source.

V

Broadcast and reminders

Approved template broadcasts to many contacts within Meta's rules, plus follow-up reminders so no lead was left waiting.

VI

Dashboard and tags

A lead dashboard with countdowns, filters and tags, so the team could see sources and act on time.

Everything that shipped

The full build, delivered feature by feature across the project.

Cloud API and messaging
WhatsApp Cloud API setup Webhook verification Message templates Real-time inbox Reply to a specific message Photo and media send Voice notes Drag and drop upload Sticker support 24-hour window handling Graph API version update
Leads and team
Shared team inbox Agent assignment Auto lead creation Duplicate prevention Lead tags and status Unread-only filter Lead search Phone normalization Facebook ad label
Attribution and growth
ctwa_clid capture Conversions API Purchase events Correct dataset routing Template broadcasts Bulk photo send with catalogue Welcome and away messages Business hours logic Lead dashboard and KPIs

How the work was run

The same way I run every project.

Written and async

Every scope, decision and handover was in writing. No calls at any stage, start to finish.

Verified, not assumed

Conversions API changes were tested with real test events before going anywhere near live sales.

Built from scratch

Custom code for this business, not resold software, so it fit their process rather than the other way round.

Documented handover

Written notes on what was built and where, with ongoing maintenance available afterwards.

What the business has now

A single place to run every WhatsApp conversation, a team that works from one number, and sales from chat that can finally be connected back to the ads that started them. The setup is in place and verified with test events, so the business can measure what Ads Manager was never able to show before.

Want something similar?

Describe your WhatsApp setup in a few lines. You get a written plan and a quote, with no calls.