Pricing
Book a Demo Register for a Trial
Messaging · Live

Conversations attached to documents.

Stop hunting through email for the thread about that PO. Messages live in OmniPATH with the document attached, the person tagged and the audit trail intact - but they leave as real emails so suppliers can reply from anywhere.

Book a Demo Watch Reels Calculate Your Savings
3
Recipient types
∞
Attachable entities
AWS SES
Native delivery
Team Messaging 3 new
LEDGE → @simon
Just now · auto-routed
@simon Manchester is asking about the FS Foodservice salmon price - it's up 23% vs the 90-day average. Worth raising with the account manager?
Anomaly £480/wk save
Suggested replies
Query FS Foodservice Check contract Find alternative
Why this matters

Email is where context goes to die.

Conversations about a PO live in one inbox. The PO lives in your purchasing system. The credit note lives in another email. When the auditor asks why a payment was short, three places to dig - and only the people on the original thread know the story.

Conversations live with documents

Click any PO, invoice or supplier and you see every message about it. The thread, the attachments, the @mentions, the resolution - all on one panel.

@mention pulls people in

Type @ and pick a teammate. They get a notification, the message lands in their inbox and the message is logged as an assignment against the document. Nothing slips.

Suppliers reply from email

Messages to external recipients leave OmniPATH as real emails via AWS SES. Replies go directly to the sender's business email - no app install or OmniPATH account required for the supplier.

01 / Compose with context

Attach the document. Not a screenshot.

The compose view has a recipient picker that handles three types - internal users, your supplier contacts and one-off external email addresses. Below the body, an entity reference search lets you attach POs, invoices, suppliers and other documents to the thread.

Recipients see the attachments inline. Click an entity reference and OmniPATH opens the document directly - no PDF to download, no spreadsheet to dig out, no "what version were you looking at" confusion.

  • Recipient picker: User · Supplier · External email
  • Entity reference search across PO, PR, GRN, invoice, supplier, document
  • Drafts auto-saved as you type
  • Subject and body fields with rich text support
To
SMSarah Mitchell JMJames (FS Foodservice) accounts@brakes.co.uk
Subject
Discrepancy on PO-08823 - please confirm credit application
Hi James,

Following the short on the salmon order - could you confirm the credit note has been applied against INV-29481 rather than carried to the next invoice?

Looping in @sarah for visibility.
PO-08823
CN-4421
Attach more
Send
02 / @mention system

Type @ - pick a teammate.

Mention works the way you'd expect. Type @ in the body and a search picker appears, querying /memberships/mentionable for users in the current org. Pick one and they're added to the recipients automatically, notified in their bell and the message is logged as an assignment against any attached entity.

Suppliers can be mentioned the same way - when an external email is mentioned, the system handles routing to their address rather than creating an internal assignment.

  • Live search as you type - name or email match
  • Auto-adds mentioned users to recipients
  • Creates a notification + assignment record
  • Mentions render as styled chips in the message body
Need a second pair of eyes on this one - @sa
Mention a teammate
SM
Sarah Mitchell
CFO · sarah@acmehospitality.co.uk
SP
Sam Parker
Site Manager · The Crown
SK
Sanjay Kumar
Procurement Lead
03 / Email-native delivery

Sent as a real email.

Internal users get the message in their OmniPATH inbox. External recipients (suppliers, accountants, anyone with an email address) get a properly formatted email via AWS SES - with the attached entities rendered as buttons that link back to OmniPATH or, where access isn't shared, expand to show the document context inline.

Replies go directly to the sender's business email. The supplier doesn't need an OmniPATH login or app install - they just reply to a normal email.

  • Delivered via AWS SES with sender domain authentication
  • Email preview shown in compose before sending
  • Reply-to routing keeps the thread together
  • External replies appear in your OmniPATH inbox alongside internal ones
Frequently asked

The messaging details.

Does this replace our email entirely?
No. Messaging is built specifically for conversations about purchasing documents - POs, invoices, deliveries, suppliers. Use it for the conversations that need to live with the document. Use Outlook for HR, marketing, or anything else. Supplier replies come back to the sender's business email as normal.
How do attached entities work for suppliers without an OmniPATH login?
For external recipients, attached entities render in the email as a summary card with the relevant fields inline - supplier, totals, dates, key line items. If the supplier has been granted view access via the Supplier Hub, the link opens the live document. If not, the email shows everything they need to action the message without an account.
What's the difference between an @mention and adding someone to recipients?
A mention is an in-body callout - it creates a notification and an assignment record against any attached entities, so the mentioned user has a tracked task to action. Recipients are who receives the message. In practice, mentioning someone auto-adds them to recipients, but recipients added without a mention don't get an assignment - they're just on the thread for visibility.
Can I see all messages about a specific PO or supplier?
Yes. Every PO, invoice, supplier and document page has a Conversations panel showing every message attached to it, in chronological order. This is the audit trail for "what happened with this purchase" - including the original procurement query, supplier negotiation, delivery dispute, credit note resolution and posting confirmation, all linked to one document.
How does the email sender appear to suppliers?
Messages are sent via OmniPATH's AWS SES relay with the sender's name in the From header. The Reply-To is set to the sender's business email so suppliers reply directly to the right person. The outbound message and all attached entities are recorded in the OmniPATH audit trail.
What happens to messages when someone leaves the org?
Messages are owned by the organisation, not the individual. When a user is deactivated, their sent and received messages remain on the document audit trail and stay accessible to anyone with permission to view those documents. Inbox-level visibility transfers to a designated handover user (set per departing user, typically their manager) so nothing in flight gets dropped.
Ready when you are

Stop chasing email threads. Start trusting the audit trail.

Live now in every OmniPATH workspace. Inbox, sent, drafts, @mentions and entity references - included in the platform.

Book a Demo See the Command Centre
30-min demo · We'll set up a sandbox you can message into