Skip to main content
DoneThat

AI Adoption GuideRetailSell

Associate Next Best Action

ML recommends the next best action for store associates using customer profile, basket context, inventory, service history, and current campaign priorities.

Retail processPlanBuyPriceStockSellFulfillReturnClear

By Don, DoneThat’s AI coach · updated

What associate next-best-action does

Next-best-action (NBA) for store associates is a recommendation layer that sits on the associate’s handheld, POS, or clienteling app. It proposes one primary action, and sometimes a short ranked list of alternatives, for the customer currently in front of them or recently identified. The model uses customer profile signals, the live basket, on-hand inventory, prior service history, and active campaign priorities. The associate remains the decision maker: the system recommends; the person chooses whether to act, adapt, or ignore the prompt.

This page is for floor leads, store ops, and retail tech owners who want associates to get timely, inventory-aware prompts without turning the interaction into a script. Related capabilities on the sell path include AI Shopping Assistant for guided discovery, Personalized Product Recommendations for ranking merchandise, and Conversion Drop-Off Diagnostics when you need to diagnose where sell flows stall.

Inputs the model needs

NBA quality depends on five input families arriving together for the active session:

  • Customer profile: loyalty tier, preferences, size or fit notes, channel history, and consented attributes that are safe to surface on the floor.
  • Basket context: items already scanned or reserved, price points, category mix, and any open holds or appointments tied to this visit.
  • Inventory: store on-hand, nearby store or BOPIS availability, and constraints that make a suggestion unsellable (out of stock, restricted location, damaged unit).
  • Service history: recent returns, alterations, complaints, and successful recovers so the prompt does not repeat a failed pitch or ignore an open issue.
  • Campaign priorities: current promos, attachment goals, clearance windows, and brand or category pushes with clear start and end rules.

When basket, inventory, or profile inputs are missing for the active customer or session, the page and device should return empty output: no default “upsell” card, no generic campaign fill-in, and no stale recommendation from another visit. Empty is safer than a confident wrong prompt. Associates should see a calm “insufficient context” state and continue the conversation without artificial urgency.

How the recommendation loop works on the floor

In a healthy loop, identification or basket start creates a session. Features are assembled server-side or at the edge, the model scores candidate actions (attach an accessory, fetch a size, offer a fitting, invite a loyalty enroll, route to a specialist, schedule pickup), and the UI shows one primary action with optional runners-up and a one-line reason the associate can verify. After the associate accepts, edits, or dismisses, the outcome (acted, declined, superseded) feeds training and campaign reporting.

Typical action types stay concrete and floor-operable:

  1. Merchandise move: suggest a complementary SKU that is in stock in this store, with location or aisle hint when available.
  2. Service move: open a fitting room hold, check alternate size, or book a stylist slot.
  3. Recovery move: acknowledge a recent return or complaint before any new sell attempt.
  4. Campaign move: surface a promo only when eligibility and inventory both clear.
  5. Hand-off: route to beauty, tech, or fitting specialists when the basket or profile signals skill mismatch.

Associates should be able to expand why a prompt appeared (which inputs drove it) without reading a model dump. Transparency builds trust and makes overrides teachable rather than silent.

Human-in-the-loop: recommend, then choose

The model proposes; the associate still owns the customer moment. Design the experience so overrides are first-class, not failure modes. Accept, soft-edit (same intent, different SKU or wording), and dismiss should all be one or two taps. Dismiss reasons help: wrong size, customer not interested, inventory wrong, timing off, privacy concern. Those labels improve the next week’s prompts more than a binary ignore.

Keep the human loop explicit in policy and training:

  • Never auto-send messages or apply discounts without associate confirmation.
  • Never force a script; the prompt is a cue, not a mandatory line.
  • Prefer empty output over a recommendation when required inputs are incomplete.
  • Protect privacy: do not display sensitive profile fields on a shared screen; summarize what the associate needs to act.

Floor coaching then focuses on judgment: when to follow the prompt, when to ask one clarifying question, and when to close the prompt and listen. NBA succeeds when associates feel supported under time pressure, not scored for compliance with every card.

Operating guardrails and empty states

Retail NBA fails loudly when inventory or profile context is stale. Treat freshness as a product requirement: inventory age SLAs, profile consent flags, and campaign date windows should gate scoring. If any required family is absent or expired for this session, suppress recommendations and log the miss for ops (missing profile link, POS basket not synced, inventory feed lag).

Useful empty-state rules:

  • No basket and no identified customer: empty. Do not invent “store bestsellers” as next-best-action for an unknown shopper unless that is a separate, explicitly labeled browse mode.
  • Basket present, inventory unavailable: empty for merchandise actions; optional service-only prompts only if you have explicitly scoped them without stock dependence.
  • Profile unavailable but basket and inventory OK: empty for personalization-heavy actions; you may still allow strictly basket-and-stock attachment prompts if product policy separates “generic attach” from “profile NBA.” Document that split so associates and auditors share one definition.
  • Campaign expired or over-quota: drop campaign actions from the candidate set rather than showing a dead offer.

Measure outcomes that reflect real floor work: attach rate when a prompt was shown and accepted, override rate by reason, empty-state rate by missing input, and time-to-decision on the device. Avoid vanity “prompts served” counts that ignore whether inventory was valid or the associate had enough context to act.

Getting started without overbuilding

Start with one store, one category, and a short action catalog (attach, size check, loyalty invite). Wire profile, basket, and inventory with hard empty-output rules before adding campaign complexity. Pair the pilot with Personalized Product Recommendations so merchandise ranking and associate prompts share the same stock truth, and use Conversion Drop-Off Diagnostics if sell completion drops after you introduce prompts. For digital-assisted journeys that feed the same customer into the store, align with AI Shopping Assistant so online intent and floor NBA do not contradict each other.

Roll out with associate feedback sessions in the first two weeks: which prompts felt useful, which felt pushy, and which empty states were correct versus frustrating. Tune the action catalog and reason copy before expanding banners or categories. Keep human choice visible in every release note: the model recommends the next best action; the associate still decides what happens with the customer.

Is this worth automating for you?

Whether this pays back depends on how much time it takes your team today. Most teams estimate that from memory, and the estimate is usually wrong in one direction or the other.

DoneThat reconstructs where the time actually went, with no timers to forget, so you can measure the baseline before committing to a project and check the gain afterward.

Measure the baseline first