Consumer Packaged Goods

Sales Execution Copilot

Designed for Field sales representative

Prepare the field sales representative for each retail account call with a grounded pre-call plan: what the account bought and stopped buying, which planogram gaps and promotion compliance issues exist, and what the trade terms permit them to offer, all cited to the account record and the trade playbook.

Contract CON-03 · primary aggregate RetailAccountCallPlan · mode loading

Decision brief

Representative call execution and commitment capture: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Field sales representative

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A representative's 9:00 call is a 38-store grocery banner in the southeast territory.

Decision to make

Prepare the field sales representative for each retail account call with a grounded pre-call plan: what the account bought and stopped buying, which planogram gaps and promotion compliance issues exist, and what the trade terms permit them to offer, all cited to the account record and the trade playbook.

Outcome to show

CallOutcome gives Field sales representative the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Account performance analysis
  2. 2Distribution void and compliance detection
  3. 3Trade terms grounding
  4. 4Pre-call plan generation
  5. 5Representative call execution and commitment capture

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Field sales representative verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved RetailAccountCallPlan evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Prepare the field sales representative for each retail account call with a grounded pre-call plan: what the account bought and stopped buying, which planogram gaps and promotion compliance issues exist, and what the trade terms permit them to offer, all cited to the account record and the trade playbook.
Primary aggregate
RetailAccountCallPlan
Primary container
retailAccountCallPlans
Hierarchical key
/tenantId + /accountId
Schema version
1

Sample scenario

A representative's 9:00 call is a 38-store grocery banner in the southeast territory. The copilot finds three authorized SKUs absent from shelf for nine weeks, showing 640 cases of foregone volume, and one promotion where the agreed end-cap was never executed although the deduction was taken. It retrieves the tier-2 trade terms clause permitting a 3 percent volume incentive on reinstated distribution without director approval, and the objection-handling passage for the buyer's usual space argument. The representative opens with the void, secures reinstatement of two SKUs plus a corrective end-cap, records the commitments at the shelf, and the unexecuted-display evidence feeds the deduction dispute.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
retailAccountCallPlans Primary /tenantId + /accountId RetailAccount, AssortmentPosition, OrderHistoryFact, CallPlan, CallOutcome
tradePlaybookLibrary Reference /tenantId + /termsTier TradePlaybookChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
RetailAccount retailAccountCallPlans /tenantId + /accountId account::{accountId} None
AssortmentPosition retailAccountCallPlans /tenantId + /accountId account::{accountId}::assortment::{skuCode} None
OrderHistoryFact retailAccountCallPlans /tenantId + /accountId account::{accountId}::orders::{periodEndUtc}::{skuCode} None
TradePlaybookChunk tradePlaybookLibrary /tenantId + /termsTier tier::{termsTier}::playbook::{playbookDocId}::{chunkOrdinal} chunkVector
CallPlan retailAccountCallPlans /tenantId + /accountId account::{accountId}::callplan::{callPlanId} planVector
CallOutcome retailAccountCallPlans /tenantId + /accountId account::{accountId}::outcome::{callCompletedUtc}::{callPlanId} None

Query patterns