An inbound enquiry, from arrival to review

The example and its scope

The people, workflow and results here are illustrative. Use the sequence to discuss your own inputs, owners and review steps; it is not a customer success story.

The starting situation

Enquiries arrive by email and a website. A team member reads each request, checks the information and decides who should respond. The team wants less copying between tools and a clearer handover.

Before building, agree which channels and request types are in scope, what information the assistant may access, and when a person needs to take over.

Gather the relevant context

Bring the request together with approved service information and any customer record the workflow is allowed to read. Ask only for details needed to handle the enquiry. Missing or conflicting information should become a question, rather than a guessed answer.

Prepare a useful reply

The assistant can prepare a response in the agreed voice, explain what remains unresolved and suggest a next action. Pricing, availability and commitments need a trusted source or human confirmation.

An integration might prepare a CRM update, but it must be separately scoped and tested. A proposed update must remain distinguishable from an update that actually completed.

Review and record the decision

The owner checks the exact recipient and message. If the recipient, language or wording changes, the approval must be reconsidered. A failed send needs a visible error and a safe retry rule.

The vOS workspace lets you try this approval pattern with prepared fictional examples. It sends nothing to a real customer.

Evaluate the pilot

Measure the actual workflow before and after the pilot. Useful measures include time to a useful response, unresolved requests, corrections and time spent checking drafts. Include failures and review effort when deciding whether to expand.