Acceptance criteria should tell the client what the receptionist must do and how they can verify it. “Sounds natural” and “books appointments” are too broad to settle whether the delivered workflow is correct.
Write criteria around caller scenarios and resulting records. Include the permitted customer commitment, destination fields, action status, staff notification, and unresolved-work owner. Keep subjective voice preferences separate from consequential behavior.
Use observable conditions
A criterion can state that a verified eligible caller requesting a supported visit receives the correct appointment details only after the destination confirms creation. The failure case should state that an uncertain write produces pending language and a reconciliation task.
Avoid requiring a precise sentence when several wordings preserve the intended meaning. Be strict about dates, properties, prices, authority, and supported claims; allow reasonable conversational variation elsewhere.
Work through a fictional booking requirement
A service company wants routine visits booked at the correct property. The acceptance case supplies a fictional existing customer with two sites, asks for one site, and verifies the resulting remote property identifier.
A companion case makes the scheduling response time out. The expected outcome is no false confirmation, a durable uncertain action, and a staff-visible recovery item. Passing the first case alone does not establish the booking workflow is ready.
| Acceptance dimension | Evidence |
|---|---|
| Caller context | Correct matched or unresolved identity |
| Business rule | Approved eligibility and scope applied |
| Remote action | Correct verified destination record |
| Failure handling | Honest status and recovery owner |
| Handoff | Accepted transfer or approved fallback |
Agree on environments and limitations
Specify where tests run, what differs from production, which dependencies are simulated, and what controlled post-cutover verification is required. Use fictional records and isolate notifications or dispatch side effects.
Detailed criteria take time but prevent review from becoming a debate about impressions. Excessive criteria can also make a small project unwieldy. Prioritize common paths and consequential failures, then add coverage as scope expands.
Record supported exclusions and their fallback. An unsupported scenario handled honestly may pass its intended criterion. Review field-service acceptance for a practical matrix format.
Questions about acceptance criteria
Should every possible call have a test?
No finite suite covers every call. Focus on meaningful decisions, ambiguity, dependency failures, and costly wrong actions.
Can a demo count as acceptance evidence?
Only for the scenarios and conditions it actually exercises, with inspectable results.
Who signs off?
The operational owner approves business outcomes and usability; technical owners verify implementation and recovery. Document unresolved limitations and who accepts them.