The Messages page keeps internal team threads and customer conversations in one list.
Start a team thread
Open Messages, choose New conversation, add the team members who should be included, enter a subject, and send the first message. The thread remains available to its participants, so decisions do not disappear into personal texts.
You can also see project-linked conversations from the project’s Messages tab.
Follow unread messages
Each conversation shows its unread count. The main navigation also adds the unread conversations together, giving you one badge when something needs a reply.
Opening a conversation loads the thread and marks its messages read. Customer conversations are labeled in the list so you can tell them apart from team-only threads.
Chat on a customer’s public page
A customer can open the chat panel on a shared bid page and send a message without signing in. Their message creates or continues a conversation tied to that specific bid. Staff replies appear in the same panel, and the customer sees a notification dot when a new reply arrives while the panel is closed.
Conduit also accepts an invoice public link as the context for a customer conversation. The current shared invoice page does not yet display the chat panel, however. Shared completion receipt pages currently show receipt details and company contact information but do not provide customer chat.
That means the customer-facing chat control you can rely on today is the one on the shared bid page. Invoice-linked conversations can appear in Messages when created through the conversation endpoint; receipts should be handled through the email or SMS that delivered them.
For one-way alerts and automated reminders, see Customer Text Messages.