Setting up the sales accelerator

What it does

The sales accelerator is a workspace in Dynamics 365 Sales that gives sellers a single prioritised list of records to work through, with the next action for each one attached. Setting it up means turning the workspace on, telling it which tables belong in the list, and picking which forms sellers land on when they open a work item.

Key facts

Configuration lives under Change area > Sales Insights settings > Sales accelerator > Workspace. There is a Quick setup path that does the minimum: security roles, record types, forms.
Setup asks you to add security roles explicitly. Users without a role you selected here won't see the workspace even if they have the licence.
Lead, Opportunity, Account and Contact are selected by default. You can add more tables, and there is no documented cap on how many.
Custom tables must be user-owned. Organisation-owned tables are not supported and won't appear in the picker.
A custom table also needs Activities, Connections and Sending email enabled under Communication & Collaboration on the table definition. Enabling Sending email creates the email address field if the table doesn't already have one.
There's an Add sample data option intended for sandboxes and trials. It writes real records into the environment — don't run it in production.
With a Sales Enterprise licence the accelerator is included but capped at 1,500 sequence-connected records per month. Sales Premium removes that cap. Sales Professional doesn't include the accelerator at all.
Usage against the Enterprise cap is calculated by the Sales insights sequence daily usage Power Automate flow and the usage panel refreshes roughly every 24 hours, with six months of history retained.
The accelerator doesn't show up in the app designer's component list because it's a URL-based custom control, not an entity form. For a custom app you add a sitemap subarea pointing at /main.aspx?pagetype=control&controlName=MscrmControls.AcceleratedSales.AnchorShellControl.
Disable on the workspace page turns it off and removes the Sales accelerator entry from My Work. Configuration is retained, so it's reversible.

When to use / skip

Turn it on when the client has a genuine high-volume, repeatable outbound motion — inside sales, SDR teams, lead qualification desks — where the day is a queue of touches rather than a handful of large deals. That's the shape the accelerator is built for, and it pays back quickly.

Skip it, or at least defer it, for classic enterprise field sales with long cycles and small account counts. Those sellers live in the opportunity form and a Kanban pipeline view, and a work list of five items is a solution to a problem they don't have. Also skip if the client is on Sales Professional — it isn't there, and no amount of configuration will surface it.

The awkward middle is Sales Enterprise. The accelerator works, but 1,500 sequence-connected records a month across the whole tenant goes faster than clients expect once sequences are applied on lead creation. Model the volume before you promise the feature.

Configuration decisions

Which tables belong in the work list. Every table you add widens the list and dilutes prioritisation; adding Account and Contact by default is rarely the right answer for an SDR team that only works leads.
Whether custom tables are in scope. That decision drags in the user-owned requirement and the Activities/Connections/Sending email flags, which are data-model changes, not app config.
Which form opens for each record type. The Sales Insight form ships with the up next widget already on it; a client's heavily customised main form does not.
Which security roles get the workspace, and whether managers get it too. Managers usually want the sequence reporting rather than a work list of their own.
Whether Sales Enterprise capacity is sufficient, or whether the accelerator is the argument for a Premium upgrade. Decide this before design, not after UAT.
Whether predictive lead and opportunity scoring go in alongside. Scores drive the ordering at the top of the list, and without them the "next best customer" claim is thin.

Gotchas

Enabling Activities on a Dataverse table is a one-way door. You cannot turn it off later. If you add a custom table to the accelerator on a whim, you've permanently changed that table.
Organisation-owned custom tables silently don't appear in the record type picker. There's no error explaining why, and people burn an afternoon on it.
The accelerator is invisible in a custom model-driven app until you hand-add the sitemap URL. Every project with a bespoke sales app hits this.
Adding the sitemap entry does not put the up next widget on any forms. That's a separate job per form, and the two are easy to conflate.
The Enterprise cap doesn't hard-stop the feature on a schedule you can predict from the UI — you get a warning marker and overage shown in red on the usage graph, and the guidance is to upgrade. Don't design a process that assumes a clean cut-off.
Sample data in a sandbox that later gets copied forward is a well-known way to end up explaining fake leads to a steering committee.

Consultant notes

Demo the work list with the client's own data shape, not the sample set. The whole value proposition is "your morning, ordered", and generic sample leads don't land it.
Get the record-type list agreed and signed off early. Changing it later is easy in the UI but the downstream card, filter and sort configuration all keys off it.
Push back on requests to add every custom table. Ask what action a seller takes on that record today; if there isn't one, it doesn't belong in a work list.
Before go-live, check the workspace with a real seller's security role rather than a system administrator. Role-based visibility is the most common "it works for you but not for me" ticket.
If they're on Enterprise, put the usage panel in the admin handover pack and tell someone to look at it monthly.

Worth revisiting if the Enterprise capacity limit changes, or if custom table support stops requiring user ownership.