Salomon Web Services Salomon Web Services
Home/ Blog/ AI & Automation
AI & Automation

Handling Tax Season Volume Without Hiring Seasonal Staff

Firms describe busy season as a volume problem. Looked at closely it is usually a composition problem: the same people doing preparation work and answering the same forty questions, in the same twelve weeks.

Calendar showing tax season deadlines

Track where hours go in a firm during February and March and the shape is consistent. A significant share is not preparation or review. It is asking clients for documents, answering where-are-we questions, scheduling, confirming receipt of things, and explaining the same handful of items to different people.

That work has to happen. It does not have to be done by the people who prepare returns, and it does not have to be done during the twelve weeks when those people are the constraint.

What the non-technical load looks like

Document chasing. Requests, follow-ups, checking what arrived, telling clients what is still missing. This runs the entire season and lands on whoever has capacity.

Status questions. “Any update on mine?” arrives constantly, by email, phone and text. Each one is a small interruption to someone doing focused work, and interruptions during review are expensive.

Scheduling. Signature appointments, review calls, extension conversations. Weeks of coordination in aggregate.

Repeat questions. What documents do I need, did you get my upload, when is my extension due, how do I pay. The same questions across hundreds of clients.

Extension logistics. Identifying who needs one, notifying them, filing, and explaining what it means, in a compressed window near the deadline.

None of this requires professional judgment. All of it consumes professional time.

What can genuinely be handled without a person

Document intake and follow-up. A request adapted to the client’s situation, progress they can see, and automatic reminders that escalate. This alone removes a large share of the season’s administrative load.

Status responses. A client asking where their return stands can get an accurate answer immediately if the system knows the state of the engagement. The information exists; the delay is that a human has to look it up.

Scheduling. Real calendar availability, booked directly, with the right meeting type and duration.

Routine questions. The recurring forty, answered consistently, with escalation to a person when the question is not routine. The escalation rule matters more than the answers.

Extension identification and notification. The system knows who is missing what against the calendar and can flag the list before anyone has time to assemble it.

The line that must not move

Preparation, review, positions taken on a return, and anything a client could reasonably interpret as tax advice stay with licensed people. This is not a cautious framing, it is the requirement.

The practical rule that works: automation handles logistics and status. Anything about what a client should do goes to a person, and the system should be built to route rather than to attempt.

Firms that blur this create risk that dwarfs any efficiency gain. Firms that respect it find the boundary is clearer in practice than it sounds in the abstract.

What actually changes

The realistic outcome is not that the season becomes easy. It is that preparers spend their hours preparing.

Firms that separate these workloads report the same pattern: the same team handles noticeably more returns, the interruption rate during focused work drops sharply, and the administrative crunch in the final two weeks flattens because document chasing happened continuously instead of in a panic.

There is a secondary effect worth mentioning. Client satisfaction tends to improve, and the reason is not sophisticated. Clients hate not knowing where things stand. Immediate accurate status removes most of that anxiety, even when the actual timeline has not changed at all.

Where to start, and when

Start with document intake, because it runs the longest and consumes the most. Status responses second.

Build in the off season. A firm implementing anything new in February is adding a variable during the period with the least tolerance for one. Build in summer, test in fall with a subset of clients, run it live for the following season.

The measurement that tells you whether it worked: hours logged to administrative categories as a share of total hours during the season, compared year over year. Most firms have never separated that number, and seeing it is often the moment the case becomes obvious.


If busy season is capping what your firm can take on, get in touch. We build intake and client communication systems for accounting practices, with the professional work left where it belongs.

Frequently asked questions

Can AI prepare returns?

No, and firms should be careful with anyone claiming otherwise. What automation handles is the surrounding work: intake, document chasing, status questions, scheduling and routine client communication. Preparation and review stay with licensed professionals.

What about client confidentiality?

Any system touching client tax information needs the same controls you would apply to a portal: access restrictions, encryption, audit logging and a clear data retention policy. This is a real requirement, not a formality, and it should be settled before anything goes live.

Will clients accept automated communication from their accountant?

For status and logistics, generally yes, because the alternative is waiting a day for an answer. For anything advisory, no, and it should not be attempted. The distinction is usually obvious to clients when the boundary is respected.

Want to apply this to your business?

We'll walk you through the implementation step by step, no commitment required.

Get a free quote More articles