PLATFORM · COMMUNICATIONS

The thread about the late lot lives in someone's Slack DMs. The order record knows nothing.

Trade ops teams generate hundreds of conversations a week — about orders, production lots, shipments, invoices, claims, samples, internal coordination. The thread with the factory about the late lot lives in someone's Slack DMs. The discussion about the amendment lives in an email thread on a procurement manager's laptop. The client's question about lead time lives in WhatsApp messages no one else can search. The record of the order knows nothing. Six months later, an audit asks "why did we accept the split shipment?" and nobody can find the conversation that explained the decision.

Messages in TradeOS anchors every thread to the entity it's about, surfaces who you're talking to (client / supplier / logistics / your team), lets any line become a task in one click, and keeps internal team coordination inside the same thread without exposing it to the counterparty. The conversation lives on the record. The record knows what was said.

Book a demo See pricing →

Entity types

Order, shipment, lot, invoice, claim, sample, task, direct message

Counterparty kinds

Client, supplier, logistics, internal team

Edit window

15 min · then immutable

Tasks from chat

One click from any selected line

Production lot PL-2026-067 · Crescent Manufacturingsupplier · Crescent Manufacturing · 4 messages

Open production_lot →

Today · April 14

Crescent Manufacturing9:14

First lot of 300,000 pcs at 80% complete. AQL 2.5 inspection scheduled Tuesday morning. SGS report will follow within 48 hours of inspection. Photos of the QC samples attached.

Carmen Aldridge · you9:22

Got it — please send the SGS report directly to [email protected] and copy me. Also confirm: are we still on track for the Apr 26 cut-off at Port Klang?

Crescent Manufacturing9:48

Confirmed — we'll have the SGS report by Wednesday EOD. Apr 26 cut-off is tight; we're loading second container Apr 25 to be safe. Will share BOL draft when it's issued.

→ Task · Follow up on SGS report by Wed EOD · assigned to James Chen · due Apr 16

James Chen · ops manager10:03internal · team only

Heads up team — Crescent has slipped twice on test reports this quarter. If we don't have the SGS by Wednesday EOD let's escalate to Wei (their plant manager) directly.

Internal note — visible to your team only

Type your reply…

Send · ⌘↵

The operator Messages page — entity-anchored threads on the left, active conversation with task pills and internal notes on the right.

WHEN CONVERSATIONS LIVE OFF-RECORD

Trade conversations are not channels. They're records.

A trade conversation about a production lot, an order amendment, or a quality dispute is a business record — not a Slack channel that scrolls away. Most platforms treat it as the latter; the cost shows up six months later when no one can find the conversation that explained the decision.

01 · INBOX SPRAWL

Conversations live in inboxes, not on records.

The thread with the factory about the late lot lives in someone's Slack DMs. The discussion about the amendment lives in an email thread on a procurement manager's laptop. The client's question about lead time lives in WhatsApp messages no one else can search. The record of the order knows nothing.

📧 inbox💬 DM📱 phone↛ order record

02 · HANDOFF LOSS

Every handoff means rebuilding the context.

The ops lead is on PTO. A colleague picks up the order, opens it in the platform, and sees a clean status row — but nothing about the three-message back-and-forth on the QC concern, the agreed split-shipment plan, or the supplier's promised remedy. The conversation existed; the platform doesn't have it.

person Ahandoffperson B↛ zero context

03 · ACTION DRIFT

What was decided becomes what was discussed.

"Send the SGS report by Wednesday." Said in a message. Agreed in a message. Forgotten in a message. Decisions made inside conversations need to become tracked tasks on the record — not stay buried in the thread until someone finds them too late.

decision→chat history⚠ never executed

WHAT IT DOES

What the Messages module does

Open any order, see the conversation about it — without leaving the platform.

A thread in TradeOS is never abstract — it carries a threadType and entityId pointing at the order, shipment, production lot, invoice, claim, sample, or task it's about. Eight thread types in total. Open an order; the thread is there. Open Messages; the thread shows the entity it belongs to in a badge above the preview. Open the entity from the thread header with one click. No more "which channel was that in" — the conversation lives on the record it's about.

THREAD TYPES · 8 ENTITY-ANCHORED

📦

OrderRD-2026-018 → consignee, amendments, LC questions

🚢

ShipmentSH-2026-088 → vessel updates, BOL, customs

🏭

Production lotPL-2026-067 → AQL inspections, QC concerns

🧾

InvoiceINV-2026-077 → payment, dispute, balance

⚠

ClaimCLM-2026-014 → quality, damage, short-ship

🧪

SampleSMP-2026-142 → dispatch, evaluation, feedback

✓

TaskTSK-2026-089 → coordination on a tracked task

💬

Direct (internal)no entity → team-only or 1:1 internal chats

142 active threads · all anchored to a record or to your team

Filter your inbox by who you're actually talking to — client, supplier, logistics, your team.

Every counterparty in TradeOS is tagged with a relationship kind: client (the buyer), supplier (the manufacturer), logistics (the forwarder, carrier, customs broker), or internal (your own team). The Messages inbox carries that tag onto every thread, and the filter strip lets the operator narrow to one relationship at a time. Sales follow-ups go under Client. Production check-ins go under Supplier. BOL discussions go under Logistics. Team coordination goes under Internal. The signal-to-noise ratio in the inbox shifts from "every message" to "every message from the side of the trade you're working on right now."

RELATIONSHIP FILTER · 4 KINDS

client5 threads · 1 unread

Brevin Health EU · SH-2026-088

Norwell Components UK · RD-2026-091

Iberica Healthcare · INV-2026-064

supplier4 threads · 2 unread

Crescent Manufacturing · PL-2026-067

Sapphire Industries · SMP-2026-142

Crescent Manufacturing · QC-2026-0142

logistics2 threads · 0 unread

COSCO Booking Desk · SH-2026-088

DHL Forwarder · SH-2026-091

internal1 thread · 0 unread

James Chen · ops handoff

filter strip: All · Client · Supplier · Logistics · Internal — one click narrows the inbox

Decisions made in chat become tracked tasks on the record — not buried in the thread until someone finds them too late.

Decisions made in conversations don't have to stay there. Highlight any text inside a message — a deadline, an action item, an agreed remedy — and a floating "Create task" button appears above the selection. Click it; the task modal opens with the selected text prefilled as title and description, the source message attached, and the thread's entity context inherited. The composer also carries a "Create task" button for proactive task creation when no specific message is the source. Tasks spawned from a message appear as a pill directly under it in the thread, so the conversation always shows which lines became commitments. Composer-spawned tasks land in a footer summary at the bottom of the timeline.

TASKS FROM CHAT · 2 ENTRY POINTS

Select text in any message

Highlight the action item, deadline, or agreed remedy.

Confirmed — we'll have the SGS report by Wednesday EOD. Apr 26 cut-off is tight.

Modal prefilled · source message attached

Title and description carry the selection; assignee, due date, priority set on creation.

Pill appears under the source message

The thread keeps a visible link from the line that became a task to the task itself.

→ Task · Follow up on SGS report by Wed EOD · assigned to James Chen · due Apr 16

Tell your team what you really think about the supplier — without the supplier ever seeing it.

The hardest part of customer-facing communication isn't the customer-facing part — it's the team coordination that happens around the customer-facing part. Most platforms force operators to spin up a separate Slack thread to coordinate on a reply, then forget which conversation belonged to which. TradeOS keeps both inside the same thread: flip the "Internal note" toggle in the composer, post your team-side message, and it saves with audience scoped to operator users only — invisible to the client, supplier, or logistics partner on the other side of the thread. Distinct styling makes internal notes visually obvious so no one posts to the wrong audience by accident. Every internal note is part of the same chronological timeline as the external messages; the team coordination context lives next to the customer context.

INTERNAL NOTE · SAME THREAD · OPERATOR-ONLY AUDIENCE

Crescent Manufacturing9:48visible to all

Confirmed — we'll have the SGS report by Wednesday EOD.

James Chen · ops manager10:03internal · team only

Heads up team — Crescent has slipped twice on test reports this quarter. If we don't have the SGS by Wednesday EOD let's escalate to Wei directly.

Carmen Aldridge · you10:08internal · team only

Agreed. I'll send a Tuesday-evening nudge if there's no SGS update by then. Tracking on TSK-2026-091.

Carmen Aldridge · you10:12visible to all

Thanks for confirming. We'll plan around the Wednesday EOD SGS report — will share customs prep status once we have it.

Crescent only sees the external messages (the SGS confirmation and Carmen's reply). The two internal notes are visible to the EDMA team only.

HOW IT CONNECTS

Every other section reads from this thread — every order page, every shipment, every task.

Messages isn't a separate inbox living next to the platform — it's a layer that lives on every entity that already exists, with bidirectional connections to Tasks and Documents.

Messages at the center · 6 connected sections · every thread anchored to an entity (or marked direct/internal).

Section	What flows	What you see
Orders	One thread per order · subject + consignee + amendments	Order detail surfaces the thread inline
Production	One thread per lot · QC questions, inspection coordination	Lot detail shows the thread next to QC results
Shipments	One thread per shipment · forwarder, carrier, BOL discussion	Shipment detail shows the thread next to tracking
Finance	One thread per invoice · payment, balance, dispute	Invoice detail shows the conversation
Tasks	Bidirectional: tasks created from messages, messages reference source tasks	Task pills appear under spawning messages
Documents	Message attachments stored as documents (linked by documentId)	Attachments land in the documents library

ON THE ROADMAP

Where Messages is heading next.

Today, Messages is an in-app messaging layer — entity-anchored, relationship-aware, with tasks-from-chat and internal notes. The next milestones extend it outward to the channels trade actually runs on, plus the in-thread affordances (attach, mention) that are currently scaffolded but not yet wired.

v1.5 · NEXT

Channel routing

Inbound messages from WhatsApp Business, Telegram, Email (Gmail · Outlook · IMAP), and SMS via Twilio land in the same threads, anchored to the same entities. Outbound replies route back through the same channel. Counterparties keep using their existing apps; operators keep using TradeOS Messages.

messages.channel column + inbound webhooks · provider registry already scaffolded at server/src/modules/integrations/providers/

v1.5 · NEXT

Attach & Mention in composer

The composer's Attach button (link a file from the documents library or upload a new one) and @Mention picker (tag teammates or counterparty contacts) are currently scaffolded with disabled "coming soon" tooltips. Wiring them up is a near-term unlock — the data model already supports it (message attachments and mentions fields exist on the DTO).

UI stubs already in place · backend fields live

v2 · LATER

Inline translation

Auto-translation for cross-language threads (Mandarin ↔ English the most common case for our footprint), with a trade-terminology dictionary that preserves Incoterms (CIF / FOB), LC terms, QC standards (AQL / EN 455), and product references rather than translating them word-for-word. Operators see source + translated; counterparties see their native language.

deferred to v2 · LLM-backed with trade-specific overrides

v2 · LATER

Voice notes & meeting recap

Voice memos in WhatsApp / WeChat threads transcribed inline. Calendar meetings (Zoom, Meet, Teams) summarized into thread posts on the relevant order or claim. Both depend on channel routing landing first; both are paced behind operator demand once the in-app foundation is settled.

depends on v1.5 channel routing

We list the integration backlog explicitly because the alternative — claiming WhatsApp / Telegram / WeChat / SMS as built when they're not — wastes a buyer's evaluation cycle and our reputation. Today's Messages is in-app; tomorrow's is the same threads, more channels.

VS. ALTERNATIVES

Where Messages fits versus the tools that already organize conversations.

Capability	TradeOS	Slack	MS Teams	Front	HubSpot
Threads anchored to order / shipment / lot / invoice / claim / sample / task	✓	—	—	—	deal only
Relationship-aware inbox (client · supplier · logistics · internal filter)	✓	—	—	tags	contact type
Create task from selected text in a message	✓	via app	via app	via app	workflows
Internal notes inside a counterparty thread (audience-scoped)	✓	—	—	✓	deal notes
15-min edit window then immutable audit trail	✓	unbounded edit	unbounded edit	email immutable	activity log
Connected to order / lot / shipment data inside the same platform	✓	—	—	—	CRM only
Channel routing (WhatsApp / Telegram / Email / SMS)	v1.5 roadmap	email · WA	email	email · WA · SMS	email · WA

This isn't a knock on Slack, Teams, Front, or HubSpot. Slack and Microsoft Teams are excellent at internal team chat organized by channel. Front is excellent at collaborative email with shared inboxes and team comments. HubSpot is excellent at sales conversations attached to a CRM deal. Each was built for a specific shape of conversation. TradeOS Messages is built for the conversation a trade operator actually has — anchored to an order, a lot, a shipment, an invoice, with the counterparty's relationship (client / supplier / logistics) tagged on the thread, and tasks spawning from any line. Channel routing (WhatsApp / Telegram / Email / SMS) is the next milestone, not the current claim.

Send us one order with a real thread happening on it. We'll show you what that conversation looks like anchored to the entity, with tasks spawning from selected lines.

Send the email thread, the WhatsApp chat, or the Slack DMs you'd normally have about one in-flight order. We'll show you how those messages land on the order record, how internal notes stay invisible to the counterparty, and how decisions in chat become tracked tasks. No demo data. Your conversation.

Book a demo Talk to sales

See pricing →

FAQ

Frequently asked questions

The five questions operators ask first when they evaluate Messages.

How is this different from Slack or Microsoft Teams?

Slack and Teams are channel-based — conversations live in #channels named after projects or teams. TradeOS Messages are entity-based — every conversation lives on the order, shipment, production lot, invoice, claim, sample, or task it's about. Open an order, see its thread. Open Messages, see every thread grouped by what it's about and who you're talking to (client / supplier / logistics / internal). You don't need to remember which channel a conversation lives in — it lives on the record.

What if a counterparty replies by email or WhatsApp today?

Channel routing — Email (Gmail / Outlook / IMAP), WhatsApp Business, Telegram, SMS via Twilio — is on the integration roadmap (target v1.5). Today, TradeOS Messages is in-app: you and your counterparties post into the thread, with attachments and internal notes. When channel routing ships, the inbound email or WhatsApp reply will land in the same thread automatically; until then, paste it in or attach the source file and link the thread to the entity it's about.

Can I create a task from a message? How does that work?

Yes — two ways. (1) Select text inside any message and a floating "Create task" button appears above your selection. Click it; the task modal opens with the selected text prefilled as the title and description, and the source message attached so the task carries the conversation context. (2) Use the composer-level "Create task" button for a proactive task that isn't tied to a specific message ("we just agreed on X, let me capture it"). In both cases, the spawned task appears as a pill under the source message in the thread, and tasks created from the composer show up in a footer summary at the bottom of the timeline.

What's the edit window? Can I delete a message?

Each message is editable for 15 minutes after sending — fix a typo, correct a number, no problem. After that, the message is immutable: it's part of the audit trail. Edits within the window are tracked (the message shows an "edited" indicator), and the original content is preserved server-side. Deletion follows the same model: soft-delete within the window, immutable record after. Spec §11.4 positions Messages as business-record communication, not chat — every message is a record of what was actually said.

How do internal notes work? Can the client see them?

In any thread with a counterparty (client, supplier, or logistics), the composer has an "Internal note" toggle. Flip it on, type your note, post — the message saves with audience scoped to your team only, invisible to the counterparty. The same thread carries both: the outbound conversation with the buyer and the side-channel between you and your ops manager about how to handle their question. No more spinning up a separate Slack thread to coordinate on a customer reply.