Source report
WhatsApp leads are counted by source beside web forms and referrals.
Read more about Source report
See which sources bring leads and which of them close, with WhatsApp leads counted alongside web forms and referrals.
Each WhatsApp lead is written to Desk or your CRM when it is captured.
Without sync, WhatsApp leads miss the pipeline review. We write each one to the CRM and keep its owner and status current.
If WhatsApp leads live only in WhatsApp, the monthly pipeline review misses them. Sales heads end up asking reps to copy chats into the CRM by hand, which happens for some leads and not others. We connect WhatsApp CRM to Desk or your CRM so the lead is written when it is captured, and its owner and status stay current as the conversation moves.
Desk is CyberFreezeDev's own CRM and project management product, with paying users, so it is the simplest fit. It is not required.
Desk's own lead model, filled from the WhatsApp side.
| WhatsApp CRM | Desk |
|---|---|
| New chat from an unknown number | A lead (a person), optionally filed under a company account |
| Where the chat came from | Lead source, such as an ad, the website form or a referral |
| Qualification answers | Lead notes and your custom fields |
| AI temperature | Hotness, from 1 (cold) to 5 (hot) |
| Assigned rep | Lead owner |
| Follow-up due | A task for the owner |
| Deal worth pursuing | An opportunity in your pipeline |
Before creating a lead, Desk runs a duplicate check on email and phone, with +91 and a 0 prefix normalised.
WhatsApp leads are counted by source beside web forms and referrals.
See which sources bring leads and which of them close, with WhatsApp leads counted alongside web forms and referrals.
Desk's monthly review includes the WhatsApp pipeline.
Desk's monthly review includes the WhatsApp pipeline instead of leaving it out.
A booked call or site visit lands on the rep's Desk calendar.
When a WhatsApp lead books a call or a site visit, it is a meeting on the rep's Desk calendar.
Won deals carry on as delivery work in Desk's projects.
When a deal is won, Desk's project side holds the delivery work, under the same login.

For another CRM we build the link through its API, usually in n8n, after checking which fields its API allows.
If your team already runs a different CRM, we build the integration through that CRM's API, usually as an n8n workflow you can see and change. The same idea applies: one record per person, the source kept, the owner and status current. We check what the CRM's API allows before promising a field mapping. For a broader CRM build, see WhatsApp CRM automation service.
No. Desk is the simplest fit because we build both, but we connect to other CRMs too. Ask for a demo of either.
No. Desk checks for duplicates on phone and email before creating a lead, and a returning number is matched to its existing record.
Ask us in the demo. We show what the current link between the two looks like rather than describe it here.
Last updated