Choose the smallest workflow with material demand, an observable result and an acceptable exception path. Begin with a one-page workflow brief rather than a vendor shortlist.
What should the workflow brief contain?
- Problem: unanswered eligible enquiries, booking backlog, queue overflow or another specific failure.
- Population: locations, telephone numbers, opening hours, supported languages and included call types.
- Outcome: the operational record that proves completion.
- Permissions: information the agent may read, records it may change and actions it must never take.
- Exceptions: who receives unsupported, urgent, disputed or unsuccessful requests.
- Ownership: one accountable operations owner, plus named system and risk approvers.
- Alternative: what you would do if AI were unavailable.
Use a definition such as: “Book an eligible non-emergency plumbing visit into the approved dispatch system, within service-area and capacity rules, without promising an unsupported arrival time.” Avoid “answer every call” as the success definition.
How should the starting scope differ by buyer?
| Buyer | Recommended first scope | Required evidence | Keep outside the initial autonomous scope |
|---|---|---|---|
| Home-services operator | Routine inbound booking or after-hours enquiry capture | Correct address, eligible job, service area, capacity and booking identifier | Emergency diagnosis, invented estimates and unauthorised dispatch promises |
| Dental group | Approved appointment types at a limited set of practices | Correct patient match, provider, location, duration and appointment record | Clinical advice, discretionary insurance assurances and unrestricted chart access |
| Contact-centre operator | One routine service intent or defined overflow queue | Verified resolution plus repeat-contact and escalation records | Broad complaints adjudication or consequential account changes without appropriate controls |
| Revenue operations team | Inbound qualification and approved appointment booking | Qualification evidence, accurate CRM record and accepted appointment | Automatically adding outbound campaigns to the inbound approval |
| Outsourcer | One client-approved workflow | Client permission, workload economics and an agreed responsibility matrix | Cross-client data access or unilateral changes to client service commitments |
What baseline should you collect?
Export aggregate or appropriately redacted records covering a representative operating period. Include busy and quiet periods, after-hours demand and important location differences.
- Offered, answered, abandoned and missed calls.
- Unique enquiries, repeat attempts and calls already recovered by staff.
- Eligible enquiries versus spam, wrong numbers and unsupported requests.
- Correctly completed tasks, unresolved cases, cancellations and subsequent corrections.
- Staff handling, follow-up, quality review and supervisory time.
- Existing answering-service, telephony and relevant software costs.
- Available fulfilment capacity: appointment slots, technicians or receiving staff.
Decision: classify the workflow as pilot-ready, prepare first or do not automate yet. Missing outcome evidence or an unowned fallback should produce “prepare first”, not an optimistic readiness score.
Owner: operations. Deliverable: workflow brief, baseline and prerequisite list.