03 · Final audit & launch readiness

Launch approved for the rebuilt HR Support Assistant snapshot.

Intake, read-back, correction and submission to HR work. Phone, sender, pipeline owner and leave policy remain employer setup.

Source v1Rebuilt Sep 24, 2026Agent inactive during QAZero live channels
FINAL AUDITDECISION · APPROVED

Leave
Intake

Findings9
Routes proven2 / 2
Behavior tests13 / 15
Dangling links0
RecommendationREADY
01 · Launch decision

The rebuilt snapshot is approved.

Employers receive the leave line Votel promised: every request is complete, confirmed by the employee and delivered to HR with a status, and no employee is ever told their leave is approved by a machine.

Built

Submission

Pipeline, HR email and receipt.

Built

Confirmation loop

Correct and confirm again.

Approved

Master generation

The agent can become the next official baseline.

Launch decision: approved. The employer reviews the leave types, connects an email sender, assigns the pipeline and adds its leave policy, then runs the acceptance calls.
02 · Rebuilt inventory

What the final snapshot contains.

AssetStateDetail
HR Support AssistantRebuilt

Inactive; GPT-5.4 Mini; boundaries, privacy and intake rules.

Leave of Absence IntakeConnected

Nine-question intake, read-back, correction loop, submission.

Leave Requests pipelineInstalled

Submitted, Under HR Review, Approved, Denied, Closed.

HR fieldsInstalled

Leave Type, Employee ID, Leave Start Date, Expected Return Date, Manager or Supervisor.

HR leave intake workflow
Leave of Absence Intake, saved September 24, 2026. Dashed steps need the owner's email sender.
Text version of this diagram

Morgan explains that the call records a leave request for HR review and does not approve or deny leave. The employee gives their name, employee ID if they have it, department, leave type (FMLA, military leave, jury duty, court appearance or short-term disability), start date, expected return date, manager, preferred follow-up method and any notes. Morgan reads the whole request back and asks whether it is correct. A change is updated and read back again. Once confirmed, the request moves to Submitted in the Leave Requests pipeline, HR is emailed the full request, the employee is emailed a receipt that is not an approval, and Morgan confirms it was submitted for review.

03 · Final validation

What was proven and what the employer proves.

ControlResultEvidence
Connected graphPass

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

Confirm and correctPass

Confirmed path completed at 98; correction route taken at 95.

Boundaries and intake rulesPass

13 of 15 behavior tests, both misses explained.

Live calls and emailOwner step

Run the acceptance calls with a synthetic employee.

04 · Owner setup

Connect the employer, not the logic.

HR owner setup journey
Owner configuration, September 24, 2026.
Text version of this diagram

Install the snapshot, review the leave types against your policy, connect an email sender and confirm the HR support address, decide who works the Leave Requests pipeline, add approved leave policy to a knowledge base, assign the agent to your employee leave line, run the acceptance calls with a synthetic employee, then activate.

Launch approved.

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

Open the buyer-facing guide →