Call categories and routing rules
Ocular classifies every after-hours call into a category and applies one clear rule per category. The categories on this page are those of a quick-service restaurant; they are adjusted per store from the platform, without touching the agent's prompt.
Summary
| Call type | What Ocular does | Where it ends |
|---|---|---|
| General question (hours, address, drive-thru) | Answers from the knowledge base. No transfer. | Resolved on the call, without touching the store |
| Aggregator delivery (late, missing items, refund) | Explains the store does not handle it and redirects | Aggregator app or support |
| Own order for pickup or through the store app | Collects the key details and builds a summary | Store, with summary |
| Employee: shift or absence | Logs the request; the store phone does not ring | Manager or shift lead |
| Employee: urgent matter | Transfers with context, summary before connecting | Store queue in Zoom |
| Customer complaint (service, product, charge) | Logs the reason and contact details | Complaint owner |
| Abusive or no value (insults, pranks, spam) | One warning and closes, firm tone without arguing | Log only; never reaches staff |
| Unclassifiable (unclear reason or audio) | One follow-up question, never back to the start | Person or message, always with summary |
Every call is stored with category, transcript, summary and outcome, visible on the live dashboard.
The categories in detail
1. General question
- Examples: hours, address, whether the dining room is open, drive-thru availability, payment methods.
- What Ocular does: answers from the store's knowledge base. Keeps the store's service rules (for example, no driving directions, offer the address instead).
- Destination: none; resolved on the call.
- Configuration: knowledge-base content and store hours. The base is connected directly from Zoom or copied to Ocular, and tested with real questions before publishing.
2. Aggregator delivery
- Examples: late, incomplete or refund request for an order placed through a delivery app (DoorDash, Uber Eats, Grubhub or others).
- What Ocular does: identifies the aggregator, explains that the store does not manage those orders and says where to claim. It can text the support link to the calling number (for example, +1 555 010 0100).
- Destination: aggregator app or support.
- Configuration: which aggregators operate with the store and whether the link is sent by SMS.
3. Own order for pickup or through the store app
- Examples: a problem with an order placed for pickup or through the store's own app.
- What Ocular does: asks for name, order number and the problem, and builds a summary. It replaces blind voicemail: the store receives an organized case, not an incomplete message.
- Destination: store, with the summary, through the configured channel (platform, email or Zoom queue).
- Configuration: who receives the summary and through which channel.
4. Employee: shift or absence
- Examples: shift swap, running-late notice, absence.
- What Ocular does: verifies the employee (code or registered number), logs who, which shift and what is requested, and notifies the manager. The store phone does not ring.
- Destination: manager or shift lead, through the configured notification channel (platform, email, SMS or WhatsApp).
- Configuration: employee verification method and notification channel.
5. Employee: urgent matter
- Examples: an operational problem that cannot wait (equipment, safety, opening).
- What Ocular does: verifies the employee and transfers to the store queue with a summary first, so whoever answers knows what it is about before talking.
- Destination: store queue in Zoom (the current destination is kept).
- Configuration: what counts as urgent.
6. Customer complaint
- Examples: service, product or a charge at the store.
- What Ocular does: listens, logs the reason and contact details, and explains the next step and response time.
- Destination: complaint owner, with the full record for follow-up.
- Configuration: owner, response time and channel.
7. Abusive or no-value call
- Examples: insults, pranks, repeated calls with no purpose.
- What Ocular does: gives one warning; if it continues, closes the call in a firm tone without arguing. Leaves a log.
- Destination: log only; never reaches staff. Optionally, an alert on repeat calls from the same number.
8. Unclassifiable
- Examples: unclear audio or a reason outside the categories.
- What Ocular does: asks one follow-up question; if it does not clarify, offers to take a message. Never goes back to the greeting or the menu.
- Destination: a person (if urgent) or a message with summary.
- Configuration: after-hours message destination.
Emergency rule
For emergencies or safety issues at the store (fire, accident, break-in), Ocular transfers immediately to the configured emergency destination, without follow-up questions, and logs the call with priority.
How they are configured and tested
- Categories, examples, rules and destinations are edited from the platform, per store.
- Each rule is tested in a staging environment with simulations and, if the store shares them, with real recordings, before publishing.
- Publishing is controlled: the previous version can be restored at any time.
- The dashboard shows the call distribution per category and helps spot missing categories or confusing rules.
Related: Anti-loop rules and handoff · Measurement and rollout