Sign inEvery client conversation, attached to the client — not buried in one inbox
Connect a Microsoft 365 mailbox read-only and incoming email is logged against the right client, with attachments filed to that client's documents. WhatsApp is two-way and visible to everyone on the team with access to the client.
Oblix client communications ties email and WhatsApp to the client record rather than to a single person's inbox. Inbound Microsoft 365 email is synced read-only and logged against the matching client, with attachments filed to that client's documents; WhatsApp is two-way and captured against the client, visible to everyone on the team with access to it. Oblix never sends, drafts or modifies email in anyone's mailbox.
- Connects a Microsoft 365 mailbox read-only and logs incoming email against the matching client
- Files email and WhatsApp attachments to the client's documents automatically
- Captures two-way WhatsApp against the client, with delivery and read status
- Shares WhatsApp, phone notes and post across everyone with access to the client, while keeping synced email private to the mailbox owner
- Filters personal, newsletter and automated mail out of the client view by default
"Who's been talking to this client, and where did that file go?"
The conversation with a client is scattered. The accounts query sits in one fee-earner's Outlook, the WhatsApp reply is on someone's phone, and the bank statement that came in last week is an attachment nobody else can find. When a partner asks what's happening with a client, or someone covers for a colleague on holiday, the only honest answer is "let me ask". Nothing is wrong with the work — it is just that the record of it lives in individual inboxes instead of with the client.
The client record holds the conversation
Connect a mailbox and incoming email is logged against the matching client, so the next person opening that client sees the same history. WhatsApp messages and their attachments are captured against the client and shared across the team. Documents that arrive by email or WhatsApp are filed to the client's documents automatically, so nobody hunts through someone else's mailbox for a statement. Phone notes and post logged against a client are shared in the same way, so the picture of who said what sits in one place.
How it works
Four steps take client correspondence from scattered inboxes to a shared client record — read-only on mail, two-way on WhatsApp, and filtered to keep the view useful.
Connect a mailbox, read-only
Oblix connects to Microsoft 365 with read-only permission (Mail.Read). It reads the inbox to log correspondence and never sends, drafts or changes anything in the mailbox. Sync starts from the moment the mailbox is connected.
Email is matched to the client
Each incoming message is matched to a client by the sender, then logged against that client. Oblix stores a short preview of the message rather than the full body, and files any attachments to the client's documents.
WhatsApp, both ways
Inbound client WhatsApp messages and their attachments are captured against the client. Staff reply from inside Oblix — text, documents, images or approved templates — with delivery and read status tracked. This uses the WhatsApp Business API, configured once by the firm.
Shared by the client, owned by the team
WhatsApp, phone notes and post logged against a client are visible to everyone on the firm with access to that client — they belong to the client, not the individual. Synced email stays private to the mailbox owner.
Noise filtered out
The comms view shows work-related correspondence by default and keeps personal, newsletter and automated mail out of the way, so the client record stays useful rather than cluttered.
Read-only on inbound mail, on purpose
Oblix never sends from anyone's mailbox. The Microsoft 365 connection is read-only, so connecting it cannot change, send or delete a single email. Where a reminder or reply does go out, a person reviews it and clicks send — the system drafts and queues, it does not send on its own. For practices nervous about handing a tool access to client correspondence, that line is firm and easy to explain to a partner.
What it gives the practice.
Inbound Microsoft 365 email synced read-only and matched to the client, with attachments filed to documents
The client's correspondence and files live on the client record, so covering for a colleague or briefing a partner takes seconds, not a round of "can you forward me that?"
Two-way WhatsApp captured against the client, with delivery and read status
Client WhatsApp stops living on one person's phone — the team can see the thread and reply from inside Oblix, with attachments filed automatically.
WhatsApp, phone notes and post are firm-wide; synced email stays private to the mailbox owner
Shared conversation where it should be shared, with personal mailboxes kept private — nobody has to choose between visibility and discretion.
Read-only mail access (Mail.Read only); Oblix never sends, drafts or modifies email
You can connect a mailbox without worrying the tool will ever send or alter a message — an easy yes for a cautious partner.
Questions practices ask
Can Oblix send email on my behalf?
No. Oblix connects to Microsoft 365 with read-only permission and never sends, drafts or modifies email in anyone's mailbox. It reads incoming mail to log it against the right client; it cannot send. Where a reminder or reply is needed, a person reviews the draft and clicks send themselves.
Who can see a client's emails and WhatsApp messages?
WhatsApp messages, phone notes and post logged against a client are visible to everyone on the firm with access to that client, because those communications belong to the client rather than the individual. Synced email is different: it stays private to the owner of the mailbox it came from. So shared channels are shared, while a person's connected inbox remains theirs.
How does an email get attached to the right client?
Each incoming message is matched to a client by the sender address and logged against that client automatically. Any attachments are filed to the client's documents at the same time, so a bank statement or letter sits on the client record rather than stuck in one inbox. Oblix stores a short preview of the message rather than the full email body.
Does WhatsApp work, and what is needed to set it up?
Yes — WhatsApp is two-way: inbound client messages and attachments are captured against the client, and staff reply with text, documents, images or approved templates from inside Oblix, with delivery and read status tracked. It uses the WhatsApp Business API, so the firm configures its WhatsApp Business credentials once; it does not work with personal WhatsApp accounts. Free-text replies are available within WhatsApp's 24-hour window, with pre-approved templates outside it.
Will Oblix import all our historical email when we connect a mailbox?
No. Email sync starts from the moment a mailbox is connected and logs new incoming mail from then on, rather than backfilling old correspondence. Oblix reads the inbox and stores a short preview of each message plus its attachments, not the full email body.
Give the practice one place to see the work.
Bring every client, job, deadline, document, chargeable hour and client conversation into a single operating view for the whole firm.