Evaluation guide
Seven questions to ask before hiring an answering service
A polished greeting proves very little. Evaluate what happens when the caller is unclear, the request is urgent, the software connection fails, or your policy changes.
1. What information can the service reliably capture?
List the fields your team needs before it can act: name, callback number, email, service address, issue, urgency, preferred time, existing-customer status, and any industry-specific details. Ask to see the exact notification or record your team receives.
2. How are urgent and unsafe situations handled?
Define the situations that require emergency-services guidance, an on-call transfer, a priority notification, or ordinary follow-up. The provider should use your approved language and never improvise technical, medical, legal, or safety advice.
3. What happens outside the script?
Test a caller who changes the subject, gives conflicting information, asks for a promise the business cannot make, or wants a person. A good system acknowledges uncertainty, avoids invented answers, and follows a clear fallback.
4. How do integrations and outages work?
If the service books appointments or writes to a CRM, ask which fields are synchronized, how duplicates are handled, and what happens when the connected system is unavailable. There should be a fallback notification or queue so the call does not disappear.
5. What can we review?
Ask whether you can access recordings, transcripts, summaries, outcomes, transfers, and usage. Confirm how long data is kept and who can access it. Reliable quality improvement requires evidence, not anecdotes.
6. How is privacy handled?
Understand what data is collected, why it is collected, where it is processed, how long it is retained, and which vendors receive it. If you operate in a regulated field, obtain the agreements and controls your legal or compliance adviser requires before sending protected information.
7. What is the total price at our real volume?
Model your normal month and your busiest month. Include base fees, minutes, calls, transfers, overages, add-ons, holidays, integrations, setup, and cancellation terms. Ask what happens if a call is long, spam, transferred, or disconnected.
A simple scorecard
- Accuracy of information given to the caller
- Completeness of captured details
- Correct escalation or fallback
- Natural handling of interruptions and ambiguity
- Usability of the notification your team receives
- Transparency of reporting and price
A service should earn broader call volume through a controlled pilot. Start with overflow or after-hours calls, review the evidence weekly, and refine the workflow before relying on it for every caller.