Account-grounded campaign review
Advisor Guidance for Salesforce Marketing Cloud teams.
How Campaign Builder helps Salesforce Marketing Cloud teams review campaign strategy, retrieve account-scoped context, save useful recommendations, and decide next steps before execution moves to Bruno, Factory, or specialist agents.
What it supports
Concrete workflow support, not generic AI copy.
This use case is grounded in implemented Campaign Builder routes, agents, shared SFMC clients, and documented review boundaries.
Advisor chat searches account-scoped knowledge and can return snippet IDs when retrieved content is used.
Recommendations can include account tone-of-voice settings, subject taxonomy, uploaded context, session history, and prior feedback signals.
Authenticated Advisor context routes can list, create, and delete temporary campaign context for the current account and user.
Teams can save Advisor outputs as account-scoped advices and reload session history when a strategy discussion needs to continue.
When async Advisor jobs are enabled, long-running guidance requests can be queued and polled by job ID for durable status.
Implementation map
What technical evaluators can trace.
Advisor is mounted under `/api/v1/agent/advisor/*` with authenticated account context before chat, snippets, advices, sessions, feedback, context, or jobs are accessed.
`POST /api/v1/agent/advisor/chat` supports grounded chat, optional session history hydration, grounding limits, feedback hints, and async job enqueue when configured.
`GET /api/v1/agent/advisor/snippet/:id` uses readable tenant and workspace filters before returning source previews for grounded recommendations.
`GET /api/v1/agent/advisor/context`, `POST /api/v1/agent/advisor/context`, and `DELETE /api/v1/agent/advisor/context/:id` manage non-expired text context records for the authenticated Advisor user.
`GET /api/v1/agent/advisor/advices`, `GET /session/:sessionId`, `POST /feedback`, and `GET /jobs/:jobId` support saved advice, conversation continuity, feedback capture, and durable job polling.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Advisor provides recommendations and next-step support; it does not approve sends, activate journeys, or run SFMC production writes.
Boundary
Snippet lookup and grounding stay within authenticated account, tenant, workspace, and readable knowledge filters.
Boundary
Uploaded Advisor context is account-scoped and user-scoped support material, not shared global knowledge or SFMC launch approval.
Boundary
Execution moves through Bruno, Factory, Email, Content, Image, or Journey workflows when teams need confirmed SFMC-facing writes.
Boundary
Saved advice and feedback are account-scoped guidance records, not campaign launch approvals or compliance attestations.
FAQ
Evaluation questions for Advisor Guidance.
What makes Advisor different from a generic campaign chatbot?
Advisor uses authenticated account context, readable knowledge filters, retrieved snippets, subject taxonomy, tone settings, uploaded context, session history, and feedback signals before returning recommendations.
Can Advisor make changes in Salesforce Marketing Cloud?
No. Advisor is a guidance layer. SFMC-facing work remains in confirmed specialist workflows such as Bruno, Factory, Email, Content, Image, and Journey draft creation.
Can teams preserve Advisor recommendations?
Yes. Implemented routes support saved advices, session history lookup, snippet preview, feedback capture, and optional async job polling for longer-running guidance.
Next step
Review this workflow against your SFMC setup.
Bring one existing campaign, journey, email, Content Builder process, or Data Extension workflow to the demo so the evaluation can stay concrete.