Inbound status questions per week in peak season
Should fall as proactive updates go out.
In March the front desk can spend most of the day answering the same handful of questions: did you get my documents, is my return ready, what do I owe you, where is my refund. Each one means looking up the client in the tax software or portal. Mixed in are messages that matter more, such as a CP2000 notice with a response deadline or a client who just received a letter about identity verification.
We would sort incoming calls, emails and portal messages by type, answer routine status questions from data your software already has and draft replies for staff to check. IRS and state notices go straight to the assigned preparer with the deadline highlighted, so they never sit in the general queue.
Classify incoming calls, emails and portal messages as documents, return status, refund, fees, IRS or state notice, or other, using the client record for context.
Send portal or email updates at key stages, such as documents received, in preparation, ready to review and e-file accepted, so fewer clients need to ask.
Draft answers to routine questions using the client's current status and your written policies, including pointing clients to the IRS refund tracking tool, for staff to check and send.
Route IRS and state notices to the assigned preparer with notice type and response deadline highlighted, and add them to a tracked notice list.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
Should fall as proactive updates go out.
Notices carry deadlines, so speed protects the client.
Shows whether routine questions are handled quickly without crowding out important ones.
For example, the front desk opens a Monday inbox with 50 portal messages. Most are status questions already covered by stage updates, and a dozen get drafted replies about fees or pickup. One client uploads a CP2000 notice proposing extra tax on unreported 1099 income. That message goes straight to her preparer with the response date highlighted and is added to the notice list. The numbers are illustrative.
In the first 30 days we would count a sample of calls and messages by type, review how notices currently reach preparers, set up return status stages in your portal and agree which replies can be drafted and which always go to a preparer.
Many portals, including TaxDome and Canopy, can show clients a status or pipeline stage. That works well if staff update stages consistently. We would set up stages that match how returns actually move through your office, so the status clients see is accurate.
It can, depending on your phone system. Some offices route peak-season calls to an answering assistant or call-back queue that captures the question and identity details. Others focus on portal and email first. We would look at where the volume actually comes from before deciding.
Every notice, however it arrives, goes onto one tracked list with the client, notice type, response deadline and assigned preparer. The owner or a lead preparer reviews that list weekly. That simple discipline matters more than any particular tool.
Illustrative defaults for a tax preparation office. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Customer support triage: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.