Spending, estimates, holds, releases, and refunds

Before an action that uses tokens begins, LeadsParrot checks account access, workspace access, the configured spending source, and the monthly cap. Bulk or queued work may place a hold for the estimated maximum cost.

Holds reduce both source availability and cap remainder immediately. As results finish, LeadsParrot captures the actual charge and releases unused held tokens. Free actions do not consume tokens. Estimates in the interface are guidance; the backend confirms every final charge.

For waterfall work-email and identify-by-email jobs, LeadsParrot reserves the maximum for every submitted row, then captures only successful results. No-match, duplicate, skipped, failed, timed-out, and unused portions are released. Once external work is submitted, the process cannot be cancelled because its external credit spend may already have occurred.

Campaign email holds

A campaign email uses the current send-cost hold before LeadsParrot asks the sending provider to deliver it. Provider acceptance captures the hold as the final charge. A confirmed send failure releases the hold, so failed campaign emails do not consume tokens. See token costs by action for the live cost.

If the selected token source or workspace monthly cap cannot cover the hold, LeadsParrot leaves the affected lead waiting and retries later. It does not attempt the send or charge the email. Retries settle the reservation associated with that campaign email instead of creating duplicate charges.

If a completed charge is refunded, tokens return to the originating workspace bucket while that bucket remains active. If the workspace is archived or no longer uses its bucket, the refund returns as shared tokens.

A process stopped by a confirmed cap reduction releases unused capacity. Check Activity Log for process status and Tokens → Token activity for the token ledger entries. The initiator also receives a web app notification explaining that the workspace cap stopped the process.