KB-01 / Sample delivery policy
Standard delivery takes 3–5 business days after dispatch. Tracking is emailed when the order ships.
Built by BuildZn · Sample data
Support assistant
We built a source-linked support workflow that answers covered policy questions and prepares a human handoff for unsupported requests. Run it with sample data.
AUTHORSHIP / RUNNING CODE
Designed and built by BuildZn.
BuildZn-designed and implemented browser workflow. Run the code here, inspect the implementation and compare the actual outputs. Automated tests exercise successful inputs, review gates and failure cases.
THE ORIGINAL TASK
A support team repeatedly checks policies before replying. Questions outside those policies need a clear handoff.
What we built
We built a policy-matching workflow that returns source-linked answers for covered questions and a review summary for unsupported questions. It runs below with a fictional knowledge base. Live semantic retrieval and help-desk connections are separate production work.
ACTUAL SAMPLE OUTPUT / FICTIONAL DATA
See the result before trying it.
Question: How long does delivery take? Answer: Standard delivery takes 3–5 business days after dispatch. Tracking is emailed when your order ships. Source: KB-01 · Sample delivery policy Outside coverage: human handoff, with no unsupported answer.
Generated from the same sample inputs and deterministic functions used below. Built by BuildZn; these are sample outputs, not customer results. Try the steps to inspect the fields, review gates and exceptions.
Run the implementation we built: local parsing, source matching, validation and review gates. Responses use templates. No live AI model, paid account or external connection. Use sample data only; inputs stay in this page and are cleared on reload.
01 / Sample knowledge base
KB-02 / Sample returns policy
Unused items may be returned within 14 days of delivery. Contact support with the order number before returning an item.
KB-03 / Sample support hours
The support team handles requests Monday to Friday, 09:00–17:00 UTC. This is a fictional policy for the demonstration.
02 / Ask a question
Exact, conservative phrase matching chooses recorded answers. Unrecognized wording hands off to a person.
03 / Answer or handoff
Ask a question to inspect the answer, sources or handoff.
THE PROBLEM
Where the work gets stuck.
Repeated support questions require checking the correct policy. Requests outside those policies need escalation rather than a confident unsupported reply.
Try the workflow
- Read the sample knowledge base
- Ask a covered question and inspect its sources
- Try an unsupported or conflicting question
- See a handoff summary when no safe answer is available
Technical scope
A small fictional knowledge base, conservative local matching, recorded grounded answers and a visible human handoff.
The decision that matters
A helpful-sounding answer without support is not enough. Questions outside the source coverage produce a handoff rather than an invented policy.
Inspect the evidence
Our workflow logic, React interface and executable checks are public in BuildZn’s website repository. The interactive workflow runs this code; the sample outputs and screenshots come from it.
Have a similar repetitive task?
Share the input, the tools and the decision that should stay with a person.
Discuss your workflow ↗