Rivet Messages

The conversation stays with the work.

Discuss an invoice on the invoice. Review a change beside the order. Keep every answer, decision, revision, and approval attached to the object it affects.

One model, clear boundaries

Every conversation knows where it belongs.

Internal channels and DMs stay inside your company. Cross-company conversations live under the business relationship. Outside participants get bounded access to a single conversation — never the workspace around it.

Internal

Team channels and direct messages for your organization. Internal stays internal — DMs never cross the company boundary.

operationsaccounts-payableDana Reyes
Connections

Conversations under a formal business relationship. Documents belong here — attached to the connection, its workflows, and its history.

Kestrel Parts Supply (general)spring-order
Named for the counterparty — each side sees the other's name, never a generic room.
GuestsComing

Bounded conversations with outside participants — a driver receiving a gate pass, an inspector sharing a report — scoped to that conversation only.

R. Alvarez · transport
Context, not chat noise

New participants understand without the hundred-message scroll.

Messages carry the document, version, status, and decision they concern. Anyone joining sees what happened and what is waiting — the thread is the briefing.

Email still works with Rivet: replies and documents route back into the relationship, so partners can start from the inbox they already use.

spring-orderKestrel Parts Supply
Jk
Jordan Kim · invited Kestrel Parts Supply
Welcome — the spring order lives here. Invoice and PO are already attached.
DR
Dana Reyes · joined from the invoice task
INV-4417 · v3Approved
Jk
Jordan Kim · Just now
Payment queued for today's run — remittance will attach here.

Give every message a context anchor.

Rivet Messages — The Conversation Stays With the Work