Two layers of AI control
The backend token allowance governs workspace AI resources. The browser’s daily cap limits how many requests you dispatch without changing token accounting.
- Set a browser cap between 1 and 100 requests per UTC day.
- AI scoring and reply drafts share this cap.
- Device permission, workspace status, and plan entitlement are still checked.
Uncertain outcomes still need reconciliation
A lost response does not establish that the provider did no work. The extension retains the request ID, counts conservatively against the local cap, and checks the existing outcome before an explicit resend decision.
- A definite pre-processing rejection can release the local request slot.
- Malformed AI output does not automatically start another paid request.
- The backend reconciles actual tokens; local request counts are not a token total.
Data limits keep the workflow manageable
Some limits apply to on-device data and others to each cloud batch. Check the scope before exporting, importing, or selecting many records.
- Local Inbox: up to 2,000 leads; backup import: up to 64 MB and 2,000 leads.
- Sync: up to 100 leads in a confirmed batch.
- Categories: up to five for posts and five for comments; background intervals range from 15 to 360 minutes.
