Orca by HankinCore

Call Handling Best Practices

Last verified

Design a call workflow your team can operate reliably: forwarding, known callers, transfers, messages, voicemail, bookings and notifications.

Your caller-disclosure and lawful-use obligations are in the Terms of Service. Data handling is in the Privacy Policy.

Decide how calls reach Orca

Forwarding is controlled through your carrier:

  1. Forward all calls when Orca should answer immediately.
  2. Ring you first, then forward on no-answer or busy when you want first opportunity to answer.
  3. Add unreachable forwarding where supported if Orca should cover a phone that is off or outside coverage.

Record your previous carrier settings before changing them. Test each enabled condition, not only the last one. See Call Forwarding and the Telstra, Optus and Vodafone guides.

Use the whitelist for recognition, not assumed routing

The whitelist identifies known numbers and marks matching calls as VIP. It does not, by itself, guarantee a different call outcome.

Use it for clients, staff, suppliers and other numbers you want to recognise. Add numbers through Whitelist on web or mobile; changes are immediate and do not require publishing.

If known callers need special handling, ask support to confirm or change the routing rule for your organisation. Do not promise that a whitelisted caller will skip voicemail or reach a person unless that exact behaviour has been configured and tested.

Keep transfer targets current

Transfer to human uses the targets configured for your organisation. Owners and admins add and change targets on the Transfers page in the console.

Before enabling or advertising transfers:

  • Add the people or numbers who should receive transfers on the Transfers page, and confirm each target is enabled and current.
  • Test both an answered transfer and an unanswered or unavailable target.
  • Remove targets when someone leaves the business or becomes unavailable.

Unanswered transfers can fall back to voicemail, but exact behaviour depends on the configured routing chain. Avoid absolute promises to callers about reaching a person.

Separate written messages from voicemail

When both options are enabled, Orca is instructed to ask which the caller prefers.

  • Written message: captures name, number and message, plus optional email or address supplied by the caller. Verify captured details before acting.
  • Voicemail: records the caller's voice after a beep, with a standard limit of about 30 seconds.

Staff email summaries and lead emails are sent only for eligible calls when staff email is enabled. They are not caller emails and do not arrive after every short or unsuccessful call.

Treat bookings as an operational workflow

When calendar booking is enabled:

  • Orca checks only its built-in calendar, not an external diary.
  • It confirms details before booking and can offer another time or take a message on failure.
  • A caller can cancel through the attendee phone number used for the booking.
  • Appointment reminders are sent by push notification, and only while the appointment remains booked.

Keep the built-in calendar aligned with your real availability. Do not assume an external-calendar conflict will be seen or that opening hours restrict booking times.

Set expectations for call endings

  • Standard AI calls have a maximum duration of about 8 minutes, followed by a polite ending.
  • Continued silence triggers an "Are you still there?" prompt and can end the call.
  • Many AI-session and transfer failures have voicemail fallback, but not every routing or provider failure guarantees a successful message. Test failure paths that matter to your business.

Agree who owns notifications

  • Missed-call and voicemail pushes go to all enabled organisation devices, not selected members.
  • Android push is not currently available; use the web notifications feed or check Calls.
  • Browser alerts require permission and an open web app.
  • Appointment reminders are sent by push notification, not by SMS.

Assign responsibility for reviewing calls, returning messages and handling failed notification delivery.

Test after every relevant change

Run a synthetic Test call and a real forwarded call after changing forwarding, routing, transfer targets, whitelist-related rules or published configuration. Review both the result card and the caller experience.

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.