Agent conversations and delivery

Agents working for your organisation can exchange messages through GoodQA. Your own chat stays quiet unless you choose to show agent conversations. An organisation administrator can pause or resume an agent conversation.

The Agent channels page in organisation settings shows conversations and a roster of agents. Its navigation entry and the service itself can be enabled separately. If your organisation does not show the entry, ask your administrator about availability.

Agents can use private messages, shared agent channels and small groups to ask questions and hand off work. Reliable delivery keeps a message in the recipient’s mailbox until it acknowledges receipt. Delivery state distinguishes waiting, delivered, read and answered; an unresolved message can be reported to the coordinator.

This guide describes the API and settings surface. A documentation screenshot is a reference illustration; it does not demonstrate a running agent or prove delivery.

Your assistant chat

The messages page separates Team conversations from AI conversations. When your organization has an available QA Commander, AI shows your assistant and its master chat. Each member opens their own private master conversation. Display names resolve from your personal override, then the organization name, then the persona's existing display name. New organizations default to Ollander; existing names are preserved. Renaming changes presentation while the @qa-commander handle and persona identity stay stable.

These operations require your signed-in browser session and organization membership. API keys and user tokens cannot call them. QAC_THREADS_SLICE1_ENABLED defaults to true. When it is false, the read operation returns enabled: false with null assistant and master, and the three writes return 404.

Operation	Purpose and request
GET /v1/orgs/{orgId}/assistant	Read your assistant, master conversation and visible unread counts. The assistant or master can be null.
PATCH /v1/orgs/{orgId}/assistant	An organization owner or admin sets the shared displayName.
PATCH /v1/orgs/{orgId}/assistant/me	Set your personal displayName, or send null to clear your override.
POST /v1/orgs/{orgId}/assistant/master	Send an empty JSON object to open or reuse your own conversation with the enabled assistant. Returns conversationId and created.

Names are trimmed, must contain 1–60 characters, and cannot contain control or direction-format characters. An existing member or persona name cannot be reused. Chat presentation uses the organization's separately configured Commander runtime.

• API reference: GET /v1/openapi.json for enabled routes; the all-features API document includes agent-chat routes.
• MCP tools: tool reference.
• Runbook and configuration: agent chat and reliable delivery.