Calling issues

A call you started never connected, inbound calls aren't reaching you, or a caller's voicemail didn't show up. Work through the causes below in order.

Common causes#

Click-to-call never connects — answer your own phone first#

Click-to-call works by bridging: Landing Zone calls your phone first, and only after you answer does it dial the contact. If your phone is off, silenced, or you let the call ring out, the contact is never dialed. Answer the incoming call on your phone, then wait for the bridge. Check the call log to see how far each attempt got. See Click-to-call.

Inbound calls don't ring#

Calls to your Landing Zone numbers forward to your routing number. If inbound calls aren't reaching you, open Settings → Phone numbers and confirm the routing number is correct and is a phone you can actually answer. See Receive inbound calls.

Voicemail not captured#

Landing Zone captures voicemail when a call to one of your numbers goes unanswered. If the call is answered anywhere along the way — including by your routing phone's own carrier voicemail picking up first — Landing Zone doesn't record a voicemail. Check where the call actually landed in the call log, and review your routing number in Settings → Phone numbers.

Quiet-hour blocks#

Outbound calls are blocked during the contact's local quiet hours — by default 9 PM to 8 AM in the contact's timezone, configurable per workspace. If a call won't start in the evening or early morning, this is likely why. See Quiet hours.

The contact is suppressed or on a DNC list#

Outbound calling is compliance-gated: contacts on your suppression list or flagged by DNC screening can't be called. This is by design, not a bug. Check the contact's record and your screening results — see Review screening results and DNC screening.

Still stuck?#

Email support with your workspace name, the contact or call involved, timestamps of the attempt, and screenshots of the call log — see Contact support.