Last updated: 23 May 2026.

A 3CX missed-call workflow fires automatically when a call rings out unanswered on the PBX, pushes the event into the CRM in real time, and runs a follow-up sequence (text, email, task, escalation) against the matching contact. The integration relies on the 3CX Call Control API event stream documented in the 3CX API reference and a CRM that accepts a webhook or API trigger. The follow-up fires within seconds, not the next morning, which is why response time matters.

Why missed calls cost more than the call itself

Research from Harvard Business Review found that companies contacting a new lead within an hour were nearly seven times more likely to have a qualifying conversation than those who waited longer, per "The Short Life of Online Sales Leads" (2011). Subsequent lead-response research from Velocify summarised at leadresponsemanagement.org found odds of contact dropping sharply after the first five minutes.

The numbers move in one direction: the faster the follow-up, the higher the conversion. A missed call that gets a return text within sixty seconds reads as attentive. The same missed call returned the next morning reads as another business chasing the same deal alongside three others.

What "missed-call workflow" means on 3CX

3CX exposes three call states that matter to a CRM bridge: started, ended, and unanswered. The unanswered state (missed call) is its own event with its own payload. The bridge listens for it, looks up the contact by inbound number, and posts a trigger event into the CRM.

From there the CRM workflow takes over. The bridge is the trigger; the workflow logic is the CRM's job. That separation is on purpose: the same missed-call event can drive a sales playbook on one team and a support escalation on another, without changing the bridge.

Manual missed-call follow-up vs an automated workflow

Bottom line: manual works when call volume is low and your team is patient. Automated wins as soon as call volume is consistent or the cost of a missed lead is more than a few minutes of work.

Who manual is best for: very small teams under ten calls a day, where the person who answers the phone also runs the workflow personally, and where the personal touch of a hand-typed reply earns more than speed.

Who automated is best for: any team where missed calls happen during meetings, after hours, or in a queue large enough that the next-morning catch-up is unreliable.

How to set up a 3CX missed-call workflow in your CRM

The sequence below works whether you build the trigger yourself or install a marketplace app. The steps are the same; only the listener changes.

1. Confirm 3CX is firing missed-call events. Open the 3CX call history, place a call to an unanswered extension, hang up, confirm the event appears with status "missed" or "no answer". This is the source signal.
2. Set up the bridge to listen. A marketplace install handles this step. A custom build needs to subscribe to the 3CX Call Control API event stream and filter on the missed status.
3. Map every 3CX inbound number to a CRM source list. A call to the main sales line should fire the sales workflow, not the general workflow. The mapping table sits in the bridge, not in 3CX.
4. Design the workflow in the CRM. Most teams start with two paths: in-hours fires an SMS within sixty seconds; after-hours fires an email and a task for the next morning. Branch on hours of operation, not just contact owner.
5. Add a check for repeat-misses. A contact that has been missed twice in a week needs escalation, not another auto-text. Pull a custom field into the workflow that counts missed calls and escalates after the second one.
6. Test with a real number. Call the inbound line from a phone that is not in the CRM, let it ring out, watch the CRM create a new contact and fire the workflow. Then call again from a number that is in the CRM and confirm the workflow fires against the existing contact.
7. Monitor the first week. Log every workflow firing, compare against the 3CX missed-call count, find the gap. Most gaps come from two things: missing extension mapping and unnormalised phone numbers.
8. Tune the timing. Sixty seconds is the default for in-hours SMS because it reads as "we just saw you". Three minutes feels slow; ten seconds reads as a bot. Adjust to fit how your team answers calls.

What a working missed-call workflow looks like in practice

A common pattern we see on the Connect Zero base licence, with three branches.

• In-hours, first miss. Bridge fires the unanswered event. CRM workflow sends an SMS to the caller within sixty seconds, content along the lines of "Sorry we missed you, name calling from agency. Quick reply with what you need and we'll call straight back." Workflow creates a follow-up task for the contact owner.
• In-hours, second miss in seven days. Same trigger, different branch. Workflow escalates to the team manager via internal notification, tags the contact repeat-missed, opens a task for the manager to call back personally.
• After-hours, first miss. No SMS (set quiet hours). Workflow fires an email acknowledging the call and a task for the morning standup. Tag the contact after-hours-callback so it surfaces top of the queue.

You can read about the agency rollout pattern, where the same workflow rolls out across sub-accounts, on the for-agencies page.

Three patterns to avoid

Three patterns we see teams build, regret, and unwind.

• Firing the SMS before the missed-call event settles. 3CX briefly reports a call as missed in the seconds between the rings and the voicemail handoff. If the bridge fires too eagerly, the caller has already left a voicemail by the time the SMS arrives. Wait for the final settled event.
• Sending the same auto-reply to every caller including existing customers. A logged-in customer who calls support and gets a generic "leave your details" SMS reads as a bot. Branch on existing-contact-with-open-deal versus new-inbound-number.
• Ignoring the recording context. A missed-call workflow that fires without checking whether a voicemail was left often duplicates the customer's effort. Read the voicemail flag from the call event and skip the SMS if the customer already left a message.

Measuring whether the workflow is working

A workflow that fires is not the same as a workflow that converts. Three things to measure in the first month after switching from manual to automated.

• Reply rate. Of the missed calls that triggered an auto-SMS, how many got a reply? The baseline for a sensible reply ("Yes please call me back" or similar) on a sales line tends to sit in the 15 to 25 per cent band when the message is short and personal. A reply rate under 10 per cent is a sign the message reads as a bot; rewrite it.
• Time-to-callback. When a reply comes in, how long until a human calls back? The automation closes the gap from "next morning" to "within sixty seconds" on the outbound side. The inbound side (your team actually calling) is the new bottleneck. Track it.
• Lost-lead recovery rate. Of the missed calls in a given week, what proportion turned into a conversation within 24 hours? Compare month-over-month after the workflow is live to see whether automation moved the needle.

Most teams find the first month surfaces a problem they did not see before: the workflow fires, the customer replies, and nobody on the team has the callback task in their queue. The fix is on the CRM workflow design, not the bridge. Add a task creation alongside the SMS and assign it to the current on-call rep.

How the workflow scales across an agency's sub-accounts

For agencies running the bridge across multiple CRM locations, three patterns hold up at scale.

• Centralised workflow, decentralised mapping. Build the workflow once at the agency level (template), provision it into each sub-account, let each sub-account override the message text and the operating hours. The bridge handles the mapping per location.
• Tag the source. When the trigger fires, the contact gets a source: missed-call tag. Downstream reporting at the agency level can roll up missed-call recovery rates across all sub-accounts without each sub-account writing its own report.
• Cap auto-SMS volume per number. A repeated dialler that hits the same inbound line three times in a minute should not trigger three auto-SMS. The workflow needs a rate limit. Connect Zero exposes the call history in the trigger payload so the workflow can read the recent count and skip the SMS on duplicate misses.

What the bridge needs to be in the base licence

A useful missed-call workflow needs the trigger plus enough write-back to update the CRM as the workflow runs. Premium tiers that lock either behind upsells make the workflow brittle. With Connect Zero, the missed-call trigger and the Update Call Record action are both in the base licence, alongside the call-started and call-ended triggers. You can see the features behind the bridge for the full event list.

Frequently asked questions

How fast can a 3CX missed-call workflow fire?

The trigger fires within seconds of 3CX reporting the call as missed. The CRM workflow then runs against that trigger. End-to-end, an SMS reply lands within ten to sixty seconds depending on the CRM provider and the SMS gateway latency.

Does the workflow work after hours?

Yes, and most teams want it to behave differently after hours. Branch the workflow on hours-of-operation so the after-hours path sends an email and creates a morning task instead of a late-night SMS that reads as a bot.

Can the missed-call workflow update the existing contact, or only create a new one?

Both. If the inbound number matches a contact, the workflow runs against that contact and posts the missed event on its timeline. If no contact matches, a new one is created with the inbound number and the workflow runs against the new record.

What 3CX licence is needed for missed-call workflows?

3CX v18 or later with the Call Control API enabled, and an API user with the Reports User role. The Recording Manager role is not required for missed-call workflows specifically (no recording is generated on a missed call), though most teams want both roles for the broader integration.

Does the workflow fire on internal calls between extensions?

No, by default the bridge filters out internal-to-internal calls because they do not correspond to a CRM contact. Inbound calls from external numbers and outbound calls from extensions are the two paths that hit the workflow.

Can I prevent the workflow firing on calls from numbers that are already in an open deal?

Yes, branch the workflow on deal status. The bridge posts the missed-call event with enough context for the CRM workflow to read the contact's open deals and skip the auto-reply if one is active.

What happens if the caller leaves a voicemail?

The call event carries a voicemail-present flag. Most workflows skip the auto-SMS if the customer left a voicemail and instead create a task to listen and call back, because the customer has already said what they needed.

Are missed-call workflows a premium feature in Connect Zero?

No. The missed-call trigger plus the call-started and call-ended triggers are in the base licence at USD 39 per location per month. Write-back via the Update Call Record action is also in the base licence. Detail on what teams get out of the bridge and the base-licence feature list.

Connect Zero is built by Auswide IT, an Australian 3CX VAR partner deploying 3CX across South Australia. Last updated 23 May 2026.