Recognize a value moment
A product or account signal indicates that an add-on matches what the customer is trying to accomplish.
← Action Library
04 Reference workflow · Expand
Contextual Add-On Offer
Product usage and account context trigger an eligible add-on offer that the customer can review and accept at the moment of need.
Initiated byProduct surface or expansion agent
Intended outcome
An eligible offer appears with its effective date, co-term behavior, and prorated first charge; the configured billing and product integrations complete activation after acceptance.
Product analyticsCatalogBillingEntitlementsCRM
Transaction path
From intent to completed outcome.
A customer reaches a usage pattern or workflow where an additional capability would provide clear value.
Confirm commercial eligibility
The agent checks plan compatibility, existing entitlements, pricing, and offer rules.
Present the add-on in context
The recommendation explains the outcome, price, and account impact where the need appears.
Execute on acceptance
The accepted add-on moves through the configured billing integration and the product consumes the resulting subscription event.
Commerce contract
One action. Explicit context and control.
Context required
- Feature and usage signals
- Current plan and entitlements
- Eligible add-ons and compatibility
- Account-specific pricing and exclusions
Guardrails applied
- Explainable recommendation trigger
- Frequency and suppression controls
- Offer and discount eligibility
- Customer confirmation before charge
REFERENCE REQUEST
POST /api/v1/preview/add-on
{
"subscriptionId": "sub_2048",
"addOnProductId": "prod_analytics"
}PeakCommerce result
200 OK
{
"subscriptionId": "sub_2048",
"effectiveDate": "2026-08-30T21:00:00Z",
"financialImpact": {
"chargeCents": 40000,
"currency": "USD"
},
"policyEvaluation": { "allowed": true }
}Availability and downstream effects depend on the billing and product integrations configured for the tenant.
Take the next step
Map this action to your commerce stack.
Start with this workflow already selected, then identify the billing, customer, and product systems involved in executing it.