Brand Rooms
Brand Rooms are live in Create with Chat. The brand is the room. Your team talks in it. Cuppa runs from it. Recurring playbooks stay in it.
Strategy used to live in Slack. Drafts lived in Cuppa. Context died in the paste. Brand Rooms keep coordination and the agent in one thread — with brand DNA, keywords, GSC, planner, and knowledge already loaded.
What changed
- Threads on a brand are shared by default. You see who said what.
- Scratch work stays private with the lock (Just me).
- Enter posts a note to the team. No model call.
- Cmd+Enter, Run, or @Cuppa asks the agent.
- One person runs the agent at a time so you do not collide.
- A good prompt can become a scheduled playbook (clock in the input bar). Results append to the same thread.
Talk vs run
| Action | What it does |
|---|---|
| Enter | Team note. Coordination only. No tokens burned. |
| Cmd+Enter or Run | Agent turn. Cuppa executes tools from the thread. |
| @Cuppa | Same as Run — directs the message at the agent. |
| @teammate | Notifies that person (in-app; Slack if connected). |
The agent treats [Name, note] as background and [Name, to Cuppa] as the instruction. Only the latest to Cuppa turn is executed.
Visibility
| Mode | Who sees it |
|---|---|
| Brand room (default) | Anyone on this brand can jump in |
| Just me | Only you. Flip the lock in the input bar. |
Only the thread creator can change visibility on an existing chat. History shows a lock on private threads.
Scheduled playbooks
When a prompt is worth repeating, click the clock in the input bar (after at least one message):
- Name the job (e.g. Weekly content audit)
- Keep or edit the playbook prompt
- Pick cadence: daily, weekly, monthly, or manual
- Save
Cuppa appends the next run to the same thread: a scheduled note, then the agent, then the result. The team can reply in the room after.
Empty-state tiles (Morning Brief, Build Content Cluster, etc.) are starter prompts, not scheduled jobs. The clock is what turns a playbook into a cadence. Next run time shows in the room (jobs fire around 06:00 UTC).
Pause, edit, or run-now from the playbook chip on the thread.
Try this with a teammate
- Open Create with Chat
- Post a note:
We need a cluster around [topic]. - Have a teammate add context (Enter — still a note)
- Hit Run and let Cuppa work from that thread
- If it is a weekly job, hit the clock and save the playbook
Why this is not Slack + ChatGPT
- Brand-scoped tools (GSC, clusters, publishing, Link Engine) already in the room
- Shared threads without a second Slack
- Notes do not cost a model call
- Recurring playbooks write back into the same thread
See Agentic AI for the tool catalog the agent can run from a Brand Room.
Notifications
- @mentions — in-app (and Slack if the workspace has Slack connected)
- Agent finished — other participants can get a completion ping so they do not have to watch the run
FAQ
Can two people run the agent at once?
No. One active agent run per room. Presence shows who is running.
Do notes use my API keys?
No. Enter is a note. Only Run / Cmd+Enter / @Cuppa starts a model turn.
Who can see a Brand Room?
Anyone with access to that brand, unless the creator locked it to Just me.
Is this on Solo?
Shared rooms need teammates (Studio+ seats). Solo still gets Chat and can lock threads to Just me. Agentic tool use follows your plan and the Agentic AI table.
Related
- Agentic AI — Tools, permissions, agentic mode
- Slack Integration — Mentions and alerts
- Brand Permission — Who can access a brand
- Content Planner — Where scheduled content can land