Salesforce Winter '27 for Agentforce and Data 360: What Actually Changes
Waves land 4 Sep, 2 Oct and 9 Oct 2026. Why the Data 360 section looks thin, what the Agentforce renames signal, and the deprecations that actually break things.
Segments that survive six months, activation as a promise to another system, and honouring the customer's no.
Designed and created by Salesforce Expert
6 sections · 23 lectures · 9 hands-on labs
It opens with a catalogue that went to the same person three times. This course is about the half of Data 360 that touches real customers: designing an audience that survives contact with the business, living with a segment for six months as the data drifts, and activation — which is a promise made to somebody else's system.
The consent module is the one most implementations skip. Honouring the no is treated here as a design requirement, not a checkbox.
Waves land 4 Sep, 2 Oct and 9 Oct 2026. Why the Data 360 section looks thin, what the Agentforce renames signal, and the deprecations that actually break things.
Four ways to ground an agent in Data 360, when each is right, and why zero-copy federation is the wrong choice for the retrieval path of a live conversation.
Every Agentforce project has this argument in week three. The rule that sorts deterministic steps from generative ones, and why each half needs a different test.