How Orca Handles Calls
Last verified
This guide explains what happens from the moment someone dials your business number to the moment your team sees the outcome in Orca.
The call lifecycle
- A caller dials your existing business number. Your phone carrier forwards the call to Orca under the conditions you selected. See Call Forwarding.
- Orca answers. The caller hears ringback, then your published greeting. Identity and tone come from your AI configuration.
- The AI handles the conversation. It uses your published services, policies and do-not-say guidance. FAQ entries are read to callers as question-and-answer pairs in the current release - publish, then run a test call to confirm the spoken wording before relying on them.
- The call reaches an outcome. Depending on the configuration, this can include a written message, a booking, a transfer attempt, voicemail or a failed call.
- A call record appears. AI-answered calls can include a transcript, summary, sentiment and the configuration version used.
What the AI can do during a call
The available actions depend on the tools enabled in the published configuration and on your organisation's setup.
- Take a message - enabled by default. Orca captures the caller's name, phone number and message, plus email or address when the caller provides them. The spoken confirmation says the message has been passed to the team.
- Attempt a transfer - Orca uses the transfer targets configured for your organisation, such as a mobile number or an app user. Owners and admins manage these targets on the Transfers page in the console. If a transfer cannot be completed, the configured fallback can route the caller to voicemail. Transfers are attempted, never guaranteed.
- Book an appointment - when calendar booking is enabled and provisioned, Orca can use its built-in calendar to book or cancel appointments.
- Record a voicemail - when both written messages and voicemail are available, Orca is instructed to ask which option the caller prefers.
If something goes wrong
Many AI-session and transfer failures have a voicemail fallback. Exact behaviour depends on the routing rule and the point of failure; Orca does not guarantee that every call reaches a successful outcome.
- If an AI session cannot start correctly, the configured fallback can send the caller to voicemail.
- If a transfer target does not answer or cannot be reached, the fallback chain can end at voicemail.
- If a caller remains silent, the AI asks "Are you still there?" before ending the call after continued inactivity.
- If no routing rule covers a call, the call can fail rather than reaching the AI. This is why complete routing and real-call testing matter.
After the call
- Email: when staff email is enabled, eligible calls produce either a call-summary email or a lead-captured email. Eligibility depends on the call and configuration; do not expect an email after every short or unsuccessful call.
- Push: missed-call and voicemail events can produce push notifications on supported, registered iOS devices. Android push is not currently available. The web notifications feed provides an alternative view.
- Call record: status, timestamps, duration, configuration version and available transcript or summary appear in Calls.
Limits to be aware of
- Call duration: the standard configuration limits AI calls to about 8 minutes, followed by a polite ending.
- Voicemail duration: standard voicemail recording is limited to about 30 seconds.
- Transcripts: machine-generated transcripts, summaries and sentiment can contain errors. Verify important names, numbers, addresses and times.
- Voicemail storage: recordings use private storage and short-lived access links. See the Privacy Policy for current retention and deletion terms.
- Playback: a recent voicemail may remain unavailable until recording processing finishes.
Related guides
Need a hand?
If anything here does not match what you see in the app, contact us and we will sort it out.