Conversation OS
Start free
All posts

Guide

Click-to-call on the person — not a second phone system

VartaDesk

Click-to-call CRM: log the 1:1 call on the same person as WhatsApp. Kernel voice, not a pack, not a PBX, not robocalls — RingOut from the desk beside the thread.

A phone next to a laptop — the call has to land on the same person as the WhatsApp thread, or the desk is lying.
A phone next to a laptop — the call has to land on the same person as the WhatsApp thread, or the desk is lying.

Teams searching click to call CRM usually do not want a call-centre stack. They want this: the buyer is on the person rail, WhatsApp is in the inbox, and the agent can ring their mobile from the desk so the call is logged next to the thread — not in a personal recents list.

In VartaDesk that plane is kernel voice: a Call row on the person, beside Conversation. It is not a messaging channel, not a catalog pack, not a PBX, and not a bulk dialer.

What click-to-call is here

  • 1:1 RingOut from the mapped agent to the person’s mobile (RingCentral JWT connect today; other CTI adapters exist on the same seam).
  • Inbound / CDR on the same person so “did we talk?” is a fact, not a rumour.
  • Person brief can read call disposition and duration. Kept-audio transcription in brief is off unless an admin turns it on — and it never fetches a vendor recording URL.

What it is not: hunt groups, IVR, presence, meetings, RC SMS, robocalls, selling DIDs, or treating voice as another chat channel so campaigns can “just send calls.”

Notes on a laptop after a conversation — the CDR belongs on the person, not in a spreadsheet of ‘called’.
Notes on a laptop after a conversation — the CDR belongs on the person, not in a spreadsheet of ‘called’.

Why the call has to sit on the person

Showrooms, clinics and brokers already call. They do it from a mobile while WhatsApp lives somewhere else. The next agent then asks for the same details again.

Identity is phone-first. If the DID and the WhatsApp number resolve to one person, the click-to-call button is useful. If they do not, you will log a call on the wrong record — worse than not logging.

Consent still gates outbound: opt-out and voice-specific blocks are enforced server-side. A campaign must never dial.

Settings → Voice, not a pack tile

Admin path is Settings → Voice: connect, pull numbers, map desk users to extensions. Agents do not get the JWT. Unmapped agents cannot click-to-call once RingCentral is connected — that is intentional, not a bug.

Human takeover still pauses messaging journeys. A live call does not resume a broadcast. Brief is on-demand; it never sends and never dials.

A desk telephone — we log the 1:1 call. We do not become the office PBX.
A desk telephone — we log the 1:1 call. We do not become the office PBX.

Pair it with the channel they already use

Click-to-call does not replace WhatsApp. Most “can you call me?” threads should stay on chat until a human decides to ring. The CRM’s job is that the ring, the WhatsApp, and the SMS reminder are one person.

Related: WhatsApp Business App vs CRM when the number is still a handset; Wati vs VartaDesk when you already have an API inbox and need the desk; industry records on real estate and dealerships where a missed call after a visit is expensive.

First week

  • Connect Voice as admin. Map extensions by email. Do not skip the map.
  • Click-to-call from one person rail. Confirm the Call row appears beside the thread.
  • Leave transcription off until you have a retention and consent story.
  • Do not import a call-centre campaign list. This is 1:1.

See the product or start free. The first win is the call that is already on the person when the next agent opens the same buyer.

Product Start freeRSS