Handling non-sales calls
How to handle wrong-number and vendor calls in an AI receptionist
By ByTomorrow · Published
A delivery update and a sales inquiry can arrive on the same public number. Treating them both as leads can confuse the caller, create unnecessary follow-up and distort the sales queue.
This matrix classifies the request being made, rather than the person's perceived value. It supplies suggested business handling and fictional cases, not a trained classification model.
Where mistakes enter
Check these failure points
Vendor means spam
A supplier may be calling about a current delivery or service issue. Automatically discarding all vendor calls can lose legitimate operational work.
Every completed call becomes a new lead
A completed conversation, supplier request and qualified sales opportunity are different events. Store those outcomes separately.
Practical working sheet
Use this procedure with your own records
Confirmed wrong number
Fictional caller asks for an unrelated business and confirms they dialed incorrectly. Suggested reply: “You have reached [actual business]. It sounds like you intended another business.” End courteously through the normal call-ending flow; do not enroll the caller in sales follow-up.
Existing supplier or delivery matter
Ask only enough to identify the operational request and route it to the approved purchasing or delivery contact. Record the matter as operational work with an owner. A supplier should not have to answer customer qualification questions.
Unsolicited vendor offer
Follow the business's published or approved vendor-contact process. If offers are accepted through a separate route, state that route accurately. Avoid promising a purchasing review or sharing staff contact details without authority.
Unclear purpose
Use one neutral clarification such as “Is this about work you need from us, or something you provide to our business?” If the answer remains unclear, keep the category unresolved. A company name alone is insufficient evidence to reject the call.
Disposition worksheet
Use columns: call reference; caller-stated purpose; customer inquiry/operational supplier/vendor offer/wrong number/unresolved; supporting statement; permitted next action; owner if needed; sales-opportunity eligibility. A category can exclude a call from sales reporting while retaining an operational task.
Correct a mistaken classification
If the caller clarifies that a supposed vendor call is a customer request, update the current category and cancel any unsent inappropriate follow-up. Preserve the initial classification in the review trail so the failure can be studied.
Apply and verify
Test the complete behavior
Define operational destinations
Name who receives delivery, purchasing and supplier-service requests.
Write neutral clarification questions
Focus on the requested action and avoid classifying by name, accent or brevity.
Test mixed examples
Include a supplier with an urgent operational message, a customer using a company phone and a true wrong number.
Check reporting and follow-up
Verify each category reaches the right queue and does not create an inappropriate sales sequence.
Questions
Straight answers.
Retell documents custom extraction categories, including selector values. A configured label is still an inference that needs review against representative cases.
This guide makes no deletion recommendation. Follow the business's existing record-handling rules while keeping sales metrics accurate.
An audit counts and reviews past attempts. This matrix specifies how the conversation and next action should differ when a non-sales caller reaches the agent.
Sources and further reading
- Retell post-call extraction
Retell documents structured analysis after a call and absent custom fields when no conversation occurred.
Checked .
Choose one behavior to verify
Bring the relevant route, script or worksheet to a scoping conversation. Agree on the expected result and the evidence before changing the working system.
Discuss your workflow