Ask ten people on a UK team how they would rather be contacted and you will get at least four answers: chat, email, a phone call, or someone wandering over to the desk. The difficulty is rarely a shortage of tools. It is that nobody has agreed which tool owns which job.

Email is not going anywhere, and Onyx Chat is not trying to replace it. What matters is deciding in advance what belongs where — so a question that needs a two-minute answer does not sit in an inbox until tomorrow, and a decision that needs a record does not disappear into a channel you have to scroll back through for ten minutes.

What email still does better

Email is a records system that happens to deliver messages. That is its strength. Anything you might need to find, forward or defend in six months belongs there.

  • Messages to clients, suppliers and anyone outside your organisation.
  • Confirmations: a signed-off quote, an agreed deadline, a change to a contract.
  • Long-form writing where structure matters — a project brief, a proposal, a policy update.
  • Anything with a paper trail attached: invoices, approvals, HR matters.

Email also carries a useful formality. A note that says “as agreed” holds weight in a way that a message in a busy channel does not. If something might later need to be checked by someone outside the team, keep it in email and keep the thread intact. For anything with contractual or legal weight, follow your organisation’s own policy and take advice from your legal or compliance lead rather than relying on a chat thread.

Where Onyx Chat wins on speed

Most of a working day is small stuff: a quick check, a “can you look at this”, a link, a screenshot, a question only one person can answer. Email adds a subject line, a greeting, a sign-off and, often, a delay while someone clears their inbox. Chat removes all of that.

A practical example. A designer needs to know whether the client approved the revised colour palette. In email, that becomes a message sent at 09:20, read at 11:00, answered at 11:15. In a project channel on Onyx Chat, it becomes a question anyone can answer the moment they see it — and everyone else on the project sees the answer too, so nobody asks again.

Three habits make chat work well:

  1. Use channels for topics, not for people. A channel called website-rebuild keeps the whole conversation findable; a group chat with seven names does not.
  2. Reply in threads when a message sparks a side discussion, so the main channel stays readable.
  3. Say what you need. “Any thoughts?” is easy to ignore. “Can you confirm the delivery date by Thursday?” is not.

File sharing: attachments versus shared spaces

This is where the two tools diverge most sharply, and where teams lose the most time.

Email attachments multiply. Three colleagues open the same spreadsheet, make three sets of edits and send back three files called budget-v2, budget-v2-final and budget-v2-final-JS. Nobody knows which one is current, and the answer is usually buried in the newest message rather than in the file name.

Sharing a file in an Onyx Chat channel keeps it next to the conversation that explains it. A version shared there is immediately visible to the group, and comments about it sit alongside the file rather than in a separate inbox thread.

The sensible split is this: chat for working copies and quick reviews, a proper document store for the master version. Agree one canonical location for each important file — your shared drive, project folder or document system — and use chat to talk about it. Then everyone knows where to look and which copy to trust.

Keeping a dispersed UK team organised

Teams spread across London, Manchester, Leeds or entirely at home face a specific problem: people working different hours and different patterns. A message sent at 07:30 by someone starting early should not feel like a demand on a colleague who starts at ten.

A few rules that help:

  • Post one short daily update in a channel rather than messaging five people separately. “On the Davies account today: finishing the report, need the figures by 3pm.”
  • Use threads so people catching up later can read one discussion instead of reconstructing it from fragments.
  • Respect quiet hours. Turn notifications off after a set time, and check your organisation’s policy before treating any message as urgent.
  • Keep personal or sensitive information out of casual channels, follow your data protection policy, and ask your data protection lead if you are unsure.

A rule of thumb you can apply today

If it needs to be found in six months, email it. If it needs an answer in ten minutes, chat it.

That single line settles most arguments. When you are unsure, ask two questions: who needs to see this, and how soon? A message for one person that can wait until tomorrow is an email. A message for the whole project that needs a reply before lunch is chat.

Some cases sit in the middle. A decision made in Onyx Chat that affects a client should be written up and sent by email, with a line explaining where the discussion happened. The record exists, and the speed is not wasted.

Start with one channel and one rule

Do not attempt a company-wide overhaul on a Monday morning. Pick one team, create one channel for a live project, and agree the rule above. After a fortnight, ask what has improved and what has slipped. Most teams find that chat absorbs the small exchanges and email becomes calmer and more useful as a result.

Then write it down in two or three lines, somewhere new starters will see it, and review it in a few months. Tools do not organise teams; agreements do. Decide where each kind of message belongs, say it out loud, and the rest tends to follow.

Photo: Sora Shimazaki / Pexels