Managing buyer conversations at scale
Conversation ownership, templates, unread state, follow-up limits, images, and team permissions in one inbox.
Keep context beside the conversation
A useful inbox shows whether the thread belongs to a request or accepted order, the game, service, assigned member, current external state, and recent timeline. Internal notes must remain separate from messages sent to the buyer.
Conversation access follows the same game and assignment scopes as the order.
Use a template hierarchy
A workspace default can be overridden by category, game, service, or automation profile. Variables should come from validated request data. A missing variable should block or omit the affected segment rather than sending raw placeholder text.
Images need the same deduplication and checkpoint rules as text messages.
Limit follow-up
A follow-up should confirm that the request remains active, the buyer has not replied, and no previous follow-up was sent. The default policy can be one follow-up, with rate limits and an owner-controlled delay.
Automated AI replies are not necessary for a reliable first release. Owner-written templates and manual replies are easier to control.