Built by BuildZn · Sample data
Inquiry assistant
We built an intake workflow that structures requirements, creates a lead record and prepares an editable response for human approval. 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 service inquiry arrives as free text. Someone must identify the contact, copy requirements into a lead record and prepare a first reply.
What we built
We built the labeled-input parser, required-field checks, structured lead record, editable response template and approval reset. Run these steps below. A connected CRM and email adapter are separate production work.
ACTUAL SAMPLE OUTPUT / FICTIONAL DATA
See the result before trying it.
{
"id": "DEMO-001",
"contact": {
"name": "Alex Morgan",
"email": "alex@example.com",
"company": "Sample Studio"
},
"requirements": {
"request": "Capture service inquiries, structure requirements and draft a reply for approval.",
"tools": "Website form, spreadsheet, CRM",
"volume": "25 inquiries per week"
},
"status": "needs-human-review"
}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 inquiry
Keep the labeled format: Name, Email, Company, Tools, Request, Volume. This parser is intentionally limited.
02 / Requirements & lead
Structure the inquiry to inspect the fields and missing requirements.
03 / Response for approval
Create a valid sample lead to prepare a response draft.
THE PROBLEM
Where the work gets stuck.
Service inquiries arrive with inconsistent details. Re-entering contacts and requirements makes it easy to miss the information needed before replying.
Try the workflow
- Choose or edit a fictional inquiry
- Extract contact, tools, request and missing information
- Create a sample lead and review the response
- Approve locally; reset without sending anything
Technical scope
Browser-based intake parsing, required-field checks, lead record creation and draft approval. Records stay in memory; nothing is sent to a CRM or inbox.
The decision that matters
An inquiry is not authorization to promise a price or start work. Missing information is flagged and the response remains a draft until reviewed.
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 ↗