The before
Sales’ most expensive silent tax
What slow, scattered conversations cost a 10-person sales or admissions team — every month.
average first response to a web lead, among companies that reply at all
of companies never respond to the enquiry they already paid to acquire
drop in odds of qualifying the lead if first contact waits 30 minutes instead of 5
HBR 2011 · InsideSales.com / MIT 2007. Qualification odds: 5 minutes vs 30 minutes.
The reveal
Introducing VartaDesk
Capture from the ad and the site. Engage on WhatsApp, SMS, RCS or Email. Call from the same person record. Hand off when it matters. Write the conversion back to Meta and Google. Measure spend and WhatsApp as different questions — never one blended number.
Maya Tan Singapore · CTWA lead
James Hale London · agent
Amira Al-Mansouri Riyadh · leadChat + Call
One inbox for WhatsApp, SMS, RCS, Email. Phone is a Call on the person — not a fifth chat channel.
Ads in
Lead Ads, CTWA, LinkedIn Lead Gen — no CSV.
Human in control
Bot greets. Agent takes over. Automation pauses.
Ads out
CAPI + Enhanced Conversions when the thread converts.
Honest Insights
Spend ≠ installs ≠ WhatsApp credit. Never summed.
The thread
Click-to-WhatsApp to owned conversation
Maya taps a Meta ad in Singapore. Twelve seconds later she is on WhatsApp. James in London takes the same thread. The click id is first-touch — ready for CAPI when she converts.
Maya · WhatsApp · Singapore · 09:14
Hi — I came from the ad. Is the weekend workshop still open?
James Hale · Agent · London · 09:16
Maya, I can hold 11:00 or 16:30 SGT. Which suits you?
Maya Tan
Singapore · WhatsApp +65
- Source
- Meta Click-to-WhatsApp · first-touch click id
- Pipeline
- Enquiry → Qualified
- Owner
- James Hale · Agent · London
- When she converts
- CAPI Lead Won · optional Google Enhanced Conversions
- Consent
- Reachable on WhatsApp · not opted out
- Call
- Click-to-call · same person · not a new chat
The same person
WhatsApp is the thread. The call sits on the same record.
James does not leave the desk for a separate phone app. Click-to-call uses the team’s RingCentral numbers — 1:1, not a dialer, not a PBX inside the CRM.
Click-to-call
Settings → Voice connects RingCentral. Mapped agents RingOut to Maya’s mobile. Unmapped agents cannot dial. No bulk, no IVR, no embedded softphone widget.
Call log on the rail
Answered, missed, duration — beside the WhatsApp thread. My day surfaces missed calls. Voice is never treated as a messaging channel.
Recording with consent
Company policy plus her opt-in. Audio stays in the tenant store. Play it back at the desk. We never fetch a vendor recording URL.
Person brief
On-demand: what she asked on chat, what the calls show. Optional transcript of kept audio when an admin turns it on. Never auto-sends. Never auto-dials.
James Hale
London · mapped RingCentral extension
- Click-to-call
- RingOut to Maya · +65 · 1:1
- Last call
- Outbound completed · 90s · kept audio
- Person brief
- Messages + call times · optional kept transcript
- Consent
- Recording only if she opted in
How it works
Enquiry to follow-through — in four steps
Your team’s judgment stays. The keyboard work does not. No parallel WhatsApp. No “I’ll log it later.”
Land the lead
Meta Lead Ads, Click-to-WhatsApp, LinkedIn Lead Gen, website, widget, AI assistant — no CSV. One people record, phone-first, click id first-touch.
Reply in seconds
A journey or approved template greets them on WhatsApp (or SMS / RCS / Email) while James is still in another meeting.
The agent stays in charge
One click flips BOT to HUMAN. Automation pauses. James edits, sends, assigns — or click-to-calls Maya from the same record.
Close the loop
Day 1 / 3 / 7, campaigns, Flow Studio. On Won or order: CAPI / Enhanced Conversions. Spend stays on its own tile.
If they can message you, VartaDesk can own the thread. If James needs the phone, the call is on the same person — and still gets out of the way when a person should talk.
The media you already buy
We are built for performance marketers — not as Ads Manager.
Four pipes. Four questions. If a vendor adds them into one ROI number, the dashboard is lying. VartaDesk keeps them apart — and still gets the WhatsApp conversion back to Meta and Google.
Lead Ads · CTWA · LinkedIn
Meta leadgen and Click-to-WhatsApp land as a person in the inbox. LinkedIn Lead Gen Forms too. Idempotent. No CSV import. Click ids stamp first-touch for later write-back.
Paid Media Pulse
What did we spend, and what did Meta / Google say we got? Spend, clicks, CTR, platform-reported conversions. Overlay only — we do not create, edit, or bid campaigns.
Owned-channel conversions
When the WhatsApp thread becomes a Won lead or a confirmed order, tell Meta CAPI (ctwa_clid / hashed phone) and optionally Google Enhanced Conversions. Deduped vs the pixel. Not Adjust’s job.
Internal attribution
Which VartaDesk touch gets credit? First / last / linear. Insights shows WhatsApp credit vs paid spend as two series — never summed, never sent to the networks as a bid signal.
Live product: store census and MMP first-opens on separate tiles — labeled so nobody adds them. Same honesty for ads spend, CAPI, GA4, and journey conversion.
The product
It speaks where they already are — and proves every send.
Same desk in London, Singapore and the Gulf — Alfie Brown, Sophia Taylor, James Wilson on a UK +44 book. Maya’s CTWA thread sits next to them.
Trust
Customer data never crosses a tenant.
Built as production multi-tenant SaaS — isolation is structural, not a policy paragraph. Opt-out is not a suggestion.
Tenant isolation
Every tenant-owned read and write is scoped at the data layer. Agents only see their assigned people and threads.
Secrets encrypted
Provider API keys are AES-256-GCM at rest, never returned to the browser, never written to logs.
Opt-out chokepoint
STOP and per-channel flags gate every outbound message. Campaigns exclude globally opted-out people before enqueue.
GDPR · PDPL · DPDP
Hosted notice, purpose log, preference center, DSAR export and Super-Admin erasure. Call recording only with company policy and their opt-in.
Webhooks you can audit
Inbound signatures verified before the body is trusted. Raw payload stored. Outbound HMAC-signed, SSRF-guarded.
Quotas are real
Plan flags and monthly caps are checked server-side before a send, a bot turn, or a journey step.
The math
Hours returned to selling. Leads you already paid for, recovered.
The personal-WhatsApp way
- First reply waits on whoever saw the form
- Notes vary; half never reach a CRM
- Follow-up is memory and goodwill
VartaDesk
- Bot greets; James takes Maya’s same thread
- One record, one history, one owner — chat and call
- Day 1 / 3 / 7 that pause for people
| Team size | Hours recaptured / mo | Time value / mo |
|---|---|---|
| 5 people | 220 hrs | from $5,500 |
| 10 people | 440 hrs | from $11,000 |
| 25 people | 1,100 hrs | from $27,500 |
| 50 people | 2,200 hrs | from $55,000 |
Assumptions, labeled as such — not a customer case study: 2 hours/person/day × 22 working days × $25 fully loaded hour. HBR: firms contacting within an hour were ~7× as likely to qualify as those waiting another hour.