Client Communication Management for Accountants: A 2026 System That Scales Across the Firm

Why client communication management for accountants breaks down as the firm grows#

Client communication management for accountants is the quiet discipline that decides whether a firm feels calm or frantic. When it works, every client knows where their return stands, every promised document has a home, and no deadline sneaks up on anyone. When it breaks down, the work is still getting done, but nobody can prove it, three people email the same client the same question, and a filing slips because the reminder lived in one preparer's head instead of a system. The strange part is that the communication rarely breaks because the accounting is hard. It breaks because the messages outgrow the place they are stored.

In the earliest days of a practice, a single inbox is a perfectly good client-communication system. You are the only person emailing clients, you remember what you asked for, and you can scroll back to find the last thread. That works right up until it doesn't. Add a second preparer, a bookkeeper, a portal, a shared support@ address, and a couple of hundred clients, and the inbox that used to be a system becomes a pile. The information is all still there, technically, but it is scattered across inboxes, portals, text messages, and the occasional voicemail, with no single record of what was said, promised, or still owed.

This post lays out a client communication management system built for the way accountants actually work: heavy on documents, ruled by deadlines, spiky by season, and bound by a duty to keep client financial data private. We will start with why the inbox overflows in the first place, then build a system piece by piece, triage, per-client threads, templates, batching, deadline discipline, and integration with your practice-management tools and client portal. From there we will cover how the same system holds up when you add staff, and how it survives the January-to-April deluge. At the end, honestly and without hype, we will look at where an AI-native email client like AI Emaily fits, and the one line you should never cross: keep the chasing automatic, keep the financial data human.

Why accountant inboxes overflow: six pressures pulling at once#

An accountant's inbox is not a normal inbox. A marketing manager's inbox is mostly conversation; an accountant's is a logistics operation running through email. Six distinct pressures pile into the same thread list, and each one alone would be manageable. Together, they are why email management for accountants is a genuine profession-specific problem rather than a matter of willpower.

Understanding these pressures is the whole point, because a good system is designed around them, not against them. Here is what is actually landing in the inbox.

• Clients, and lots of them. A solo practitioner might carry a couple hundred clients; a small firm, many hundreds across several staff. Every one of them emails with questions, updates, and the occasional panic, and every one expects to be treated like the only client you have.
• Documents, the endless flow. This is the signature pressure. Bank statements, receipts, W-2s and 1099s, prior-year returns, engagement letters, signed approvals. The work cannot start until the documents arrive, and the documents arrive late, in the wrong format, or one file short, which means the inbox fills with follow-ups asking for the rest.
• Deadlines, immovable and stacked. Quarterly estimates, payroll filings, extension dates, the April and October walls. A missed reply is not just rude; it can be a missed filing. The inbox is where those deadlines get tracked, badly, unless something better catches them.
• Agency notices. A letter from the IRS or a state revenue department turns a quiet week into an urgent one, and the client forwards it with a one-line 'what is this?' that needs a careful, unhurried answer, exactly when you have no time.
• Invoicing and money. Engagement scope, fee questions, unpaid invoices, and the awkward follow-ups that come with them all run through the same inbox as the work itself, tangling the billing conversation with the delivery conversation.
• Advisory and relationship. The higher-value work, planning, structure, the 'should I incorporate?' question, arrives as email too, and it deserves a considered answer, which is hard to give when it is buried under forty document reminders.

Notice how different these six are in the response they need. A document reminder is repetitive and low-judgment; it should take fifteen seconds. An agency notice is high-judgment and needs your full attention. An advisory question is the reason clients pay a premium, and it deserves an unhurried reply. When all six land in one undifferentiated list, sorted only by time of arrival, you pay a tax on every single message: you re-decide, over and over, which kind of thing you are looking at before you can act on it. That constant re-sorting is the real cost of an unmanaged inbox, and it is worst precisely when volume is highest.

The firms that stay calm are not the ones with fewer emails. They are the ones who have stopped treating all six pressures as one undifferentiated stream and built a system that sorts them once, routes each to the right response, and keeps a record of what was promised. That system is what the rest of this guide builds.

The foundation: triage every message into a few clear buckets#

Every good communication system starts with triage, the habit of sorting each incoming message into a small number of buckets the moment you see it, before you decide what to do about it. Triage is not answering; it is labeling. The goal is to look at a message once, decide what kind of thing it is, and route it, so that when you sit down to work you are handling one type of thing at a time instead of context-switching on every click.

The mistake most accountants make is skipping triage and going straight to answering, top of the inbox down. That feels productive but it is not. You answer a quick document reminder, then hit an agency notice that needs deep focus, then a billing question, then an advisory email, whipping your attention between low-judgment and high-judgment work with no rhythm. Triage first, act second. Below is a bucket scheme built specifically for an accounting practice; adapt the names to your firm, but keep the shape.

Six buckets is about the ceiling; four or five is better. If you find yourself wanting a seventh, you are probably slicing too fine, and the overhead of deciding which bucket a message belongs in starts to cost more than the sorting saves. The test of a good bucket scheme is that a message's home is obvious in under two seconds. If you hesitate, the scheme is wrong, not you.

Triage also gives you something an unsorted inbox never can: a picture of your day before you start it. Glance at the buckets and you know instantly that there are three agency notices needing careful replies, a wall of document reminders you can batch, and one advisory question worth protecting an hour for. That picture is what lets you plan instead of react, which is the entire difference between managing your inbox and being managed by it.

Keep a per-client thread: one record of what was promised#

The second pillar is the one that scales, and the one solo habits fight hardest against: a single, findable record per client of what has been asked, sent, promised, and owed. In a one-person practice this lives in your memory, and memory is a wonderful system right up to the moment it fails, at which point it fails silently and you do not find out until a client says 'I sent you that three weeks ago' and you cannot prove otherwise.

A per-client thread is exactly what it sounds like: for each client, one place where the whole conversation is visible in order, including what documents you requested, when, what came back, what is still outstanding, and what you committed to. The point is not tidiness for its own sake. The point is that the answer to 'where does this client stand?' should take five seconds to find, by anyone on the team, without asking the one person who happens to remember.

There are a few ways to hold this, and the right one depends on your tools. Here is how to think about it.

1. 1

   Consolidate the conversation, not just the email

   A client's history is scattered across email, a portal, texts, and calls. You do not need every channel in one literal place, but you do need one canonical record, usually the practice-management client record or a well-kept email thread, that captures what matters: what was asked, what was sent, what is outstanding.

2. 2

   Make 'what's owed' explicit, per client

   The single most valuable field is the outstanding-items list: the documents or approvals you are still waiting on. When this is written down against the client rather than held in your head, follow-ups become mechanical instead of anxious, and anyone can pick them up.

3. 3

   Timestamp the promises

   'I'll have your return done by the 15th' and 'send me the bank statements by Friday' are both promises. Capture them where you can see them. A promise you cannot find is a promise you will break, and broken promises are what erode client trust faster than a late reply ever could.

4. 4

   Make it readable by the whole team

   The per-client record earns its keep the day a colleague covers for you. If the answer to 'what does the Henderson account still owe us?' lives only in your inbox and your head, the firm cannot scale past you. If it lives in a shared record, anyone can step in without a handoff meeting.

The per-client thread is the difference between a firm that is a collection of individual inboxes and a firm that is one organization. It is also the quiet backbone of scope discipline: when what you promised is written down, the extra request that quietly expands an engagement is visible, and you can bill for it or push back, instead of absorbing unbilled scope creep that nobody remembers agreeing to.

Template the repetitive asks so you never write them twice#

A large fraction of an accounting firm's outbound email is not creative writing; it is the same handful of messages sent over and over with the names swapped. The initial document request. The gentle reminder. The firmer reminder. The 'we received your files, thank you' acknowledgment. The engagement kickoff. The deadline-approaching nudge. The 'your return is ready to review' note. If you are writing these from scratch each time, you are paying a writing tax dozens of times a week for messages that should be picked, personalized, and sent.

Templates are the fix, and they do three things at once. They save the minutes it takes to compose. They keep the firm's voice consistent across every preparer, so a client cannot tell whether the reminder came from you or a junior. And they encode your best version of each message, so the reminder that actually gets clients to respond becomes the reminder everyone sends, not a fresh improvisation that might land wrong.

Build your template library around the buckets. Here is a starter set worth having before your next busy stretch.

• Initial document request: warm, specific, with a clear checklist of exactly what you need and a due date. Vague requests get vague responses.
• Reminder ladder: a first friendly nudge, a second more direct one, and a final 'we cannot proceed without these' message, each escalating in tone but never in blame.
• Received-and-thanks acknowledgment: closes the loop so the client knows their files landed and stops wondering. This one email prevents a surprising number of duplicate sends.
• Deadline-approaching notice: a dated reminder tied to a filing or estimate, sent on a schedule rather than when you happen to remember.
• Ready-for-review / ready-to-sign: tells the client the ball is in their court and exactly what to do next.
• Engagement and onboarding: the welcome, the what-to-expect, and the how-we-work notes that set the relationship up cleanly.
• Fee and invoice follow-up: a courteous, templated frame for the money conversation, with the specific figures filled in by a human every time.

One rule keeps templates from feeling robotic: template the structure, personalize the specifics. The skeleton, the greeting, the framing, the call to action, is reused; the details, the client's name, the exact documents, the dates, the numbers, are filled fresh. A good template is a well-built form, not a mass-mailer. The client should feel written to, not blasted at, and the only way to guarantee that is to keep a human in the loop on anything with a specific figure or a personal circumstance in it.

There is a natural boundary here that matters for accountants specifically. The pure logistics messages, the document requests, reminders, and acknowledgments, are safe to standardize heavily because they contain no sensitive figures and no advice. The moment a message includes a specific dollar amount, a tax position, or a recommendation, it crosses out of pure-template territory and needs a human eye. Keep that line bright; it is the same line that governs where automation is safe, which we will come to.

Batch your replies instead of grazing the inbox all day#

Once messages are triaged into buckets and your templates are ready, the way you actually work through them matters as much as the sorting. The enemy is grazing: checking email constantly, answering one message here and one there, letting a new arrival yank your attention off whatever you were doing. Grazing feels responsive, but it is the single most expensive habit in inbox management, because every switch between a document reminder and a tax return costs you the minutes it takes to reload the harder task into your head.

Batching is the antidote. Instead of a hundred small interruptions, you handle email in a few dedicated blocks a day, and within each block you work one bucket at a time. All the document reminders in one pass, all the billing follow-ups in another, the advisory questions in a protected focus block where nothing else is allowed in. Working one bucket at a time means one mode of thinking at a time, and one set of templates open at a time, which is where the real speed comes from.

A workable daily rhythm for an accountant looks something like this.

1. 1

   Morning triage sweep (10 minutes)

   Sort everything that came in overnight into buckets. Do not answer yet, except for genuine emergencies. You are building the map of your day, not driving it.

2. 2

   First reply block: logistics (20-30 minutes)

   Blast through the document requests, reminders, and acknowledgments using templates. This is high-volume, low-judgment work; do it fast, in one mode, while your focus is fresh enough to spare.

3. 3

   Deep-work block: the actual accounting

   Close the inbox entirely. Returns, reconciliations, and agency-notice responses need uninterrupted attention. Nothing in the inbox is more urgent than protecting this block, because this is the billable work only you can do.

4. 4

   Afternoon reply block: judgment work (30-45 minutes)

   Handle the advisory questions, the careful notice replies, and the billing conversations, the messages that need a human brain and a personal touch. Give them the focus the morning logistics did not deserve.

5. 5

   End-of-day sweep and set-ups

   Clear FYI items, confirm nothing deadline-linked is stranded, and queue tomorrow's reminders. Leave the inbox sorted so tomorrow's triage sweep starts from calm, not chaos.

The resistance to batching is always the same fear: 'but what if a client needs something urgently and I don't see it for hours?' This is where triage and batching work together. Genuine emergencies, an agency notice with a fast deadline, a client in real distress, get caught in the triage sweep and can jump the queue. Everything else can wait two or three hours without any harm, and the honest truth is that clients do not notice the difference between a reply in ten minutes and a reply in three hours nearly as much as accountants fear they do. What they notice is a reply that is clear, complete, and correct, which is exactly what batched, focused work produces and frantic grazing does not.

Deadline discipline: never let a filing live only in the inbox#

For most professions, a missed email is an awkwardness. For an accountant, a missed email can be a missed filing, a penalty, and a very unhappy client, which is why deadline discipline deserves its own pillar rather than being folded into general triage. The core principle is simple and non-negotiable: no deadline should live only inside an email thread. The inbox is where deadlines arrive; it must never be where they are stored.

The failure mode is familiar. A client emails a document, you note mentally that the extension is due in three weeks, the thread scrolls down as forty newer messages pile on top, and the deadline surfaces in your memory two days too late. The email did its job, it delivered the information, but the inbox is a terrible calendar, and treating it like one is how good firms miss dates they absolutely knew about.

Here is how to make deadlines safe.

1. 1

   Extract every deadline out of the inbox immediately

   The moment a deadline appears in an email, it goes into a real system, your practice-management tool, a workflow tracker, or a calendar, with the client and the obligation attached. The email can stay for reference, but the deadline no longer depends on the email being seen again.

2. 2

   Attach the deadline to a client, not a task in your head

   'File the Rossi extension by the 15th' is safe when it lives against the Rossi client record with a date the whole team can see. It is unsafe when it lives as a nagging feeling you will remember to check the thread.

3. 3

   Schedule the reminders backward from the date

   Do not remind the client when you happen to think of it. Set the nudges in advance, two weeks out, one week out, two days out, so the follow-up fires on a schedule regardless of how busy you are the week it matters.

4. 4

   Separate 'client owes us' from 'we owe the agency'

   Track both, but know which is which. A document you are chasing from a client is a different risk than a filing you owe a tax authority. The second one has no grace and no excuse, so it gets the most conservative buffer.

Deadline discipline is where communication management and risk management become the same thing. Every other pillar in this guide makes your firm calmer and faster; this one keeps it out of trouble. It is also the pillar clients feel most, even though they never see it, because the firm that never misses a date and never lets a document request go stale simply feels more trustworthy than the one that occasionally panics near a filing wall. That felt reliability is worth more than any single fast reply.

Integrate with practice management and the client portal#

Everything so far can be done inside email alone, but accountants rarely live in email alone. Most firms run a practice-management platform, a client portal for secure document exchange, and often a workflow tracker on top. A client communication management system that ignores those tools ends up fighting them, with the same information half-tracked in two places and neither one trustworthy. The system works best when email and the firm's other tools play defined roles instead of overlapping.

The cleanest division of labor treats each tool as good at one job. Think of it this way.

• Email is the conversation layer. It is where the human back-and-forth happens, questions, answers, nudges, warmth. It is fast and universal and clients live in it, which is exactly why it is a bad place to store the authoritative record.
• The client portal is the secure exchange layer. Sensitive documents, signed forms, and anything with real financial data belong in a portal built for it, not as email attachments floating around unencrypted inboxes. The portal is also where the 'has the client uploaded it yet?' status can live cleanly.
• Practice management is the system of record. The client's standing, the outstanding-items list, the deadlines, the engagement scope, the promises, all belong in the tool built to be the single source of truth, readable by the whole team.
• The workflow tracker is the status layer. Where each job sits, waiting on client, in preparation, in review, ready to file, so the firm can see its whole book of work at a glance rather than reconstructing it from inboxes.

The reason to draw these lines clearly is that the portal-versus-email question is really a security question. Financial data, statements, returns, anything with real numbers and identifying detail, should travel through the secure portal, not as email attachments, both because it is safer and because it keeps the sensitive material out of the sprawling, searchable, forwardable inbox. Email is for 'I've uploaded your documents, please take a look' and 'your return is ready to review in the portal'; the portal is for the documents themselves. Getting this split right is what lets you automate the email conversation aggressively without ever automating your way into a data-privacy problem.

None of this requires ripping out your existing stack. If you already run a practice-management platform and a portal, the communication system in this guide sits on top of them: triage and templates and batching live in email, the record of what's owed and the deadlines live in practice management, and the sensitive documents live in the portal. The system is the coordination between them, held together by the discipline of always putting each kind of information in the place built to hold it.

Managing communication across a firm and its staff#

A system that works for a solo practitioner has to survive contact with a team, and this is exactly where most informal setups collapse. The habits that felt like personal preferences, whose inbox a client emails, who remembers what was promised, who owns the follow-up, turn into structural problems the moment more than one person is involved. When client communication scatters across three inboxes and a portal with no single record of what was promised, follow-ups get missed, two people answer the same question differently, and scope creep goes unbilled because nobody remembers who agreed to what.

Scaling the system across staff means answering a few questions explicitly that a solo never had to ask.

1. 1

   Decide who owns each client relationship

   Every client should have a clear primary point of contact, even if several people touch the work. Ownership prevents the two-people-answer-differently problem and gives the client one consistent voice. Shared inboxes without clear ownership are where messages fall between the cracks.

2. 2

   Standardize the templates firm-wide

   The whole firm sends the same document request, the same reminder ladder, the same acknowledgment. Consistency is not bureaucracy here; it is what makes the firm feel like one organization rather than a loose federation of individual styles, and it means a junior's reminder reads as professionally as a partner's.

3. 3

   Make the per-client record the shared source of truth

   The outstanding-items list, the promises, the deadlines live somewhere every authorized team member can see, not in one person's head or private inbox. This is what lets anyone cover for anyone, and what lets a partner check a client's standing without interrupting the preparer.

4. 4

   Route the shared inbox with rules, not luck

   A support@ or info@ address needs a defined path: who triages it, how messages get assigned, how a hand-off is recorded. An unmanaged shared inbox is where accountability goes to disappear; a managed one is a genuine asset.

5. 5

   Review scope against what was promised

   Because the promises are written down per client, the firm can see when a request has quietly expanded the engagement, and decide to bill it or hold the line, rather than absorbing unbilled work nobody noticed agreeing to.

The payoff of getting this right at the firm level is concrete: integrated, well-run client communication is repeatedly credited with saving firms meaningful hours every week during peak season, not by making anyone type faster, but by eliminating the duplicated effort, the re-asking, and the reconstructing-from-inboxes that an unmanaged setup forces. The hours saved are the hours nobody was billing for anyway, which is why the ROI on a real communication system tends to be clearest in exactly the sub-segment that feels too busy to set one up: the small growing firm.

There is a cultural piece too. A firm-wide communication system only works if the firm actually adopts it, which means the partners use it, the templates are genuinely good enough that people prefer them to improvising, and the record-keeping is light enough not to feel like punishment. A system that is technically correct but that staff route around is worse than no system, because now the truth is split. Build for adoption: make the right way the easy way, and the system holds.

Surviving the seasonal spike without the system collapsing#

For most accounting firms the year is not flat. Tax preparers can see inbound volume rise dramatically between January and April 15, with call and email traffic climbing well beyond the off-season baseline. Bookkeepers and payroll services ride a smaller but relentless monthly cycle. Whatever the shape, the defining feature of accounting communication is that the busiest weeks and the highest volume land at the same time, which is the exact opposite of how you would design it if you could.

A communication system proves its worth in the spike, not in the quiet months. In January, the difference between a firm with a system and a firm without one becomes stark, and it comes down to what the spike does to each. The unmanaged firm's inbox simply grows until it is a wall, and the same document reminders that were annoying in November become impossible to keep up with when there are ten times as many of them. The managed firm's system bends but holds, because the parts that scale, triage, templates, scheduled reminders, were built for exactly this.

A few season-specific moves make the difference.

• Front-load the document requests. Send the initial requests and checklists early, before the deluge, so the follow-up chasing is spread out rather than crammed into the final weeks. The document-collection loop is the bottleneck; starting it early is the single highest-leverage seasonal move.
• Lean hardest on templates and scheduled reminders exactly when you have the least time to write. The reminder ladder that fires on a schedule does not care that it is April; it just works.
• Protect the deep-work blocks more fiercely, not less. The instinct in the spike is to abandon batching and graze the inbox in a panic. That is precisely backward: the busier you are, the more the cost of context-switching hurts.
• Set client expectations up front for the season. A start-of-season note about response times and the fastest way to reach you in a genuine emergency buys you the grace to work in blocks instead of reacting to every ping.
• Watch the deadline tracker like a hawk. The spike is when a stranded deadline is most likely and most costly. This is the one pillar you tighten, not relax, under pressure.

The honest reason the spike is worth planning for is that it is the moment the whole practice is most exposed. A solo practitioner has no one to absorb the overflow; a small firm's staff are all maxed at once. The repetitive communication, document chasing, status updates, the same three questions answered fifty times, is not the hard part of the work, but in the spike it crowds out the hard part, the actual returns, until the billable work is being done at night because the days were eaten by the inbox. A system that handles the repetitive communication is not a nicety in season; it is what keeps the billable work in daylight hours.

How AI Emaily helps: automate the chasing, keep the data human#

Everything above is a system you can run by hand, and firms do. But the repetitive parts, the triage, the document reminders, the status updates, the reminder ladders, are exactly the kind of high-volume, low-judgment work that an AI-native email client is built to take off your plate. Here is where AI Emaily fits into the system this guide describes, said plainly and without overselling it: it does the mechanical parts of communication management faster than you can, and it stays out of the parts that need your judgment.

AI Emaily is an AI-native email client that connects your Gmail, Outlook, and other accounts into one unified inbox, so the scattered-across-inboxes problem, the specific thing that breaks as a firm grows, has a single surface again. On top of that unified inbox, its AI does the parts of the system that are mechanical.

• AI triage does the sorting for you. Instead of manually bucketing every message, the AI reads incoming email and sorts it, so the document requests, the deadline-linked items, the agency notices, and the advisory questions are separated the moment they arrive. You get the map of your day without building it by hand.
• Drafts wait for you, in your voice. For the repetitive replies, the document reminders, the acknowledgments, the ready-for-review notes, AI Emaily drafts the message in your own writing style and leaves it waiting. You review and send, or edit first. The blank page is gone; the judgment stays yours.
• Copilot and Autopilot let you choose the leash. In Copilot mode, nothing goes out without your approval, every draft is reviewed by a human before it sends, which is the right default for a firm handling client financial matters. In Autopilot, you can let the genuinely routine, low-risk flows, a recurring document reminder, a 'we received your files' acknowledgment, send on their own, within limits you set.
• The unified inbox is the single surface the firm was missing. One place where the conversation lives, searchable, consistent, and shared, so a colleague covering an account is not spelunking through someone else's mailbox to find what a client was promised.

The line that matters most for accountants is where automation stops, and AI Emaily is built around it rather than pretending it does not exist. The recurring, logistical, no-sensitive-data messages, the document requests, the reminders, the status updates, are the clean fit for automation, because they contain no figures, no advice, and no judgment. The moment a message involves a specific dollar amount, a tax position, an agency notice, or a piece of advice, it belongs to a human. AI Emaily's design keeps that boundary bright: automate the chasing, keep the financial data and the advice human-reviewed. That is not a limitation bolted on as a caveat; it is the correct shape of the tool for a profession bound by a duty of care over client data.

Two more things make this safe to actually use in a practice. Every action the AI takes is undoable, so an autosent reminder or a triage decision is never a one-way door, and everything is recorded in an audit trail, so you can always see exactly what was done on your behalf and when. For a firm that has to be able to account for its client communications, undo plus audit is not a nice extra; it is the difference between a tool you can trust with client relationships and one you cannot. You stay server-authoritative over your own practice: the AI drafts and proposes, you decide, and the record shows it.

To be clear about what this is and is not: AI Emaily is a communication and inbox tool, not a tax or accounting engine. It does not give tax or legal advice, it does not make filing decisions, and it does not replace your professional judgment or your practice-management platform. It handles the email around the work, the chasing, the sorting, the routine drafting, so you and your team spend less time managing the inbox and more time on the accounting only you can do. This guide is about communication management, not tax or legal advice; for the accounting itself, your professional judgment and your firm's obligations always govern.

Putting the system together#

Client communication management for accountants comes down to refusing to let one overflowing inbox stand in for a system. The inbox overflows for good reasons, six real pressures, clients, documents, deadlines, agency notices, invoicing, and advisory, all pouring into one undifferentiated stream, and no amount of working harder fixes a structural problem. What fixes it is structure: triage every message into a few clear buckets, keep one findable record per client of what was promised and what is owed, template the repetitive asks, batch your replies instead of grazing all day, and never let a deadline live only in the inbox.

That system scales because it does not depend on any one person's memory. Layer it over your practice-management platform and secure portal, giving each tool its proper job, email for the conversation, the portal for sensitive documents, practice management for the record of truth, and it holds up as you add staff and as the January-to-April spike hits. The firms that stay calm in season are not the ones with fewer emails; they are the ones whose repetitive communication runs on rails instead of on adrenaline.

And where the rails can be automated, automate them, with a clear line you never cross. Let an AI-native email client like AI Emaily take the triage, the reminders, the routine drafting, and the status updates off your plate, in your own voice, with Copilot approval, undo, and a full audit trail. Keep the financial figures, the advice, and the judgment human. Do that, and the inbox stops being the thing that runs your firm and goes back to being what it should have been all along: a tool your firm runs.