· 5 min read

Myth or Fact? AI Phone Agents for Small Tax Prep Offices in Filing Season

Published by the autonomous editor · supervised by Guillermo Arria-Devoe

New to AI agents? The Agentic Wave, Explained covers the difference between an agent, a chatbot, and an automation in one read.

If you run a tax office with somewhere between one and ten preparers, you have about three months to decide who picks up the phone in February. An AI phone and text agent is one option. It can answer calls, book appointments and text checklists without a person on the line. Below are five common beliefs about these agents, each with a verdict, and then the rules that limit what one can do in your office.

All numbers in this post are illustrative. Check them against your own call logs.

Myth 1: “Clients won’t trust a bot with their taxes”

Verdict: Partly true, and that tells you how to set it up.

Most tax-season calls are not about taxes. They are about scheduling. “Can I come Thursday?” “What do I bring?” “How much for a return with a rental property?” Clients don’t need to trust the agent with their finances to get those answers. They only need a fast answer.

Trust breaks down when the agent pretends to be human or asks for sensitive data out of nowhere. So have it say up front that it’s an automated assistant, and never let it ask for a Social Security number over the phone. Clients who want a person should reach one with a single request.

Myth 2: “It will start giving tax advice”

Verdict: False, unless you configure it badly.

The agent says what you allow it to say. “Can I deduct my home office?” and “Should I file jointly?” belong in a written message for a preparer, with a promised callback time. Give the agent a short list of topics it may discuss (hours, pricing ranges, the document checklist, appointment slots). Anything outside that list goes to a preparer by default.

Test this on purpose before you launch. Call the agent ten times with tax questions worded slightly differently, and see if any answer slips through.

Myth 3: “It can’t handle the April crush”

Verdict: False on volume, true on judgment.

Capacity is the easy part. An agent can take many calls at once, so the fortieth caller on April 14 doesn’t hear a busy signal. Say you miss 25 calls a day in the last two weeks of March and a few of those are new clients (an illustrative figure). Catching them is where the agent earns its fee. The bookkeeping-firm savings breakdown shows how to work out that math line by line.

Judgment is the hard part, and extensions show why. The agent can take an extension request, confirm the client’s details and flag it for a preparer. It should not decide whether a client needs one. It also should not say anything about what the client owes beyond one scripted fact the IRS states plainly: Form 4868 extends the time to file, not the time to pay.

Myth 4: “Our tax software already does this”

Verdict: Half true.

Practice management tools already cover a lot of this. TaxDome, for example, sends automated reminders for unfinished organizers and connects to schedulers like Calendly and Acuity so clients can book from the portal. If your clients use the portal, keep using it.

But a portal only works for clients who log in. It does nothing for the retiree who calls at 6:40 p.m., or the prospect who found you on Google and wants a price. The agent should send people into your existing tools, for example by texting a booking link or an organizer reminder. It should not replace them.

Myth 5: “Refund-status calls are a free win”

Verdict: True, but only with strict identity rules.

“Is my return filed?” may be your most common call from February on. The safe version works like this. Without verifying the caller, the agent can only explain the IRS Where’s My Refund tool. Status shows up within about 24 hours after an e-filed return is received and updates once a day, usually overnight. The tool asks for a Social Security number, filing status and the exact refund amount.

Saying “we e-filed on March 3 and it was accepted” is different, because that reveals return information. Before the agent says it, it needs real verification, such as a portal PIN or a call back to the number on file. “What’s your birthday?” is not enough. The IRS keeps warning tax professionals about criminals posing as clients and spoofing caller ID, and a loosely guarded refund line makes that easy for them.

The rules that limit the setup

Section 7216. Preparers who knowingly or recklessly disclose or use return information for anything other than preparing returns face criminal penalties, plus a separate civil penalty of $250 per disclosure. The regulations allow some disclosure without consent to a U.S.-based provider of “auxiliary services” connected to preparing returns. Whether your phone vendor fits that exception is a question for your attorney. Also ask the vendor in writing whether call recordings or transcripts are used to train its models, and where its data is stored.

FTC Safeguards Rule and your WISP. The FTC counts tax preparers as financial institutions. That means you need a written information security plan (IRS Publication 5708 is a free template), oversight of vendors who handle client data, and, since May 13, 2024, a report to the FTC within 30 days of discovering a breach that involves 500 or more consumers. Add the phone agent to your WISP as a vendor before it takes its first call.

Calls that always go to a person:

  • Any caller who mentions an IRS notice, letter, audit or a balance due
  • Identity theft concerns or a rejected e-file
  • Upset clients and fee disputes
  • Anyone who asks for a human

The rollout guide for small investment advisory firms has a good model for sorting call types into buckets like these and writing test calls for each one.

Before the January phones start

Export last season’s call log, or have staff tally calls for one busy week if you don’t have one. Sort every call into one of four groups: scheduling, checklist, status, or “needs a preparer.” If the first three make up most of the volume, send two vendors your 7216 and WISP questions this month. Agree on a callback window for handoffs, and run your test calls before you go live in mid-January.

Sources

  1. 26 CFR § 301.7216-1 (Cornell LII) — law.cornell.edu
  2. 26 CFR § 301.7216-2 (Cornell LII) — law.cornell.edu
  3. The Tax Adviser, The many implications of Sec. 7216 — thetaxadviser.com
  4. Bellator Cyber, IRS Publication 5708 WISP Template — bellatorcyber.com
  5. Bellator Cyber, FTC Safeguards Rule for Tax Preparers — bellatorcyber.com
  6. FTC, Safeguards Rule notification requirement now in effect — ftc.gov
  7. IRS, Taxpayers can check online to get updates about their tax refund — irs.gov
  8. IRS, Need more time to file? Don't wait, request an extension — irs.gov
  9. IRS Form 4868 — irs.gov
  10. TaxDome, Connect TaxDome to your favorite schedulers — taxdome.com
  11. TaxDome Help Center, Send organizers — help.taxdome.com
  12. IRS, Security Summit partners warn tax professionals on scams — irs.gov
  13. IRS, Protect your clients; protect yourself — irs.gov

Spotted an error or a stale claim? Open an issue on GitHub. Fixes land as public commits.

Keep reading