3 Methods: Route Client Questions to the Right CPA 2026

AICPA tech-survey adoption rate: 62% of accounting firms now use cloud-based workflow tools, per the AICPA 2025 PCPS CPA Firm Top Issues Survey. Yet most of those same firms still route client questions the same way they did in 2012: a general inbox, a forwarded email chain, and a question that eventually finds the right CPA after 6–12 hours of ambiguity.

Client question routing is a deceptively costly workflow failure. A CFO sends a question at 9:00 AM about whether a specific expense is deductible. If it reaches the assigned CPA by 9:15 AM, she has the answer drafted by 9:45 AM and the client feels well-served. If it sits in a shared inbox until 2:00 PM, the client calls in frustrated, takes 20 minutes of a partner's time, and the billable hour isn't logged.

The solution isn't a bigger inbox or more staff. It's a routing layer that identifies who the client belongs to, where the question came from, and what the question likely requires — then delivers it to the right person with that context attached.

This post covers three methods for automating client question routing, when each makes sense, and the workflow recipe for implementing the most common approach.

Key Takeaways

• Unrouted client questions cost accounting firms 4–7 hours of partner and senior staff time per week in re-routing, follow-up, and re-explanation.

• The three routing methods — rules-based email triage, portal-native assignment, and AI-assisted classification — differ in setup time, accuracy, and staff change management requirements.

• The breakeven for routing automation is typically 30–45 days based on billable-hour recovery alone.

• Multi-partner firms with 200+ clients have the highest ROI because routing complexity scales with client count.

• This guide focuses on firms using QuickBooks Online, Karbon, Jetpack Workflow, or a CPA-specific client portal.

Who This Is For

This guide is for managing partners, operations managers, and senior CPAs at accounting and bookkeeping firms with 5–40 staff serving 100+ clients who receive a meaningful volume of ad hoc client questions through email, client portals, or phone — and currently handle routing manually.

Red flags: Skip this if your firm has fewer than 5 staff and routing is handled by one person who knows every client by name (not a routing problem yet), if you already have a CPA-specific practice management system with built-in routing (Karbon's workflow assignments, for example, already cover much of this), or if your client base is fewer than 50 clients and manual triage takes under 15 minutes per day.

Routing ROI by Firm Size

The financial case for routing automation scales with firm size. Larger firms have more CPAs, more clients, and more daily inquiry volume — meaning the coordination overhead of manual routing grows super-linearly with headcount.

Triage time estimates are based on 4–5 minutes per inquiry for manual routing (read, look up client, forward, log). Billing rate benchmarks from the Thomson Reuters 2025 State of the Tax Professionals Report. Firms in the 6–12 CPA range typically achieve the fastest adoption because the routing complexity is high enough to justify automation but the client roster (150–300) is small enough to configure in a single session.

The Problem With Shared Inboxes

Most accounting firms land here: a general contact email (info@firmname.com or contact@firmname.com), a client portal with a "send message" button that emails a shared mailbox, and a team of CPAs who check that mailbox sporadically.

The structural problem is ownership ambiguity. When three people see the same email, each assumes someone else will respond. When nobody responds in 2 hours, the client follows up. That follow-up goes into the same shared inbox.

According to the Journal of Accountancy 2025 Practice Management Research, accounting firms lose an average of $14,200 in annually unbilled client-inquiry time — not because the work isn't done, but because it's done under a shared inbox attribution that prevents time tracking.

The second problem is context loss. A question that arrives in the general inbox reaches whoever picks it up first, not the CPA who knows this client's situation. That CPA then spends time re-reading prior-year returns, tax notes, and client correspondence before they can answer a question the assigned CPA would have answered in 90 seconds.

Unrouted client questions: firms lose $14,200+ per year in unbilled inquiry time per the Journal of Accountancy 2025 research.

3 Methods Compared

Method 1: Rules-Based Email Triage

How it works: Incoming emails to a general or contact address are filtered by sender email domain or sender name, matched against a client-to-CPA assignment table, and forwarded to the assigned CPA's inbox with the client context appended.

Setup: Requires a client roster exported from your practice management system with each client mapped to an assigned CPA (email address). The rules run in Gmail or Outlook filter logic, or in an automation platform like Make.com or Zapier.

Accuracy: High for established clients with consistent email addresses. Degrades when clients email from personal addresses (hotmail vs. company domain) or when a client has multiple contacts.

Setup time: 2–4 hours for a firm with 150–200 clients. Ongoing maintenance: 30 minutes per month to update the client-CPA mapping as assignments change.

Best for: Firms with stable client rosters, consistent client email behavior, and no existing practice management system with built-in messaging.

Method 2: Portal-Native Assignment

How it works: Clients communicate exclusively through a CPA-specific client portal (Liscio, TaxDome, Canopy, or Karbon's client tasks). Every message sent through the portal is automatically linked to the client record, which carries the assigned-CPA assignment. The portal routes to the CPA's task queue, not a shared inbox.

Setup: Requires onboarding clients to the portal (typically 2–6 weeks of client migration) and setting up CPA assignment rules in the portal admin. The routing is native to the platform — there's no separate automation to build.

Accuracy: Highest of the three methods. Portal messages carry client identity by design; there's no email-address matching to fail.

Setup time: 4–8 weeks if clients need to be migrated from email. Ongoing maintenance: minimal — portal assignment follows the client record.

Best for: Firms committed to a portal-first communication model, firms implementing a new client communication system, or firms where client email volume is high enough that inbox management is a daily burden.

Method 3: AI-Assisted Classification

How it works: Incoming questions (from any channel) are processed by a classification layer that identifies the question type (tax planning, bookkeeping, payroll, deadline question), the client identity, and the urgency level. The question is then routed to the assigned CPA with a priority tag and a suggested response category.

Setup: Requires an AI classification model (fine-tuned on accounting firm question types), integration with your incoming message channels, and a routing table that maps question types to staff roles (bookkeeping questions go to the bookkeeper first, not the CPA).

Accuracy: Highest for multi-type question routing — it handles the nuance of "is this a bookkeeping question or a tax question?" that rules-based and portal methods can't resolve.

Setup time: 6–10 weeks, including training the classifier on your firm's typical question vocabulary. Ongoing maintenance: monthly review of misclassified questions to improve accuracy.

Best for: Firms with 300+ clients, multiple service lines (bookkeeping, tax, advisory, payroll), and enough question volume to justify a more sophisticated routing layer.

The Workflow Recipe: Method 1 (Rules-Based Email Triage)

This is the most practical starting point for most accounting firms because it uses existing tools, requires no client behavior change, and can be operational within a week.

Ingredients

• A client roster with assigned CPA (Excel or CSV export from your PMS)

• A shared inbox that receives client questions (info@firmname.com)

• An automation platform (Make.com, Zapier, or Power Automate if you're on Microsoft 365)

• Your CPA team's individual email addresses

• Optionally: a Slack workspace for notification delivery instead of email forwarding

Recipe Steps

Step 1: Export the client-CPA assignment table. From QuickBooks Online (client list), Karbon (contacts), or Jetpack Workflow (clients), export a list of every client name, company domain, primary contact email, and assigned CPA. This becomes your routing lookup table.

Step 2: Build the matching logic. For each incoming email to the shared inbox, the automation checks the sender's email domain (company.com) against the assignment table. If matched, route to the assigned CPA. If unmatched (new prospect, personal email address), route to the intake coordinator.

Step 3: Enrich the routing notification. Before routing, the workflow pulls the client's most recent open items from the PMS: current engagements, recent correspondence, any open tasks. The CPA receives the question plus this context in a single notification — not just a forwarded email.

Step 4: Log the inquiry. The workflow creates a task in the PMS (Karbon task, Jetpack Workflow job) tagged as "client inquiry" with the question, client name, and timestamp. This enables inquiry-to-resolution time tracking and ensures unbilled inquiry time is visible.

Step 5: Set the escalation timer. If the assigned CPA hasn't logged a response within 4 hours of routing, the workflow sends a reminder to the CPA and a notification to the manager. This prevents questions from going stale when a CPA is in meetings or out sick.

Worked Example: 12-Partner Firm, 380 Clients

Consider a regional CPA firm with 12 partners, 380 clients, and 6 different service lines. The firm uses Karbon for project management and receives approximately 45–60 client questions per week through a mix of email and the Karbon client portal. Currently, the office manager monitors the shared inbox, manually reads each email, looks up the client in Karbon, and forwards to the assigned partner. This takes 2 hours per day.

After implementing Method 1 with Karbon integration: incoming emails to client@firmname.com fire an email.received webhook into the automation platform. The sender domain is matched against the firm's 380-client roster (maintained in a Google Sheet that syncs nightly from Karbon's API export). For the 85% of questions that come from matched clients, the routing fires within 90 seconds: the question is forwarded to the assigned partner, a Karbon task is created in the correct client engagement, and a Slack notification goes to the partner with the question text. The remaining 15% (personal email addresses, new prospects) go to the intake coordinator queue. The office manager's 2 hours per day on inbox triage drops to 20 minutes of exception review. In a 12-partner firm where each partner bills at $275/hour, recovering 90 minutes of non-billable triage daily across the team represents $74,250 in annual capacity — more than enough to justify the automation.

Comparison: 3 Methods Side by Side

US Tech Automations connects the orchestration layer for Method 1 and Method 3: it handles the client-roster lookup, enriches the routing notification with open engagement context from Karbon or Jetpack Workflow, and manages the escalation timer — so the workflow doesn't require a developer to build or maintain.

Client Question Volume by Question Type

Understanding which question types arrive most frequently helps you prioritize routing rules. Tax planning questions require a senior CPA; bookkeeping clarifications can often be resolved by a staff accountant. Building routing tiers by question type — not just by client assignment — reduces unnecessary partner interruptions.

Distribution based on the AICPA 2025 PCPS CPA Firm survey data on inbound client communication types. The routing layer should map each question type to a responder role — not just a named individual — so that when the assigned CPA is unavailable, the question routes to the next qualified person in the role tier, not to a generic inbox.

Response Time Benchmarks Before and After Routing Automation

Tracking response time is the clearest signal that the routing workflow is functioning. These benchmarks reflect outcomes at firms that have implemented structured routing for 90+ days.

Post-automation benchmarks from the Karbon 2025 Accounting Firm Benchmarks Report (firms using structured routing). Pre-automation figures represent the shared-inbox baseline from the same cohort. Document delivery improvements are highest because those questions don't require CPA judgment — a rules-based redirect to the correct portal link resolves them in seconds once routed correctly.

Implementation Traps to Avoid

Trap 1: Using a single routing rule for all question types. A bookkeeping question routed to a tax partner (because the client's assigned partner is on the tax side) wastes the partner's time and delays the answer. Build at minimum a two-tier routing: questions about open engagements go to the engagement team; questions about general topics go to the assigned contact.

Trap 2: Not accounting for client alias emails. Clients who email from personal Gmail accounts, who switch from a company domain they've left, or who have multiple contacts at the same company will fail the domain-matching logic. Build an explicit override table (contact-email → CPA assignment) alongside the domain-matching rule.

Trap 3: Routing to a team role instead of a named individual. "Route to the tax team" creates the same shared-inbox problem at a smaller scale. Every routing target must be a named individual with a personal queue.

Trap 4: No escalation on unanswered inquiries. Without an escalation timer, a question that lands when the assigned CPA is out of office sits until they return. Define a 4-hour business-hours escalation path to a backup CPA.

Trap 5: Routing without logging. If the routed inquiry isn't also logged as a task in the PMS, the billable time is invisible. Build the PMS task creation into the same automation step as the routing notification.

Citation Benchmarks

According to AICPA 2025 PCPS CPA Firm Top Issues Survey, 62% of accounting firms report that client communication management is a top-5 operational challenge, up from 47% in 2022.

According to the Journal of Accountancy 2025 Practice Management Research, firms with structured inquiry-routing workflows close client questions 3.4× faster than firms using shared inboxes.

According to Thomson Reuters 2025 State of the Tax Professionals Report, 58% of firm staff report spending more than 2 hours per week on email triage that does not result in billable work.

According to the AICPA 2025 PCPS CPA Firm Top Issues Survey, partner satisfaction with internal workflow processes is highest at firms that have implemented structured routing for client communications — with 71% rating satisfaction as "good" or "excellent" vs. 34% at firms without structured routing.

According to Karbon 2025 Accounting Firm Benchmarks Report, firms using a dedicated client communication platform reduce client-question response time from an average of 6.2 hours to 1.4 hours.

Partner time spent on inbox triage: 2+ hrs/week per Thomson Reuters 2025 Tax Season Pulse.

Related Workflow Context

Client question routing is the front-end of a broader client communication workflow. For how routing connects to tax deadline management, see the companion post on . For how the client roster that powers routing also feeds the bookkeeping review queue, see . For how US Tech Automations handles the source-document collection workflow that often precedes client questions, see .

Frequently Asked Questions

How do I handle a client who has questions about two different service lines?

Build a two-question form (or a question-type tag in the portal) that asks the client to categorize their question: bookkeeping, tax, payroll, advisory, or other. The routing logic uses that tag to route to the correct service-line team within the client's assigned group. If the client doesn't categorize, default to the assigned engagement partner who can re-route if needed.

What if a client emails the CPA directly, bypassing the routing system?

Direct-to-CPA emails don't need routing — they're already in the right place. The routing system handles the inbox problem; it doesn't change how direct communications work. The gap to address is ensuring those direct emails are still logged as tasks in the PMS for time tracking, which can be automated with a BCC-to-PMS workflow or an Outlook plugin.

How do I migrate clients from email to a portal?

The most effective approach is phased: start by moving all new clients to portal-native communication, and migrate existing clients at their next engagement kickoff. A brief email explaining the benefits (faster response, secure document sharing, single thread per engagement) with a short video walkthrough converts most clients within two weeks. Clients who strongly prefer email can be accommodated via Method 1 (email triage) while portal adoption grows.

Does routing automation work for firms with remote teams?

Yes — it works better for remote teams because routing removes the hallway handoff that solves routing informally in co-located offices. Remote CPAs with structured routing queues respond faster than co-located teams with informal routing because the queue is explicit and the escalation timer is enforced.

How should I measure whether the routing workflow is working?

Track three metrics: (1) average time from question receipt to first CPA response, (2) percentage of questions routed correctly on the first pass (no re-routing required), and (3) inquiry tasks logged in the PMS as a percentage of total questions routed. A healthy workflow achieves under 2-hour response time, 90%+ first-pass routing accuracy, and 95%+ PMS task logging within 60 days of launch.

When does AI-assisted classification make more sense than rules-based routing?

AI classification earns its complexity when your client questions regularly cross service-line boundaries (a client asks "how does the new 1099-K rule affect our bookkeeping?"), when your staff assignments change frequently, or when you need to route by urgency (tax-deadline questions in April get a different priority than general planning questions). For most firms under 200 clients, rules-based routing is simpler, faster to implement, and adequate.

Workflow Summary

Client question routing is a 3-step recipe: capture the question with client identity, match to the assigned CPA (and service line), and deliver with context. All three methods achieve this — they differ in how much client behavior change and setup investment they require. Rules-based email triage is the fastest path to value. Portal-native routing is the most accurate long-term. AI classification handles the multi-service-line complexity that the others can't.

See how US Tech Automations automates client routing for accounting firms