Skip to main content

After-hours call handling with Ocular on Zoom Phone

How Ocular answers a store's calls when it is closed, using Zoom Phone as the telephony layer and keeping the queues and voicemail the store already has. The reference case is a quick-service restaurant that today handles after-hours calls with a Zoom voice assistant.

On one page​

Today, with a basic voice assistantWith Ocular
Recognizes two situations (employee and pickup order) and has two exits: the store queue or its voicemail. Everything else depends on the knowledge base.Ocular takes the first contact: it classifies each call into a category and applies one clear rule per category. The Zoom destinations stay. Every handoff travels with a summary and everything is measured.
TODAY Caller ──► Zoom Phone (store number) ──► Voice assistant ──► Store queue
(free prompt, Voicemail
2 exits)

WITH OCULAR Caller ──► Zoom Phone (store number) ──► Ocular ───────────► Delivery app
classifies, decides Store or manager, with summary
and records Complaint follow-up
live dashboard Zoom queue and voicemail (kept)

The problem it solves​

Voice assistants configured with a free prompt and two or three transfer "skills" are inconsistent: they trigger transfers wrongly, confuse delivery aggregators with the store's own orders, misroute callers and give incorrect information. The cause is usually the configuration:

  • Only two exits. Any call that is not "employee" or "pickup order" has no route of its own.
  • Delivery does not exist. The words aggregator or delivery appear in no rule; the model approximates them to "pickup" and the call ends in voicemail.
  • One-line triggers. Each transfer fires on a generic sentence, with no examples; the model decides by free interpretation.
  • Knowledge base not reviewable. There is no way to audit where an incorrect answer came from.

How Ocular does it​

Ocular sits between Zoom Phone and the destinations. It does not replace telephony: it changes who decides and with what information each call reaches its destination.

  1. Entry. The store number stays on Zoom Phone. After hours, Zoom Phone hands the call to Ocular (by forwarding to an Ocular number or over SIP; see Telephony).
  2. Explicit classification as the first step. Ocular greets, listens and assigns a category to the call: general question, aggregator delivery, own order, employee (shift or urgent), complaint, abusive call or unclassifiable. Categories and their rules are configured per store and tested before publishing.
  3. One rule per category. Answer from the knowledge base, redirect to the aggregator, collect details and hand off with a summary, log and notify the manager, transfer with context to the store queue, or close with a warning. Details in Call categories and routing rules.
  4. Handoff to people with context. Whoever receives the call gets who is calling, why and what they were told, with transcript and recording available. If nobody answers, Ocular takes the call back and takes a message. Details in Anti-loop rules and handoff.
  5. Logging and measurement. Every call is stored with category, transcript, summary and outcome, visible on the live dashboard and available to compare against the previous assistant. Details in Measurement and rollout.

What stays and what changes​

DimensionBasic voice assistantWith Ocular
How the destination is decidedFree prompt and two skills with one-line triggersExplicit classification and one rule per category
Call typesTwo: employee and pickup orderEight categories plus an emergency rule
Aggregator deliveryDoes not exist in the configurationOwn category with redirection to the delivery app
EmployeesYes/no question; everyone to the queueSeparates shifts and absences from urgent matters; employee verification
ComplaintsNo handlingStructured log and handoff to an owner
Abusive callsOne warning and hang-upOne warning, close and log; they never reach staff
Handoff to a personTransfer without summaryWith summary, transcript and recording; in the platform or by email
If the transfer failsThe call is lostOcular takes it back and takes a message
Knowledge baseOne base in Zoom, not auditableConnected to Zoom or copied to Ocular; tested with real questions
Testing before publishingNot visibleTests, staging and controlled publishing
MonitoringRecording and transcriptLive dashboard, configurable analytics, SLA and routing policies
TraceabilityAgent edit historyLog of the agent's actions and its tools
ChannelsVoice onlyVoice, SMS, WhatsApp and email
LanguageEnglish onlyConfigurable; English, Spanish and others
TelephonyZoom Phone: number, queue and voicemailZoom destinations are kept; Ocular decides
Desk phones and human agentsThe ones the store already usesCompatible: devices and endpoints registered in Zoom Phone keep working as they are

Scope of the first phase​

  • Ocular handles the after-hours first contact and decides the destination.
  • The Zoom queue and voicemail remain valid destinations.
  • New destinations are added (delivery app, manager, complaint owner) as the store defines them.
  • Everything is measured from day one to compare against the previous assistant with the same calls.