Conversations and Messaging

Overview

Every transaction on ReBattery has a dedicated conversation thread inside the transaction workspace. Both parties use this thread to coordinate terms, share updates, and attach documents. Conversations are the canonical messaging layer for all transaction communication — they are stored independently of transaction state and linked securely to the relevant transaction.

How Conversation Threads Work

When a transaction is created, a conversation thread is automatically linked to it. All messages sent from the transaction workspace are stored in the platform's conversation system. The transaction itself does not own messages directly; it references the conversation.

This design means:

• Messages persist even if transaction terms change
• You can reference the full history when disputes arise
• The same conversation infrastructure powers both purchase and recycling transactions

[!NOTE] If you reload the workspace or switch devices, the thread reconnects through the conversation link.

From Offer to First Transaction Message

If an initial message is included with a purchase offer, recycling enquiry, or agreement change, that message is promoted to become the first message in the transaction conversation once the offer is accepted. This preserves context from the negotiation stage and avoids asking the same questions twice.

For Buy Now transactions, the conversation starts empty and the buyer or supplier can add the first message once the transaction workspace opens.

Read Receipts

Read receipts help you see whether your counterparty has seen a message.

• When you open a transaction workspace or conversation list, the platform marks messages as read for your account
• Unread counts update automatically when you open the conversation list or transaction workspace
• The conversation list shows a preview of the last message and timestamp, updated automatically when new messages arrive

[!NOTE] If you have multiple team members in the same account, read receipts reflect the last read state per account membership, not per individual user.

File Attachments

You can attach files directly in transaction workspace messages. Attachments are stored securely and referenced alongside the message metadata.

• How to upload: Use the attachment option in the transaction messaging tab. Files are uploaded to platform storage and linked to the message record
• Supported types: Documents, images, and PDFs commonly used for compliance and transaction coordination
• Limits: Individual uploads are subject to the platform upload limit of 10 MB per file. Larger files or bulk evidence should be shared through the Documents tab instead

If you need to share signed agreements or certificates, use the Documents tab in the transaction workspace rather than the messaging thread. The Documents tab keeps these materials organised and versioned separately from chat history.

Transaction Messaging vs Support Chat

ReBattery maintains two separate messaging systems:

Support chat uses its own threading model and is handled separately by the ReBattery support team. Support conversations are not visible to your transaction counterparties, and transaction messages are never routed to the support team unless you contact support separately.

Related Topics

• Transaction Lifecycle — how transactions progress through steps and when messaging is most useful