CRM Integrations
JustDial CRM Integration: Capture, Assign and Follow Up on Every Enquiry
A lead appearing in your CRM is only the start. Check the source, owner and next action before calling the integration ready.
A new JustDial enquiry arrives while your team is visiting a customer. Someone forwards it to a group. Later, two salespeople call the same buyer while another enquiry receives no reply. The problem is not necessarily a shortage of leads. It is the gap between receiving an enquiry and giving someone responsibility for it.
JustDial CRM integration should close that gap: capture the enquiry, preserve its details, place it in the right pipeline and make the next action visible. Here is how to check that the process actually works.
Agree on the destination before connecting the source
Choose a pipeline, starting stage and ownership rule. A kitchen renovation enquiry should not disappear into a general list that nobody reviews. Decide who covers each service area and who handles enquiries when the usual salesperson is unavailable.
Write a simple acceptance rule: “A new eligible enquiry appears in the agreed pipeline with its source, contact details and a clear person responsible for follow-up.” A connection status alone does not prove this.
How JustDial setup works in SHVYA
- Open Connect Hub and request JustDial setup.
- The SHVYA team configures the destination and generates your organization’s private webhook URL.
- Share that URL with your JustDial account manager or support contact for lead-push configuration.
- Confirm the delivery method and sample fields for your advertiser account.
- Validate a real incoming enquiry in the integration event log and CRM.
Do not publish the webhook URL in a screenshot or blog comment. It belongs to your connection. JustDial configuration can vary by account; there is no reason to assume that every advertiser sees the same self-service setup screen.
Check these fields on the first enquiry
| Field | What to verify |
|---|---|
| Buyer name and phone | The contact is usable and the country code is correct. |
| Category and location | The salesperson can understand the requested service and area. |
| External enquiry ID | The received event can be traced during troubleshooting. |
| Source and destination | JustDial attribution and the intended pipeline are visible. |
| Owner and next action | Someone knows what to do and when. |
SHVYA handles repeated JustDial lead IDs as retries. A new enquiry ID with the same normalized phone can update the existing lead rather than creating another contact, while preserving its current pipeline stage. This is useful, but the team must still read the new requirement instead of assuming it is an accidental repeat.
When an enquiry is missing, trace one example
Start with the enquiry time and external ID. Ask whether JustDial sent it, whether SHVYA received an event, whether that event succeeded, and where the lead now appears. Search by normalized phone as well as name. An updated existing lead can look like a missing new lead if you only inspect the newest records.
If no event arrived, check the provider configuration. If an event failed, inspect its recorded reason. If it succeeded, check destination filters and assignment. Avoid repeatedly reconnecting everything before identifying which step failed.
Make the first follow-up specific
Hello, this is the team at [business]. We received your enquiry about [service]. Is the work for a property in [area], and what would you like help with first?
Adapt that opening to the actual enquiry and permitted contact channel. Do not assume a marketplace enquiry grants permission for unrelated campaigns. For buyers who need a quote, use our quotation follow-up examples. If you also buy marketplace leads, compare the process with our IndiaMART integration guide.
Bring one enquiry to your setup discussion
Book a JustDial workflow discussion with SHVYA. Bring a redacted sample enquiry and your assignment rules. The useful outcome is a clear path from source to owner to next action, with a way to investigate exceptions.
