On mobile, "phone" means click-to-dial — tap a customer's number and your phone's native dialer opens to call them. There's no in-app inbound call handling and no Voice SDK on mobile.
Click-to-dial
Anywhere a customer phone number appears in the mobile app:
| Location | Example |
|---|---|
| Customer profile | The contact info card. |
| Job page | The customer's number. |
| Message thread | The contact info card. |
Tap it. iOS or Android's native dialer opens with the number pre-filled. Press call.
Where the call appears
The outgoing call is routed through your device's native phone — using your personal carrier line, not your Run a Call Phone number. The call won't show in your Run a Call inbox.
This is a known limitation of the current mobile build. For Run a Call Phone outbound calls (caller-ID matches your business number, recording, transcripts), use the desktop softphone on the web app.
In-app inbound calls
Inbound calls do not ring through to the mobile app. If the AI Receptionist is on, the AI handles them; if not, they ring through to whatever you've configured (voicemail, forwarding).
The mobile app shows you the call history and any follow-ups generated by the AI — but it doesn't ring or let you pick up a live call.
Caller ID for outbound
Because the click-to-dial uses your phone's native dialer, the customer sees your phone's caller ID (often your personal cell number), not your Run a Call Phone number.
If you want your business number to appear on the customer's caller ID for outbound calls, dial from the web app's softphone on the desktop instead.
What's NOT supported today
- Outbound dialing through Run a Call Phone on mobile (so the business number shows on caller ID).
- In-app inbound — receiving calls in the mobile app.
- Voice SDK for warm transfers and conference calls on mobile.