03 · Final audit & launch readiness

Launch approved for the rebuilt After-Hours Lead Capture AI snapshot.

Forwarding, message taking, texts, callbacks and the post-call summary all work, with the callback loop fixed and team notices kept away from callers. Team phone, numbers and sender remain owner setup.

Source v5.1Rebuilt Sep 24, 2026Agent inactive during QAZero live channels
FINAL AUDITDECISION · APPROVED

After-Hours
Receptionist

Source findings12
Workflows3
Behavior tests9 / 10
Dangling links0
RecommendationREADY
01 · Launch decision

The rebuilt snapshot is approved.

Owners receive the full receptionist Votel designed: the team is tried first, every missed caller leaves a message, gets a text and a callback, and the team gets the details and next steps by email.

Fixed

Callback loop

Inbound-only trigger, tag removed first, two callbacks at most.

Fixed

Destinations

No imported phone numbers; team notices go to the support address.

Approved

Master generation

The agent can become the next official baseline.

Launch decision: approved. Team phone, caller ID, SMS number, email sender and business name are expected setup, followed by the acceptance calls.
02 · Rebuilt inventory

What the final snapshot contains.

AssetStateDetail
After-Hours Lead Capture AI agentRebuilt

Inactive; GPT-5.4 Mini; neutral prompt; callback voicemail message.

After-Hours Calls: Connect or Take a MessageConnected

Inbound trigger, lookup, greeting, forwarding, six questions, tag, business-hours decision, team emails and closes.

After the Call: Summary and Missed-Call RecoveryConnected

Inbound call-ended trigger, three branches, four texts, two callbacks, AI summary, tasks and notes.

Callback Calls: Connect the CallerConnected

Callback greeting, forwarding, two questions, team email and close.

Fields and variableInstalled

Reason for Call, Is It Urgent, Best Callback Time and Company Name.

After-hours call handling workflow
After-Hours Calls: Connect or Take a Message, saved September 24, 2026. Dashed steps need the owner's team phone or email sender.
Text version of this diagram

An inbound call finds or creates the caller by phone number, and Sara greets them with the business name. The call is then forwarded to the owner's team line. If the team answers, the team gets a call-connected email. If nobody answers during business hours, or the call comes in outside business hours, the workflow marks which case it is and Sara takes a message: first name, last name, best phone number, reason for the call, whether it is urgent and the best time to call back, all saved to the contact. The contact is tagged missed lead, the team gets a missed-call or after-hours email with the details, and Sara confirms the message and says a text is coming before the call ends.

After-call summary and missed-call recovery workflow
After the Call: Summary and Missed-Call Recovery, saved September 24, 2026. Inbound calls only. Dashed steps need the owner's SMS number, caller ID or email sender.
Text version of this diagram

When an inbound call ends, the workflow checks what happened. If the caller left a message (tagged missed lead), the tag is removed, the caller gets a message-received text, then a callback-coming text held until business hours, then up to two callback calls five minutes apart. An answered callback is noted and the callback conversation takes over; if both callbacks fail, a task asks the team to call back manually. If the call itself was missed, busy, sent to voicemail or failed, the caller gets a sorry-we-missed-you text and the team gets a task. Otherwise an AI step reads the transcript: if the caller hung up before giving their details they get a we-got-cut-off text and the team gets a task; if the call produced next steps the team gets them by email; if neither, a note records that no follow-up is needed.

Callback call workflow
Callback Calls: Connect the Caller, saved September 24, 2026.
Text version of this diagram

When a callback call is answered, Sara says she is returning the caller's call and tries the team line. If the team answers, the connection is noted. If nobody answers or it is outside business hours, Sara confirms the reason for the call and the best time to reach the caller, emails the team that the callback did not connect, confirms, and ends the call.

03 · Final validation

What was proven and what the owner proves.

ControlResultEvidence
Connected graphPass

No dangling links after an editor save; every branch ends.

Message takingPass

Eight simulator conversations scored 78 to 96.

Conversation rulesPass

9 of 10 behavior tests; the tenth needs a live transfer.

Loop safetyPass

Reviewed: callbacks are outbound and the trigger is inbound-only.

Recovery branches and live callsOwner step

Run the acceptance calls once the line, SMS number and sender are connected.

04 · Owner setup

Connect the business, not the logic.

After-Hours owner setup journey
Owner configuration, September 24, 2026.
Text version of this diagram

Install the snapshot, set the Company Name, enter the team phone and business hours on both forwarding steps, choose the caller ID for forwarding and callbacks, connect an SMS number for the four texts, connect an email sender and confirm the support address, assign the agent to the business line, run the acceptance calls, then activate.

Launch approved.

The rebuilt snapshot is ready for master snapshot generation and owner acceptance tests.

Open the buyer-facing guide →