Reward Claim Caps
Cap how many times a reward can be claimed — per conversation, and per advocate within a rolling window or ever — to protect your reward budget from accidental or deliberate over-claiming.
When to Use Caps
Caps are configured per activity definition and are most useful when:
- A reward is tied to a specific conversation and shouldn’t be claimable more than once for the same one (per-subject cap)
- An advocate could realistically generate many claims in a short window and you want a sanity ceiling (per-advocate rolling-window cap)
- A reward should only ever be earned once, like a welcome bonus (per-advocate lifetime cap)
- You’re standing up a new reward type and want a safety net while you watch how advocates use it
Caps are entirely optional. Leave the fields blank and the reward stays unlimited.
Configuring Caps
Caps live on the activity definition itself:
- Navigate to Settings > Wallet Configurations.
- Click the wallet configuration that contains the reward you want to cap.
- Click Manage Activity Definitions.
- Click the activity definition you want to cap.
- Scroll to the Claim Limits section.
- Set the fields you want (described below).
- Click Update.
The Claim Limits section has two independent caps. You can set either, both, or neither. Under them, a sentence spells out what your settings add up to, for example “Each advocate can earn this at most once per conversation and at most 10 times a month.”
Per Conversation
Each advocate can earn this [once] per conversation
Only appears when Related To is set, and is named after what you picked. Today that’s Conversation. It limits how many times one conversation can be rewarded. Choose once for once per conversation.
- Default for new definitions: once
- Choices: once, twice, 3–10 times, or any number of times for no limit
Use this to prevent the same piece of work from being rewarded twice — for example, an advocate trying to claim the same “Hosted a test ride” reward twice against the same conversation.
Over Time
Each advocate can earn this at most [count] times per [period]
Limits how many times one advocate can earn this reward, across all their conversations.
- Count — number from 1–100. Leave blank for no limit over time.
- Period — Day, Week, Month, or Year for a rolling window, or Lifetime to count every claim ever.
Example: “at most 5 times per Week” means an advocate can claim this reward up to 5 times in any rolling 7-day window. The 6th attempt is blocked until one of the earlier claims falls outside the window. “At most 1 time per Lifetime” means each advocate can earn it once, ever, even on a reward related to conversations. For once per conversation, use Per Conversation above.
Both pending and approved claims count toward the limits. A claim that gets rejected by an admin frees up its slot.
What Advocates See When a Cap is Hit
When an advocate would exceed a cap, the Request button on their Rewards page, or the Request Reward option in a conversation’s actions menu, is disabled with a short explanation:
- Per Conversation limit hit — “Already requested for this conversation”
- Over Time limit hit — “Reached your limit of {N} per {period}”, or “Reached your limit of {N} ever” for a lifetime limit
The button reappears once the cap clears — either when an admin rejects a pending claim or when an old claim ages out of the rolling window.
Automatic Claims
Caps also apply to rewards Stoked claims on its own: a speedy reply bonus, a test ride or meeting that happened, or a Shopify order. If a cap has been reached, no claim is created.
Defaults and Backward Compatibility
- Existing activity definitions keep their previous behavior — both limit fields default to blank, meaning no cap.
- New activity definitions default Per Conversation to once (when the definition is related to a conversation). Over Time defaults to blank.
If you want stricter limits on an existing reward, edit the definition and fill in the fields.
Related: Activity Definitions · Speedy Reply Bonus · Wallets