Missed Call to CRM: Every Missed Call a Lead

Short answer: set a webhook on your missed call number pointing to your CRM. With Edesy CRM it takes a few minutes: create a Custom webhook lead source, paste its URL into the missed call portal, give a test missed call, and map data.from to phone. Every missed call after that becomes a lead. If you already use another CRM, we connect it for you, usually within a few days, using our signed webhook and REST API.

Get a Missed Call Number and connect it to a CRM on day one.

Why a CRM, Not Just a List

A missed call gives you a phone number and a time. Turning that into revenue usually needs:

• an owner for each lead
• a callback, often several
• notes from the conversation
• a stage (new, contacted, qualified, visit booked, won, lost)
• a source, so you know which ad worked

A CSV can hold the first fact. A CRM holds the rest, and stops two executives from calling the same person ten minutes apart.

The Two Paths

The CRM integration overview lists all supported setups.

Which path should you pick?

• No CRM today, or leads live in WhatsApp chats and notebooks: Path A. It is free to start and live the same day.
• A CRM your sales team already works in every day: Path B. Do not make the team check two systems; bring the missed calls to where they already work.
• An in-house system or ERP: Path B, with our team or your developers using the webhook and API.
• Unsure: start with Path A on one campaign number; moving later only means changing the webhook URL.

Path A: Edesy CRM, Step by Step

1. Create the lead source in Edesy CRM

Sign in to crm.edesy.in (same Edesy login as the missed call portal). Go to lead sources and add a Custom webhook source ("any tool that can POST JSON"). The CRM generates a unique URL for that source. Treat the URL like a password: anyone with it can create leads. You can rotate it if needed.

2. Paste the URL into the missed call portal

In the missed call portal, open webhook settings, add a subscription for the call.missed event and paste the CRM URL. Save.

3. Send a first event

Give a missed call to your number from any phone. The event reaches the CRM and shows up in the lead source's activity view.

4. Map the fields once

The CRM flattens nested JSON into dot paths, so you can pick fields from the first event:

Save the mapping. From then on, each missed call creates a lead with the caller's phone and the campaign name. If an event cannot be mapped, it is acknowledged and shown in the activity log rather than retried endlessly, so you can fix the mapping and carry on.

5. Assign and work the leads

Set up assignment (round robin or by source), stages and follow-up tasks. If your team calls from Edesy's voice products, calls from the CRM keep the history in one place.

Path B: Any CRM, Connected for You

Salesforce, Zoho CRM, HubSpot, LeadSquared, Freshsales, Pipedrive, Bitrix24, Odoo or a CRM your own team built: the mechanism is the same. Our signed call.missed webhook feeds a small integration that calls your CRM's API to create or update a lead, using the caller's phone as the key and the number name as the source.

We set this up for you, usually within a few days. There is no marketplace app to install; tell us:

1. Which CRM and edition you use
2. Which object leads should land in (lead, contact, enquiry)
3. Which fields hold phone, source and owner
4. How you want repeat callers handled (new lead, or a task on the existing record)

CRM-specific notes are in how to get missed call leads into Zoho, Salesforce or HubSpot, and there is a custom CRM page for in-house systems.

If you have developers

You can also build it yourself: receive the webhook, verify the HMAC signature, dedupe on call_sid, and call your CRM's API from a background job. See missed call webhook best practices for the details.

Repeat Callers and Duplicates

Two different things look like duplicates:

In Edesy CRM, give two missed calls from the same phone during setup and check how the second one appears, then decide on your team's rule. In other CRMs, enable duplicate rules on phone, or let the integration search before creating.

Measuring Campaigns in the CRM

Once phone_number_name lands in a source field, every report in the CRM becomes a campaign report:

• leads per source per week
• contact rate per source
• qualified leads and wins per source

Compare this with the missed call dashboard's unique callers per number to see where leads drop off between capture and first contact.

Cost

Events that cannot be delivered after all retries are not charged. Full details on the pricing page.

Common Setup Mistakes

• Mapping the wrong number. data.to is your own number; data.from is the lead. Map data.from to phone.
• Skipping the source mapping. Without phone_number_name in a source field, all leads look the same and you lose campaign reporting.
• Testing with a teammate's phone, then forgetting it. Delete or mark test leads so they do not skew reports.
• Sharing the CRM webhook URL widely. It works like a password. Rotate it if it leaks.
• No owner rule. A lead that lands in the CRM with no owner is as lost as one in a spreadsheet. Set round-robin or source-based assignment before going live.
• Paying for the webhook but working from CSV. If nobody uses the CRM, switch back to the free CSV mode until the team is ready.

Get Started

Get a Missed Call Number, then either connect Edesy CRM on the free plan or tell us which CRM you use and we will connect it.