- Define one call job
- Approve knowledge and disclosure
- Test escalation and outcomes
01
Give the call one clear job
Start with a bounded task such as booking, qualification, confirmation or follow-up. Document what counts as success, what must be confirmed and which requests the agent must not complete.
- Define the permitted outcome.
- List disallowed decisions and sensitive topics.
- Choose the human team that owns exceptions.
02
Use approved business knowledge
Provide current, attributable information that the business is prepared to stand behind. Remove conflicting instructions and add an owner and review date for price, policy, hours and eligibility content.
03
Make identity and recording rules clear
Tell the recipient they are speaking with an automated voice agent where required and apply the laws, consent rules and recording notices relevant to the parties and destination. DripTell configuration does not replace legal review.
- Review outbound-call and recording rules for each market.
- Use an approved disclosure at the beginning of the call.
- Provide an accessible route to a person or opt-out where required.
04
Test the difficult paths, not only the happy path
Run calls with unclear speech, changed dates, interruptions, refusal, sensitive requests and a request for a human. Confirm that the agent does not claim an action succeeded until the underlying system confirms it.
- 1
Normal case
Complete the intended task with correct data.
- 2
Uncertain case
Confirm the agent asks, waits or escalates rather than guessing.
- 3
System failure
Verify no false promise is made when an external action fails.
05
Return the call to the customer record
Store the transcript or permitted summary, outcome, sentiment signal, owner and next action with the same customer record. A teammate should understand what happened without replaying the entire call.