AI plan design assistant

Bitta Commission includes three governed assistants: the Commission Plan Design Assistant, which drafts a plan component from a plain-language description, Explain this earning on the earning card, and Ask about this dispute on the dispute card. Every answer is a labeled draft for a person to review. The assistants cannot create, change, approve, post or pay anything, and every call is audited.

AI setup chooses the provider and switches each capability on.

Before you start

• All three assistants are part of the AI plan drafting module. Switch it on in Commission Feature Management. When it is off, Explain this earning and Ask about this dispute are hidden, Generate Draft is unavailable, and every AI call is refused with BAA-FEATURE-OFF, whatever Commission AI Setup and the consents say. See Turn features on as you grow.
• Only a user with the Bitta Commission Setup Administrator permission set can prepare, accept, renew and withdraw consents.
• Using the plan design assistant requires the Setup Administrator permission set or a Finance (all participants) scope. Explanations and dispute answers require scope to the participant concerned.

Set up the assistants

1. Open Commission AI Setup.
2. In Provider, review the settings:

Field	What it does
Provider	The provider implementation. Deterministic Template needs no external service.
Processing Region Code, Data Region Code	Recorded on consents. Calls stop if the configured data region differs from the consented one.
Model Family	Recorded on consents. Calls stop if it differs from the consented one. Blank means the provider code.
Consent Review Months	How many months after acceptance a consent must be reviewed. Zero means 12.
External Endpoint Configured, Data Movement Acknowledged	Required only for a provider that calls an external service.
Max Prompt Length	The maximum length of a prompt after redaction.

1. In Capabilities, switch on what you want: Explanations Enabled, Design Assistant Enabled and Inquiry Enabled.
2. Choose Prepare Consent Requests. The app creates a pending consent for each capability that has none.
3. Choose Consents to open Commission AI Consents. Review each consent and choose Accept Consent.

Each capability needs the module switched on, its switch in Commission AI Setup and an Active consent: EXPLAIN-EARNING, DESIGN-ASSISTANT or DISPUTE-INQUIRY. Otherwise the action is refused with BAA-FEATURE-OFF, BAA-AI-DISABLED or BAA-AI-CONSENT.

Consents

A consent is recorded per company and per capability. It fixes what the capability may send and how its output is handled:

Field	What it records
Status	Only Active permits calls. Other states include Administrator Approval Pending, Withdrawn, Expired, Suspended and Rejected.
Provider Resource Mode Code, Model Family, Processing Region Code, Data Region Code	What the consent was granted for.
Allowed Data Categories	For explanations and design: plan, component and period codes, amounts, rates, precision, dates and eligibility trigger. For dispute inquiry: dispute status, category, priority, scope and resolution codes, dates, statement status, period codes, component and measure labels, amounts and rates.
Prohibited Data Categories	Participant names, customer and participant identifiers, document and dispute numbers, salesperson codes, free-text comments and attachments. These are redacted or never included.
Human Review Required	Always selected: output is a draft for review.
Review At, Review Overdue	When the consent must be reviewed.
Policy Hash	The hash of the field allowlist consented to.

• Renew Consent creates a pending successor for the current provider, model family and data region. Accepting it expires the earlier version, so only one consent is Active.
• Withdraw Consent stops calls for the capability immediately.
• If you change the provider, model family or data region, calls stop with BAA-AI-CONSENT-PROVIDER, BAA-AI-CONSENT-MODEL or BAA-AI-CONSENT-REGION until you renew the consent.

Draft a plan component

1. Open Commission Plan Design Assistant.
2. In Plain-language description, describe the behavior, for example "pay 3% up to 50000 and 5% above".
3. Choose Generate Draft.
4. Read Draft (AI-generated, review required). It proposes a model, rate table rows with band bounds and rates, the validation to apply, and suggested boundary tests.

Nothing is created. A plan designer enters the component and rate table in the plan editor, validates the version, and routes it through approval and publication as usual. See Plans, versions, and assignments.

Explain an earning

1. Open Commission Earnings and open an earning.
2. In the Explain This Earning part, check Status. It tells you whether explanations are enabled and consented.
3. Choose Explain this earning. Draft Explanation shows a plain-language account: which model, plan version, component and period were used, how the credited base and cumulative entitlement moved, the rounding, and the eligibility trigger.

The draft is kept only for your session. For the authoritative record, use the calculation trace. Sales reps read the trace of their own earnings with Explain on My Earnings, which is not an AI feature. See Explain any earning.

Ask about a dispute

On the Commission Dispute card, choose Ask about this dispute and pick one of three questions: where the dispute stands, what amounts are under review, or what happens next. The answer is shown in AI Draft, and you can add it to the dispute as a comment. The dispute itself is not changed. Setup administrators can choose Prepare inquiry consent on the dispute card to create the consent. See Disputes and holds.

What happens on every call

1. The app checks the AI plan drafting module, the capability switch, the Active consent, and that the consent covers the configured provider, model family and data region.
2. It builds the prompt only from the allowlisted fields of the capability.
3. It redacts participant names and identifiers and email addresses, and refuses a prompt longer than Max Prompt Length (BAA-AI-PROMPT).
4. It calls the provider and labels the result: "DRAFT, AI-generated. Review before use. This text cannot change, approve, post or pay anything."
5. It appends a row to Commission AI Call Audit.

The call audit is append-only. Each row shows Called At, Capability Code, Provider Code, Outcome Code, External Service Used, Target Reference, the user, the Consent ID, Redaction Count, prompt and response lengths, and hashes of the allowlist, prompt and response. The prompt and response text are not stored in the audit.

Related pages

• Explain any earning
• Plans, versions, and assignments
• Audit and security
• Known limitations