Skip to content
Alizane Labs

How it works

From a homeowner at 2 AM to a named human who accepted

This is the whole sequence, including the parts that do not go to plan.

Covers calls routed into the Engine. Human availability and arrival times remain controlled by your team.

Sequence

The routed-call timeline

Elapsed times are an illustration of the workflow shape, not a promised response time.
Illustrative workflow
  1. 00:00RoutedHomeowner

    Call is routed into the Engine

    Your phone system forwards the call under the conditions you configured: after hours, on no answer, or on overflow.

  2. 00:01In progressEngine

    Answer with disclosure

    The automated assistant answers and discloses automated handling and recording or processing before intake begins.

  3. 00:20In progressEngine

    Triage and intake

    Urgency is classified and the approved restoration intake is captured: confirmed address, callback number, damage type, and insurance status as reported.

  4. 01:00In progressEngine

    Incident opened during the live call

    The incident record exists before the homeowner hangs up, so escalation does not wait for a transcript or a summary email.

  5. 01:05EscalatingEngine

    Primary on-call contacted

    The first approved position on the roster is called. This is a call, not only a notification.

  6. 01:50EscalatingEngine

    Escalation continues

    No answer, voicemail, or a decline moves the incident to the next approved position under the runbook's retry rules.

  7. 02:18AcceptedTechnician

    Named human acceptance

    A technician presses 1 or verbally accepts. The incident locks against that named contact with a timestamp.

  8. Next morningAcceptedOwner

    Response evidence

    The response timeline shows calls routed, incidents opened, who accepted, and any unconfirmed exceptions.

Definitions

Five words that get used interchangeably — and should not be

Answer
Someone or something picked up. On its own, this proves only that the line was not dead.
Notification
A message was delivered to a device. Delivery is not acknowledgement, and a sleeping phone still counts as delivered.
Transfer
The call was passed to another line. If nobody picks up that line, the emergency is back where it started.
Acceptance
A named human confirmed they own the incident. This is the event the Engine is built to produce and record.
Fallback
The contracted path used when no approved contact accepts. It is defined in the agreement, not improvised at 3 AM.

Failure paths

What the Engine does when the happy path breaks

  • Escalating

    Primary does not answer

    Retry per runbook, then next approved contact.

  • Escalating

    Call reaches voicemail

    Neutral message with incident reference; no homeowner details exposed; escalation continues.

  • Escalating

    Technician declines

    Decline recorded against the named contact; next position called immediately.

  • Accepted

    Two technicians respond

    First acceptance locks the incident; the second is told it is already owned.

  • Exception

    No approved contact accepts

    Contracted fallback is reached and an unconfirmed exception is recorded.

  • Exception

    Upstream service degraded

    Defined fallback and incident-response procedures apply per service level.

Division of responsibility

What Alizane Labs manages, and what stays yours

Alizane Labs manages

  • Implementation and runbook configuration
  • Voice agent and workflow monitoring
  • On-call roster updates you request
  • Daily and weekly health checks
  • Incident reconciliation and monthly reporting

You control

  • Which calls are routed into the Engine
  • Who is on the approved on-call roster
  • Whether a technician accepts
  • Callback, crew availability, and arrival
  • Pricing, coverage advice, and the customer relationship
Book the dispatch audit