​
At a Glance

  • Included & unlimited: Real-time, call-triggered workflows (Autopilot Classic, Summaries, AI Signals, Call Recording) are not metered.
  • Metered with credits: High-volume workflows that can reprocess large historical datasets.
  • One credit = one record run. Think “one deal or account processed once.”
  • Credits are pooled across your seats and refresh monthly. No rollover.
  • If you hit zero: We pause high-volume jobs and notify admins. No auto-charges.

​
Why Credits Exist

Credits make costs predictable when you run big, non-call jobs (e.g., backfills or retro analyses). They act as clear guardrails so you can scale without surprise bills and without limiting the day-to-day, call-bound workflows your team relies on.

​
What Uses Credits

These product areas can consume credits because they operate at large scale and/or on historical data:
  • Retropilot: Re-analyzes past calls when a Salesforce event occurs (e.g., an opportunity changes stage).
  • Autopilot Batch: On-demand or scheduled backfill jobs across many CRM records.
  • Executive Briefs: Scheduled rollups digesting insights across a wide set of deals or accounts.
  • Deep Research: Ad-hoc lookups over a large corpus (e.g., enterprise-segment accounts or deals).
Not metered: AI Signals, Summaries, and other workflows triggered by live calls aren’t ever metered or paused.

​
How Credits Are Allocated

  • Account-level pool: All seats share a single monthly pool of credits.
  • Per-seat allocation: Your plan specifies a per-seat amount that rolls into the pool. Example: 150 credits/seat × 10 seats = 1,500 credits/month.
  • Monthly refresh: Credits reset on the first day of your billing month.
  • No rollover: Unused credits expire at the monthly reset.

​
How Credits Are Counted

Simple rule: one credit = one processing run per record (deal or account). Examples:
  • Retropilot: 1 credit per opportunity (or account) analyzed when the trigger fires.
  • Autopilot Batch: A batch that reviews 500 opportunities uses 500 credits.
  • Executive Briefs: A digest that processes 350 opportunities uses 350 credits.
  • Deep Research: Querying 1,000 enterprise-segment deals uses 1,000 credits.
We intentionally abstract technical costs so you can plan usage with a clear, human-readable unit.

​
What Happens at Zero Credits

When your monthly pool is fully consumed:
  1. The next high-volume workflow is auto-paused.
  2. Admins are notified in-app and can adjust/plan next steps.
  3. Workflows resume automatically at the next monthly refresh or when credits are added.
No surprise bills: Momentum’s standard policy is to pause and notify rather than auto-charge.

​
Buying More Credits

  • You can purchase additional credit bundles at any time.
  • Talk to your CSM if you anticipate a spike (e.g., a large backfill) so we can size the bundle appropriately.
  • During onboarding, some plans include generous exploration allowances. Ask your CSM for details.

​
Controls & Best Practices

  • Toggle high-volume workflows (Retropilot, Autopilot Batch, Executive Briefs, Deep Research) on/off to manage spend.
  • Use scheduling windows for batches and briefs to align with your operating cadence.
  • Get a usage report: Your CSM can provide current credit consumption on request.

​
FAQ

Do call-based features use credits? No. Real-time, call-triggered workflows are unlimited and not metered. Can I allocate credits per team or per rep? Credits live in an account-level pool. Use workflow toggles and scheduling to control where usage happens. When do credits refresh? On the first day of your billing month. Unused credits do not roll over. What if a job is paused at zero? Start it again after your monthly refresh or add a credit bundle to resume sooner. How do I plan a large backfill? Estimate records × 1 credit per record, then ask your CSM to size a temporary bundle.

​
See Also

For any questions about credits or your plan, contact your Momentum CSM or reach out to support@momentum.io.