Custom Dispositions for Voice Calls in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Custom Dispositions let an agent or the Power Dialer tag each call with one outcome (Follow Up, Requested Appointment, Not Interested). The disposition can fire workflows, fuel reporting, and works on web and mobile dialers.

Custom Dispositions turn the question "what happened on that call?" into structured data. After every voice call, the agent (or the Power Dialer) picks one outcome. That selection saves to the call record, can fire workflows, and shows up in Call Reporting.

Why use Custom Dispositions

  • Faster wrap-up: agents tag the outcome in one click and move on.
  • Cleaner automation: workflows fire based on the disposition, like sending an SMS or re-queuing in the Power Dialer.
  • Better reporting: standardized outcomes become filters and columns in Call Reporting.
  • Migration-friendly: replaces legacy Call Status with no data loss. Update existing Call Details triggers to use the new filter.

Set up your dispositions

Sparkforge ships preset dispositions on every account. Sub-account admins can edit, reorder, or replace them. Limits and rules:

  • Up to 10 dispositions per sub-account.
  • Only sub-account admins can create, edit, or delete dispositions.
  • Existing workflows keep working when a disposition is renamed.
  1. Go to Sub-account Settings > Phone System > Voice > Call Dispositions.
  2. Edit the existing dispositions or click to add a new one.
  3. Use action-oriented labels that map to your pipeline (for example, Requested Quote or Left Voicemail).

Use dispositions in workflows

  1. Under Automations, add a Call Details trigger.
  2. Select the Custom Disposition filter.
  3. Choose one or more dispositions to drive follow-up actions.

Combine dispositions with other Call Details filters (direction, duration, tags) to:

  • Send personalized SMS or email sequences
  • Re-queue leads in the Power Dialer
  • Apply or remove tags
  • Create tasks or opportunities
  • Move contacts between pipelines or campaigns

How agents log a disposition

When a call ends in the web dialer, the agent sees up to 10 dispositions. They pick one to log the outcome. Logged dispositions are stored on the call record and surface in Reporting > Call Reporting as a column and as a filter.

Custom Dispositions on mobile

Custom Dispositions are fully supported on iOS and Android.

  • Call End Screen support: pick a disposition right when the call ends or from the post-call view.
  • Single disposition per call: one definitive outcome per call to keep reporting clean.
  • Workflow ready: the same Custom Disposition filter drives mobile dispositions into automations.

Mobile-specific notes

Dispositions only appear when the selected sub-account in the mobile app matches the call's location. Cross-sub-account dispositions are not supported, so use the Switch option to change sub-account if needed.

Supported call types

  • Supported: calls made or received through the web or mobile app on Sparkforge Phone or Twilio sub-accounts.
  • Not supported: calls answered on a personal number or desk phone outside the dialer.

Frequently Asked Questions

How many dispositions can I have?
Up to 10 per sub-account. Only sub-account admins can create, edit, delete, or reorder them.
Will renaming a disposition break my existing workflows?
No. Workflows keep working when a disposition is renamed. The underlying ID stays the same, so any automation tied to it continues firing.
Do dispositions work for calls answered on a desk phone or personal number?
No. Dispositions only apply to calls handled through the Sparkforge web dialer or mobile app on Sparkforge Phone or Twilio sub-accounts.
Can I trigger automations from a specific disposition?
Yes. Use the Call Details trigger with the Custom Disposition filter. You can combine it with direction, duration, or tag filters for more precise targeting.
Do mobile dispositions feed the same workflows?
Yes. Web and mobile dispositions both use the Custom Disposition filter, so a single workflow can act on either source.

Was this article helpful?