- Chats and tasks → Chats: what your team asked, attached, and decided.
- Activity: what work ran and what state it reached.
- Notifications: what update, alert, or receipt Marketer sent.
- Awaiting action: what still needs a human decision.
- Product surfaces: what exists now.
Use Recents for a quick return
Home shows a short Recents list in the sidebar alongside current work and workspace sections. Select a recent row when you recognize the conversation and want to continue it. Open Chats and tasks → Chats when the needed thread is older, archived, or not obvious from its shortened title.Reopen a conversation from chat history
Open Chats and tasks → Chats. Each row can show:- The thread title
- An Archived label when the thread is archived
- Who started it, when that information is available
- The time of its most recent activity
Reconstruct the decision
Read the thread in this order:- Find the first turn that defined the deliverable.
- Inspect the campaigns, briefs, creatives, products, or files attached to that turn.
- Identify later messages that changed the scope, dates, authority, or acceptance criteria.
- Open any task proposal and note whether it was dismissed, edited, or approved.
- Open the final task result or output link.
- Confirm the current state in the product surface that owns the result.
Read Notifications as receipts
Open Notifications from Quick actions. The page groups items by notification type and shows a count for each group. A notification row can contain:- A severity indicator
- A title and short body
- The time it was created
- An unread marker
- A link to the source record when the notification has a destination
Manage the feed
- Select Mark visible as read to mark the notifications currently loaded on the page as read.
- Select Load older when more history is available.
- Use unread state to track whether you have seen a receipt—not whether the underlying work is complete.
Follow an update to its source
Use the same sequence for an alert, completion receipt, or approval notice:1
Read the notification type and time
Determine whether the row describes an alert, agent receipt, approval event, or budget-related update. Compare its time with the decision window you care about.
2
Open the linked record
Follow the row when it is clickable. If it is not, search Activity by the relevant name or return to the product surface named in the notification.
3
Inspect the full state
Read the task steps, result, proposal diff, workflow run, or product record. Do not make a decision from the notification body alone.
4
Resolve the next action
Answer a waiting question in chat, decide a proposal in Awaiting action, or open the output in its owning surface.
5
Verify the current object
Confirm the present campaign, creative, brief, workflow, or provider state. A historical receipt remains valid history even after the object changes again.
Choose the correct record
Distinguish similar-looking events
Response ready versus task completed
A direct chat response can be ready while a longer task is still running. Open the task card and use its lifecycle state as the execution record.Task completed versus action applied
A task can complete by producing an analysis, artifact, or proposal. Confirm a live change separately in Awaiting action, the owning product surface, and the provider when appropriate.Notification read versus decision resolved
Marking a notification read changes the feed receipt only. A pending approval remains in Awaiting action until an authorized person decides it.Archived versus deleted
An archived conversation remains visible in Chats and tasks → Chats with an Archived label and can still be reviewed. Treat it as historical context; restate current facts before continuing old work.Complete a handoff from history
When another workspace member needs to continue prior work, send them to one thread or task rather than a collection of screenshots. In the latest message, summarize:- The current objective.
- The source records and dates in scope.
- What Marketer completed.
- What remains waiting or unverified.
- The next decision and its acceptance criteria.
Troubleshooting
A recent conversation is missing
A recent conversation is missing
Confirm the active workspace, then open Chats and tasks → Chats and look for an Archived row. A thread created in another workspace will not appear in the current workspace’s history.
A notification does not explain the outcome
A notification does not explain the outcome
Open its link, or use its title and time to locate the related run in Activity. Read the underlying task or product record before drawing a conclusion.
The notification is read but the approval remains
The notification is read but the approval remains
Read state and decision state are separate. Open Awaiting action and use the approval controls on the pending item.
An old result no longer matches the product
An old result no longer matches the product
Compare the result completion time with current source freshness and later activity. Preserve it as history, then rerun the analysis with an explicit current period when needed.
The feed has too many low-value receipts
The feed has too many low-value receipts
Review workspace notification settings and recurring workflows. Keep the notifications tied to decisions your team will review, and use Activity for broad execution history.
Next step
Inspect task history
Read the run state, steps, outputs, and Activity record behind a receipt.
Resolve pending work
Move from an approval notice to the exact recorded decision.
Rebuild the request context
Continue the thread with the same records, window, and authority boundary.
Monitor recurring work
Use workflow configuration and run history as the execution source of truth.