WhatsApp vs email for accounting firms: which channel is the file?

The usual version of this comparison is about speed, and it settles nothing useful. Messaging is faster than email in every practice that has tried both, and knowing that does not tell you what to do, because speed is not the thing a professional practice gets wrong.

The question that decides the answer is which channel holds the record. An accountancy practice is required to keep one, is judged on it when something goes wrong, and hands it over when a client leaves. Work out where the file lives and the rest of the channel decision follows from it.

What we'll cover

• The comparison that actually matters
• What has to be on the file
• Advice given in a chat is still advice
• The number belongs to the practice
• Building it with CodeWords
• Retention across two channels
• Identity, and why a message is weak evidence
• A split that works
• Could you reconstruct it?
• Making it survive
• Limits worth knowing about
• What to do first
• Frequently asked questions

The comparison that actually matters

Four properties separate the two channels for a practice, and open rates are not among them.

Retrievability by somebody else. Email sits in a system the practice controls and can be searched by whoever needs it. A chat thread sits on a device and in an account, and retrieval depends on who holds that account.

Durability. Files a practice must keep run to five or six years. Messaging histories are tied to accounts, devices and platform settings, and are not archives.

Attribution. Email carries an addressable sender and a timestamp that survives export. A chat message carries a phone number, which is a weaker link to a person than it looks.

Structure. A thread with three questions, a photograph and an answer buried in the middle is harder to file against a matter than a message with a subject line.

Messaging wins decisively on getting a response. Email wins on all four of the above. That is the trade, and it maps onto a clean division of labour rather than a winner.

What has to be on the file

Anything you would want a third party to see if a client disputes what happened. In practice that means the engagement letter and its scope, anything amounting to advice and the basis it was given on, approvals and instructions, anything about fees, and the identification and risk material behind client due diligence.

The common failure is a conversation that starts on a messaging channel for a good reason, drifts into one of those categories, and never moves. Six months later the only record of a material instruction is a message on somebody's phone.

The fix is a rule people can apply without thinking: anything in those categories goes on the file, in the practice's own system, the same day, by whoever received it. A short note of what was asked, what was said and when is enough. Perfection is not required; a record is.

Advice given in a chat is still advice

The informality of the channel changes how people write and changes nothing about their obligations.

"Would I be better off as a limited company?" answered in a sentence between two other messages is advice, given without the context you would normally gather and without the caveats you would normally attach. It is also the most natural thing in the world to do when somebody asks casually.

Two habits deal with most of this. Answer the question with a conversation rather than a conclusion, because "let's talk that through, it depends on a few things" is both truthful and safer. And where you do give a substantive answer, put it on the file with the assumptions it rested on.

This matters more on a messaging channel than on email, because the register of the channel invites brevity and brevity is where caveats go missing.

The number belongs to the practice

A practical risk that firms discover at the worst moment: staff leave, and on a personal number the client relationship leaves with them.

Personal numbers also mean the practice cannot see the conversation, cannot cover an absence, and cannot produce the history if it is ever needed. The messages are on a device the practice does not own and cannot compel.

The fix is a practice-owned number on a business platform, with access granted to people rather than devices, and a rule that client contact goes through it. That is a policy decision more than a technical one, and it is easier made before somebody resigns than after.

It also solves the version of this that nobody talks about: the partner on holiday whose clients are messaging a phone that is switched off.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which categories of message go out on which channel, what gets copied to the client file, and what has to reach a person.
3. Authorize the connections to your practice management system, your document store, your email, and the messaging platform.
4. Describe the exceptions: a client who has asked for email only, a message that looks like a complaint, anything touching fees, anything that reads like a request for advice.
5. Check for a fortnight that what landed on the file matches what was actually said, because that is the only part of this worth verifying.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Retention across two channels

Running two channels means two retention answers, and most firms have only thought about one.

Client records have long lives: at least five years after the 31 January submission deadline for the self-employed, six years from the end of the financial year for companies (self-employed, company). Anything material that arrives through a messaging channel has to reach a store that will outlive the phone, the app and the member of staff.

The other direction matters too. Data protection expects personal data not to be kept longer than necessary, so a chat history retained indefinitely because nobody chose a period is its own problem. Decide a period, apply it, and make sure the material that belongs on the file has been copied there before the period expires.

Practically: treat the messaging channel as transport and the practice systems as storage. Anything that only exists in the thread is at risk.

Identity, and why a message is weak evidence

Accountancy service providers are supervised under the money laundering regulations, either by HMRC or a professional body, and must carry out customer due diligence and keep the evidence (HMRC guidance).

A messaging channel is a poor place for that evidence. A phone number tells you which account sent a message, not who was holding the device. Numbers are recycled, phones are shared, and a photograph of a passport sent through a chat carries none of the checks a verification process applies.

Which makes the sensible position straightforward: use the channel to ask and to prompt, and collect the actual identification and verification through whatever process your supervisor expects, with the evidence stored on the file. The convenience of the channel is not worth weakening the one part of your obligations that gets examined directly.

A split that works

Messaging for prompting and logistics. Document requests, reminders, status updates, confirmations, quick factual questions, sending a receipt photograph. Anything where the goal is getting somebody to act.

Email or the portal for the record. Engagement letters and scope changes, anything that amounts to advice, approvals and instructions, fees and invoices, finished accounts and returns, complaints, and anything you would want to produce later.

Either, then the file. Anything substantive that arrives on the fast channel gets written to the record the same day. That single rule prevents most of what goes wrong here.

Tell clients the split, once, in plain terms. Most are entirely comfortable being chased by message and sent their accounts by email, and saying so avoids the awkwardness of moving a conversation midway.

Could you reconstruct it?

A useful test, and quick to apply. Pick a client at random and ask whether somebody who has never met them could establish, from the practice's own systems, what was agreed, what was advised, what was instructed and when.

If the answer requires unlocking a phone, the file is incomplete. If it requires a particular person to be in the office, the file is incomplete. Both are fixable in an afternoon for one client, and both are much harder to fix across a whole book after the fact, which is the argument for setting the rule before the volume builds.

Making it survive

One practice-owned number, with access granted to people and removed when they leave.

A written rule about what goes where, short enough to remember.

Same-day copying to the file for anything substantive.

A retention period chosen for each channel, applied rather than assumed.

A periodic check that the file would stand on its own, on a couple of clients picked at random.

Limits worth knowing about

Messaging platforms are not archives, whatever export features they offer.

A phone number identifies an account rather than a person, which matters for anything relying on identity.

Some clients will only use email, and that preference is theirs to hold.

Platform rules change. Business messaging pricing, contact windows and limits have all moved recently, so anything built on assumptions from a year ago is worth rechecking.

A faster channel makes a bad process faster. If requests are vague, moving them to messaging produces quicker confusion.

What to do first

Write the split down, on one page, and tell the practice. Which categories go out by message, which go by email, and the rule that anything substantive gets copied to the file the same day. No software required for any of that.

Two habits make the difference. Put the client relationship on a number the practice owns, because the alternative is discovering the problem on somebody's last day. And apply the reconstruction test to a client or two each quarter, since the gap between what a practice believes is on the file and what is actually there is usually wider than anyone expects.

Frequently asked questions

Which is better for an accounting firm, WhatsApp or email?

They do different jobs. Messaging is the better channel for prompting somebody to act; email or a portal is where the record belongs. The rule that matters is that anything substantive gets copied to the client file.

What has to be kept on the client file?

Engagement terms and scope, anything amounting to advice and its basis, approvals and instructions, fee matters, and client due diligence evidence. Anything you would want a third party to be able to read later.

Is advice given in a chat still advice?

Yes. The informality of the channel changes the register and not the obligations, which is why the safer answer to a casual question is usually to turn it into a conversation.

Can we use staff personal numbers?

It creates real problems. The practice cannot see or cover the conversation, cannot produce the history if needed, and loses the relationship when the person leaves. A practice-owned number avoids all three.

How long do messaging records need to be kept?

As long as the underlying client records: at least five years after the 31 January deadline for the self-employed, six years from the financial year end for companies. Anything material should be copied into a store that outlives the device.

Can client identification be done over a messaging channel?

Use it to ask and to prompt, then collect and verify through the process your supervisor expects. A phone number evidences an account rather than a person, and chat is a weak place for due diligence evidence.

What should we tell clients?

The split, once, plainly: reminders and quick questions by message, accounts, advice and anything formal by email. Most clients find that entirely reasonable when it is explained up front.

How do I know whether our files are adequate?

Pick a client at random and ask whether somebody who has never met them could establish what was agreed, advised and instructed from the practice's own systems. If it needs a phone unlocking, it is not adequate.

Related reading

• Making a document request land
• Setting the channel up as a practice
• Closing the loops a practice leaves open