TL;DR

Missed-call SMS automation is one of the highest-leverage workflows you can build on 3CX. Median recovery rate is 22 percent when the SMS fires within 60 seconds; 11 percent after 5 minutes. Inbound-heavy service businesses (trades, real estate, medical) see the highest uplift.

2026 Q2 measurements

2026 Q2 update. Missed-call workflow telemetry from 2026 Q1 across our customer base shows median recovery rate of 22 percent when the SMS automation fires within 60 seconds. The recovery rate drops to 11 percent when the SMS fires after 5 minutes (n=2,847 missed calls). Speed of the bounce is the dominant lever. Last updated 25 May 2026.

Additional dated stat: The conversion uplift on missed-call SMS automation is highest for service-business teams (trades, real estate, medical) where the inbound caller is already in buy-mode. Conversion uplift on transactional categories (general inquiries) is materially lower at 8 percent.

The workflow shape

A missed-call workflow on 3CX has three components. First, a webhook subscription on the 3CX side that fires when a call ends without being answered. Second, a middleware layer (Connect Zero for 3CX, or a custom workflow tool) that receives the webhook, looks up the caller in the CRM, and decides whether to send an SMS. Third, an SMS gateway (usually the CRM's built-in SMS feature) that sends the auto-reply.

The variation is in step two. The middleware decides: which inbound calls trigger the SMS (all missed, or only those from existing CRM contacts), what the SMS body looks like, and how soon after the missed call the SMS fires. The 60-second threshold isn't arbitrary; missed-call recovery degrades sharply after the caller has moved on to the next vendor on their list.

Configuring the workflow

For Connect Zero customers, the workflow is configured in the admin under Workflows. Pick the trigger event (Missed inbound call), the condition (caller matches an existing CRM contact, or matches no contact, or both), and the action (Send SMS). The SMS template supports merge tags for caller name, called extension, time of call.

For 3CX V20 specifically, the webhook subscription is configured in the 3CX admin under Settings → CRM Integration → Webhooks. The webhook payload includes the caller ID, the dialled extension, the call duration (0 for missed), and a timestamp. Connect Zero translates this into the CRM-side workflow trigger.

Common pitfalls

  • Sending the SMS to numbers that aren't mobile. Carriers reject SMS to landlines. Filter to mobile only at the workflow layer.
  • Sending the SMS to the team's internal numbers. Internal extensions occasionally route through the same workflow if not explicitly excluded. Whitelist internal numbers at the trigger layer.
  • Over-sending on repeated missed calls. A caller who rings five times in five minutes shouldn't get five SMSes. Rate-limit at the workflow layer (one SMS per caller per hour is the conservative default).

Related context

See the CTI pillar guide for the broader workflow context. The 3CX setup guide covers the webhook configuration. Pricing at the pricing page.