Trials, demo numbers, and test-call allowances can reveal interaction style. A useful evaluation goes beyond voice quality and asks whether the system follows the business's actual rules.
Write the test before calling
Use the same scenarios for every product: a common question, new lead, existing customer, unclear request, transfer, and failure. Record the expected answer and acceptable fallback.
Match the demo to the proposed scope
A generic demo may not contain your services, hours, calendar, or escalation rules. Treat it as evidence of interaction style, not customer-specific production readiness.
Check the billing unit and artifacts
Official pages use minutes, calls, agents, or unique customers. Confirm included usage, overages, spam and test-call treatment. Then review the message or record, intent, requested action, transfer result, and scheduling status.
Define the activation gate
Require approved answers, number-preserving forwarding, selected calendar permissions, lead capture, records, escalation, voicemail or safe fallback, and rollback to pass before real callers are routed. AfterTone configures and tests these paths with the customer.