All work

Browser workflow

Support assistant

I built a source-linked support workflow that answers covered policy questions and prepares a human handoff for unsupported requests. Try the workflow.

Knowledge retrievalSource referencesHuman handoff

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.

Inspect the source and tests

A support team repeatedly checks policies before replying. Questions outside those policies need a clear handoff.

What I built

I 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.

Inspect the output.

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
Delivery policy
Outside coverage: human handoff, with no unsupported answer.
Built by BuildZn

Policy collection

KB-01 / Delivery policy

Standard delivery takes 3–5 business days after dispatch. Tracking is emailed when the order ships.

KB-02 / Returns policy

Unused items may be returned within 14 days of delivery. Contact support with the order number before returning an item.

KB-03 / Support hours

The support team handles requests Monday to Friday, 09:00–17:00 UTC.

Ask a question

Exact, conservative phrase matching chooses recorded answers. Unrecognized wording hands off to a person.

Answer or handoff

Ask a question to inspect the answer, sources or handoff.

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

  1. Read the sample knowledge base
  2. Ask a covered question and inspect its sources
  3. Try an unsupported or conflicting question
  4. 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

My 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