# AI Receptionist for Accounting Firms: Staff Transfers, No-Advice Rules and Client Data Before Tax Season

Author: Kris Hubbard
Published: November 12, 2026
Updated: November 12, 2026
Canonical: https://wrkless.com/blog/ai-receptionist-for-accounting-firms

**Short answer:** An AI receptionist for an accounting firm or CPA office answers every call, connects callers who name a staff member straight to that person, and takes a complete message for everyone else. It never gives tax advice, never looks up or confirms a client's return, and never asks for a Social Security number. New prospects get a warm "our CPAs can help with that," then a name and callback number, then the front desk. Before tax season, set it up with a staff routing list, a no-advice rule, data-storage settings that fit your written information security plan, and a test suite you run every time staff changes.

We build AI voice receptionists on Retell for small offices, with n8n sending every call summary to the right inbox. One of the lines we run is an accounting office. The numbers and examples below come from that build.

## What calls does an accounting office actually get?

Mostly people who want a person. We pulled the office's 44 voice calls from October 29 to November 11, 2026. **31 of the 44 ended in a transfer to a staff member**, and the median transferred call spent **under 30 seconds** with the receptionist before the hand-off. 41 of the 44 calls came in on a weekday between 8 AM and 5 PM local time, and none came in on a weekend.

The reasons callers gave were ordinary office traffic: appointment questions, invoice and billing questions, tax questions, a payroll problem, updates for a staff member, job applicants, and a state unemployment-tax office calling about missing quarterly reports. That mix shapes the whole design. An accounting receptionist is mainly a fast, polite router with a great memory for messages. It isn't a tax assistant.

| Call type | What the receptionist does | What it never does |
|---|---|---|
| Caller names a staff member | Transfers right away. No "what's this regarding?" first | Guess at a name that isn't on the list |
| Existing client with a tax question | Takes name, number and question, offers the right person or a message | Answer the question or quote figures from a return |
| "What was my income last year?" | Explains it doesn't have access to tax records, offers a message or transfer | Look anything up or confirm any client detail |
| New prospect or referral | "This is exactly the kind of situation our CPAs can help with," then name, number, front desk | Lecture on the tax issue |
| Payroll or paycheck problem | Urgent message to the payroll contact, or a transfer | Promise a fix or a date |
| Government agency or "the IRS" | Full message: agency, person, callback number, reference number, deadline, read back | Confirm whether someone is a client |
| Job applicant | Message to the office manager | Discuss hiring status |

## Named-staff transfers are the core feature

Most callers in that window asked for someone by name, most often the owner or the person who runs the front desk. On November 9 we changed the line so a caller who names a staff member gets an immediate transfer, with no screening question first. A name that isn't on the routing list goes to the front desk. If the caller doesn't name anyone, the receptionist asks what they need, then which staff member they'd like.

We test that behavior before every release. The November 9 version passed **12/12** playground test cases, covering named transfers, an unknown name, office hours, leaving a message and new-client calls. Our [transfer to a human guide](/blog/ai-receptionist-transfer-to-human) covers the settings that cause transfer loops.

## Staff changes are where accounting receptionists break

Staff, extensions and seasonal help change, and the routing list is easy to forget. On November 11 we removed one accountant from the office's direct-transfer list. Three things we learned are worth copying:

1. **The list the AI reads aloud is a list callers pick from.** In the 14 days before the change, no caller asked for that accountant by name. He came up only when the receptionist offered him as a choice.
2. **Removing a person means changing every rule that mentions them.** The name appeared in the prompt, the staff-routing step, a transfer node and the "anyone else goes to the front desk" condition. If you delete the person's transfer but leave them excluded from the front-desk rule, a caller asking for them matches nothing and gets stuck.
3. **Don't comment on the person.** Callers who ask for him now hear "I'll connect you to the front desk now." There's no "he's not available" and no "he's not on the list."

The new version passed **16/16** test cases before we moved the phone number onto it, and the previous version stayed ready as a rollback. Keep your staff routing list in one place you control, separate from website pages the receptionist may have learned months ago.

## The no-advice rule, and how new clients should hear it

The riskiest moment on an accounting line is a stranger describing their tax situation. Before we rewrote that path, the receptionist would start explaining the firm's services. Now it doesn't. Now, when a prospect describes a capital-gains problem and asks for a CPA, the first reply is: "This is exactly the kind of situation our CPAs can help with. May I have your name, please?" Then it takes a callback number and offers to connect them or take a message. "Do you take new clients?" gets "Yes, our CPAs assist new clients," then the same intake.

For existing clients, the same rule applies to records. When a caller asked what their gross income was on last year's return, the receptionist explained it doesn't have access to tax records and offered a message or a transfer. That's the right answer every time. Our [message-taking guide](/blog/ai-receptionist-message-taking) shows the readback pattern we use so the callback number is always right.

## Government agencies, IRS impersonators and identity checks

Real agencies do call accounting offices. On October 29 a state unemployment-tax office called about a business client's missing quarterly reports. The receptionist took the caller's name, office, callback number, the account number and the callback deadline, then read all of it back.

Scammers call too. The IRS says it initiates most contacts through regular mail and does not call to demand immediate payment using a specific payment method such as a prepaid debit card, gift card or wire transfer. So the rule for your receptionist is simple: take a full message from anyone claiming to be an agency, and never confirm whether someone is a client or share any detail about them. Your staff can verify and return the call. For robocalls and spoofed numbers, see our [spam call guide](/blog/ai-receptionist-spam-calls).

## Client data: what IRS guidance means for an AI receptionist

IRS Publication 5708 says that under the Gramm-Leach-Bliley Act and the FTC Safeguards Rule, tax and accounting professionals are considered financial institutions, regardless of size, and must keep a written information security plan. One of the FTC requirements it lists is to select service providers that can maintain appropriate safeguards and to oversee their handling of customer information. Publication 4557 adds that failure to create a security plan may result in an FTC investigation. An AI receptionist vendor, and whoever builds it, is a service provider handling call recordings and transcripts. Treat it that way. (This is a practical checklist, not legal advice. Your compliance advisor has the final word.)

What that looks like on Retell:

- **Don't collect sensitive numbers by voice.** We don't ask callers for Social Security numbers, bank details or full dates of birth. A name, callback number and reason is enough to route.
- **Choose a data-storage setting on purpose.** Retell's options are Everything, Everything except PII, and Basic Attributes Only. Everything except PII scrubs categories you select, including `ssn`, `bank_account`, `date_of_birth` and `customer_account_number`, from transcripts, recordings and call analysis.
- **Know where the data goes next.** If transcripts are scrubbed or not stored, your [post-call webhook](/retell-ai-integrations-and-webhooks.php) still receives the call details, so the email or CRM record you send them to belongs in your security plan too.
- **Turn on multi-factor authentication** for everyone who can open the call dashboard. Publication 5708 lists MFA among the FTC requirements.
- **Disclose and record lawfully.** See our guides on [AI disclosure rules](/blog/ai-receptionist-disclosure-laws) and [call recording laws](/blog/ai-call-recording-laws).

## Getting ready for tax season

The IRS opened the 2026 filing season on January 26, 2026 and expected about 164 million individual returns ahead of the April 15 deadline. It hasn't announced the 2027 opening date yet, so set up and test in December, not in the first busy week. Add extended hours, holiday closures and a "we're closed today" message ([holiday hours guide](/blog/ai-receptionist-holiday-hours)), and make sure seasonal staff are on the routing list before their first day.

## Launch checklist for an accounting firm

- [ ] Staff routing list with an extension for each person, kept in one place
- [ ] Unknown names go to the front desk, with no comment on the person
- [ ] No-advice rule written for both tax questions and record lookups
- [ ] New-client wording approved by a partner
- [ ] Agency and IRS-caller message template with reference number and deadline
- [ ] No SSNs, bank numbers or dates of birth collected by voice
- [ ] Data-storage and PII settings that match your written information security plan
- [ ] MFA on the call dashboard and on the inbox that receives summaries
- [ ] Greeting that names the firm and says it's an AI assistant ([greeting scripts](/blog/ai-receptionist-greeting-script))
- [ ] Test suite rerun after every staff change, with a rollback version kept

## Want this set up for your firm?

We'll write the routing list and no-advice rules with you, connect call summaries to your inbox or practice software, set the data-storage options, and test every path before a client hears it. See [AI receptionist for small businesses](/ai-receptionist-for-small-businesses.php) and [Retell AI voice agent setup](/retell-ai-voice-agent-setup.php), compare costs in our [AI receptionist pricing guide](/blog/ai-receptionist-pricing-2026), or [book your AI systems assessment](https://cal.com/kris-hubbard-wrk-less/ai-systems-assessment).

## Questions people ask

### Can an AI receptionist answer tax questions for an accounting firm?

It shouldn't. Set it up to take the caller's name, callback number and question, then transfer them or take a message for the right person. It should never give tax advice, quote figures from a return, or confirm any client detail. On the accounting office line we run, a caller who asked about last year's income heard that the receptionist doesn't have access to tax records, then got the choice of a message or a transfer.

### How should an AI receptionist handle new clients calling a CPA office?

Warmly and briefly. Our build answers a prospect who describes a tax problem with "This is exactly the kind of situation our CPAs can help with. May I have your name, please?" It then takes a callback number and offers to connect them to the front desk or take a message. It doesn't explain the tax issue or promise an outcome.

### Can an AI receptionist transfer callers to a specific accountant?

Yes. Give it a routing list with each staff member's number or extension. On the accounting office line we run, a caller who names someone on the list is transferred right away, and a name that isn't on the list goes to the front desk. When staff change, update every rule that mentions the person and rerun your test calls before the change goes live.

### Does the FTC Safeguards Rule apply to an AI receptionist at an accounting firm?

IRS Publication 5708 says tax and accounting professionals are financial institutions under the FTC Safeguards Rule, regardless of size. One requirement it lists is to select service providers that can maintain appropriate safeguards and oversee their handling of customer information. An AI receptionist vendor handling recordings and transcripts fits that description, so include it in your written information security plan and check the details with your compliance advisor.

### Should an AI receptionist collect Social Security numbers?

No. A name, callback number and reason for the call are enough to route it. Keep Social Security numbers, bank details and dates of birth off the phone line, and if you use Retell, its Everything except PII storage setting can scrub categories such as ssn, bank_account and date_of_birth from stored transcripts and recordings.

## Sources

- Wrk Less call review, Retell API pull (Nov 11, 2026) of an accounting office client voice line, October 29 to November 11, 2026: 44 voice calls; 31 of the 44 ended in a transfer to a staff member; median transferred call spent under 30 seconds with the receptionist before the hand-off; 41 of the 44 calls on a weekday between 8 AM and 5 PM local time; none on a weekend (0 weekend calls); in the 14 days before the change no caller asked for the removed accountant by name, who came up only when the receptionist offered him as a choice (3 calls)
- Wrk Less build notes, accounting office line: November 9, 2026 direct transfer to named staff, unknown names to the front desk; November 9 version passed 12/12 playground test cases; November 11, 2026 removed one accountant from the direct-transfer list, caller hears "I'll connect you to the front desk now."; November 11 version passed 16/16 test cases before the phone number moved to it, previous version kept as rollback; new-client replies "This is exactly the kind of situation our CPAs can help with. May I have your name, please?" and "Yes, our CPAs assist new clients"; October 29, 2026 a state unemployment-tax office call about missing quarterly reports, message with callback number, account number and callback deadline read back
- https://www.irs.gov/pub/irs-pdf/p5708.pdf
- IRS Publication 5708 (Rev. 8-2024), checked November 12, 2026: under the GLBA and Safeguards Rule, tax and accounting professionals are considered financial institutions, regardless of size; WISP must be written and accessible; select service providers that can maintain appropriate safeguards and oversee their handling of customer information; implement multi-factor authentication; report a security event affecting 500 or more people to the FTC no later than 30 days from discovery
- https://www.irs.gov/pub/irs-pdf/p4557.pdf
- IRS Publication 4557 (Rev. 5-2024), checked November 12, 2026: tax return preparers must create and enact security plans to protect client data; failure to do so may result in an FTC investigation
- https://www.irs.gov/newsroom/irs-security-summit-remind-tax-pros-they-need-a-written-information-security-plan-to-protect-client-data
- https://www.irs.gov/newsroom/how-to-know-its-really-the-irs-calling-or-knocking-on-your-door
- IRS FS-2017-7, checked November 12, 2026: the IRS initiates most contacts through regular mail; the IRS does not call to demand immediate payment using a specific payment method such as a prepaid debit card, gift card or wire transfer
- https://www.irs.gov/newsroom/irs-opens-2026-filing-season
- IRS IR-2026-12, January 26, 2026: IRS opened the 2026 filing season; expects about 164 million individual tax returns for tax year 2025 ahead of the April 15 deadline. As of November 12, 2026 the IRS has not announced the 2027 filing season opening date
- https://docs.retellai.com/accounts/privacy-disable
- Retell Data Storage Settings docs, checked November 12, 2026: Everything, Everything except PII, Basic Attributes Only; PII categories include ssn, bank_account, date_of_birth, customer_account_number; scrubbing applies to transcript, recording and call analysis; webhook events still deliver transcript and recording when opted out
- https://docs.retellai.com/features/webhook
- https://cal.com/kris-hubbard-wrk-less/ai-systems-assessment