Create a small routing taxonomy
Use categories clients recognize: new engagement, existing return, missing documents, organizer or portal help, notice, payment, scheduling, signature, delivery, technical support, complaint, and urgent deadline. Add an unknown path that reaches a trained person.
Avoid technical subcategories that require reception staff to diagnose a tax issue.
Define approved questions
Capture identity state, contact preference, service requested, relevant tax year, entity or individual context, deadline, documents already received, and the client's own description. Do not solicit unnecessary taxpayer data in an insecure channel.
When the answer affects eligibility, filing position, legal rights, or a technical conclusion, route it to a qualified professional.
Make handoffs operational
Create one task with owner, priority, response expectation, summary, source message, and secure attachments. Tell the client what happens next without promising a result the owner has not approved.
Track reopened and misrouted cases to improve the taxonomy and scripts.
Prepare for sensitive cases
Document escalation for identity theft, data exposure, government notices, threats, urgent filing issues, accommodation needs, and suspected fraud. Staff should know whom to contact and what not to say.
Review access, scripts, and training before every filing season and after material service changes.
Sources and limitations
- Protect your clients; protect yourself — Internal Revenue Service; reviewed August 15, 2026.
This article is educational and is not tax, legal, accounting, security, or investment advice. Product capabilities and tax requirements can change. Confirm current vendor scope and authoritative guidance for the relevant facts, tax year, and jurisdiction.
How this article was prepared
We separate current sourced facts from operational recommendations, avoid invented performance claims, and show the primary sources and review date used.
Read the editorial methodology