Change an input, then follow what happens.
Answer with a source
The example onboarding guide covers account setup, everyday tools and a first-week checklist. Open the team handbook to review the source.
Choose an input to explore the outcome.
An answer carries its source; a gap or disagreement carries a reason to ask a person instead of an invented answer.
Synthetic demonstration. Names, documents, records and outcomes are invented examples, not client results. These controls run locally; no message is sent, no appointment is booked and no external record changes. Sensitive or uncertain decisions stay with a person. Example policy passages are not HR, safety or legal advice.
Enable JavaScript to change the example. The complete workflow and its controls are described below.
A team question.
An approved source.
Gaps go to a person.
The full story, every step and every boundary.
Map your workflowWorking demonstration · Internal knowledge
This assistant answers from your approved documents and shows the sources. What they don’t cover goes to a named expert — not a guess.
30 minutes. One workflow mapped. You keep the map either way.
The operating rule
Every answer shows its sources. The part the documents don’t cover goes to a named expert — not a guess.
One question, end to end
Press play, or click any step to jump there.
Step 1 of 6: Question received
Click a step
Employee · 10:05
A customer wants to return a custom order — what’s the process?
System · 10:05
Searching approved documents only · 2 matches found
System · 10:05
Retrieved: SOP-04 §3 · Handbook p.12
Assistant · 10:06
Custom orders can be returned within 14 days with manager approval and a 15% restocking review. Sources: SOP-04 §3 · Handbook p.12.
System · 10:06 Human attention
Refund amount for partial use is not covered · routed to Ops manager — K. Patel
System · 10:06
Answer, sources, and documentation gap logged
Approved source set
Nothing in the set covers a partial-use refund — so the assistant stops and a person decides.
What changed at this step
Human keeps
Anything the approved documents do not cover. It stops here, with the question attached, and goes to a person by name.
The part that matters
A confident citation is the easy half. This page is about the other half — the moment it reaches the edge of the documents and hands that piece to a person.
“A customer wants to return a custom order — what’s the process?”
Custom orders can be returned within 14 days with manager approval and a 15% restocking review.
“Refund amount for partial use is not covered.”
No paraphrase, no plausible-sounding number — the part the documents don’t cover goes to a named expert, not a guess.
The same shape, other departments
HR · policy question
“How much parental leave do I have, and when do I need to file?”
Twelve weeks, filed at least 30 days ahead when foreseeable.
Not covered
Intermittent-leave scheduling is not covered
DMRouted to HR lead — D. Moss
Safety · procedure
“What’s the lockout procedure for the compressor room?”
De-energize, apply personal lock and tag, verify zero energy before entry.
Not covered
Contractor lock procedure is not covered
LGRouted to Safety officer — L. Grant
Before and after
Manual today
Connected system
Never automated
Explore another workflow
Every demonstration follows the same shape: a trigger, a system action, a visible record, a named owner, an exception path, and a recorded outcome.
01
Every call answered, labelled, and routed — with a real person one step away.
Run the demonstration02
One intake thread running in English and Spanish, structured onto one record.
Run the demonstration03
Sequenced follow-up that ends in a decision — booked, declined, or handed over.
Run the demonstration04
Missing documents surface themselves instead of stalling a file for weeks.
Run the demonstration05
One outlier surfaced against a normal series, assigned to a named person.
Run the demonstration06
Answers drawn from your own documents, cited, and honest about what it doesn’t know.
You are here
The demo is simple — the operating rules are specific
A real build starts from your approved documents, confidence thresholds, and named subject experts — mapped together on one call. Thirty minutes, one workflow, and you keep the map either way.
Pricing is scoped after discovery, once the workflow is defined.