Reward Claim Caps

Cap how many times a reward can be claimed — per related record (conversation or introduction) and per advocate within a rolling window — 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 or introduction 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)
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 Save.

The Claim Limits section has two independent caps. You can set either, both, or neither.

Same-Record Limit

How many times an advocate can claim this for the same related record.

Only appears for activity definitions tied to a subject type (e.g., a reward attached to a specific conversation or introduction). Limits how many times the same conversation or introduction can be rewarded.

Default for new definitions: 1
Range: 1–10
Leave blank for no per-subject 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.

Per-Advocate Rolling Window

Maximum [count] claims per [window].

Limits how many claims a single advocate can make against this activity definition within a rolling window.

Count — number from 1–100. Leave blank for no per-advocate limit.
Window — Day, Week, Month, or Year.

Example: “Maximum 5 claims 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.

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 for that reward is disabled with a short explanation underneath:

Same-record limit hit — “Already requested for this conversation” (or “Already requested for this item”)
Per-advocate limit hit — “Reached your limit of {N} per {window}”

The button reappears once the cap clears — either when an admin rejects a pending claim (same-record) or when an old claim ages out of the rolling window (per-advocate).

Defaults and Backward Compatibility

Existing activity definitions keep their previous behavior — both limit fields default to blank, meaning no cap.
New activity definitions default the Same-Record Limit to 1 (when the definition has a subject type). The per-advocate window defaults to blank.

If you want stricter limits on an existing reward, edit the definition and fill in the fields.

Related: Activity Definitions · Wallets