On 5 November, World Tour Paris replays Dreamforce 2026. Sort each announcement into available, pilot or only dated before a programme milestone depends on it.
Written for
CRM programme leads at mid-sized companies starting or restarting Salesforce, and their implementation partners
On 5 November 2026, AIforce World Tour Paris replays Dreamforce 2026 at the Palais des Congrès. The official page says the Essentials edition is cancelled. The main day is still listed.
A show-floor demo does not tell you what your org can switch on. Before you go, put each announcement in one box: available in your edition and region, in beta or pilot, or only dated.
Put no critical milestone on an announced GA, such as Hunter or Koa, without written confirmation from Salesforce for your org.
Text
A demo at World Tour Paris will not tell you what your org can switch on. The show, on 5 November, replays Dreamforce 2026 in a single day. The risk is coming home with a programme milestone that rests on an announcement still in pilot, or on one that only has a date. Before you go, put every announcement that affects you into one of three boxes: available in your edition and your region, in beta or pilot, or only dated. For this sort, only Salesforce’s written documents count.
What is Salesforce announcing for 5 November in Paris?
AIforce World Tour Paris 2026 takes place on Thursday 5 November, from 9 am to 6 pm, at the Palais des Congrès de Paris. Salesforce bills it as “le meilleur de Dreamforce 2026” (the best of Dreamforce 2026). The agenda covers AIforce, the new agentic features, Data 360 and Slack, with demos, customer stories and roadmap.
The same page carries a banner saying the World Tour Essentials Paris 2026 edition is cancelled because of a national day of social mobilisation on 5 November. The main day is still listed on that date. If you are travelling, reread the official page before you book your train, then again the day before. That page is the reference for whether the event goes ahead.
The published programme fits in a few slots: the keynote from 10 am to 11 am, then sessions and demos until 6 pm. Nothing on it counts as a general availability (GA) date for your edition or your region.
Available, in pilot or only dated: how do you sort?
A demo on stage proves that a product runs at Salesforce, not that it runs in your edition, in your region or on a date you can plan around.
Two announcements weigh on year-end plans. Hunter, the outbound sales agent, is in pilot, and Salesforce announces its GA for November 2026. Koa, the CRM reasoning model, is open to select pilot customers, with GA expected in Winter 2026 in US regions, followed by an open beta. For a French org, put no milestone on either one until Salesforce has confirmed in writing that it is available for that org. The note Dreamforce 2026: what is available, what is announced sorts all the September announcements.
A spoken announcement at the show moves nothing between boxes. If Salesforce documents a GA afterwards, one line in your plan records it.
Which three questions should you ask at the stand?
Three questions are enough to put a demo in the right box. Write down the answers, and ask for them in writing.
Which SKU, which edition? Is the feature you saw included in your current edition, in a paid add-on or in a separate licence?
Which region, which model? Is it available in the Hyperforce region that hosts your org, and which AI model sits behind it? A GA announced for US regions says nothing about an org hosted in Europe.
Which written status? Beta, pilot or GA: which document says so, and what written date does it give for the move to GA?
As long as one of the three has no written answer, the feature stays in the “announced” box.
What does this change for a company, a training provider or an integrator?
At a company, the programme lead or the CRM sponsor protects the plan first: no critical milestone on an announced GA. If a milestone depends on one anyway, it needs a fallback and a named owner. The decision rules for that choice are in the note Salesforce governance: decision rights and release gates.
For a training provider, a feature in pilot does not justify a course module. The next day, trainees should find in their own org what they practised. A feature that only has a date can go in a “coming next” box, with no hands-on exercise.
For an integrator, the exposure sits in the proposal. A bid that prices a feature still in pilot must say so plainly and plan for GA slipping by a few months.
What should you do before 5 November?
Table 1 Checklist: seven checks for the programme lead, before the show and then in writing after it.
Governance fails on unclear ownership before it fails on code: set decision rights at three levels, tier changes by blast radius, and gate every release.
A CoE that only approves gets routed around. Split platform, delivery and demand work, keep the review scope narrow, and fund it with assets teams reuse.