How can I change High-level settings for all outgoing calls?

How can I change High-level settings for all outgoing calls?

Change global settings for all outgoing calls (DID Fallback & Shared Route)

Short answer: Use Outgoing → Global Settings to turn DID Fallback and Shared Route on/off for every outgoing call or campaign. Test a call after saving to confirm the behavior.

What these settings do {#what}

Setting

What it does

When to use

Notes

DID Fallback

If the campaign’s primary DID can’t place calls (e.g., temporary carrier issue), the system automatically tries another your-account DID from the allowed pool.

You own multiple DIDs and want automatic resilience.

Caller ID may change to the fallback DID. Review compliance/branding.

Shared Route

If your DID is unavailable, calls route via MyOperator shared DIDs to keep connectivity up.

You have limited DIDs or frequent peaks.

Recipient will see a shared number as CLI; ensure your team can handle return calls appropriately.

Prerequisites {#prereqs}

  • Role with permission to edit Outgoing/Global Settings.
  • At least one additional DID on your account to use DID Fallback (or enable Shared Route).
  • Caller ID/CLI policy that allows presenting fallback/shared numbers in your region.
  • (Optional) A small test list/number to validate changes.

Change global outgoing settings (UI steps) {#steps}

  1. Sign in to MyOperator Dashboard.
  2. Go to Call → Outgoing.
  3. Click Global Settings (top right).
  4. Click Edit next to Outbound Settings.
  5. Toggle DID Fallback and/or Shared Route On/Off.
  6. Click Save.
  7. Place a test call to confirm the behavior (see below).

Expected results & how to verify {#verify}

  • Logs: The test call appears in Call Logs → Outbound with a Caller ID matching the DID used (primary, fallback, or shared).
  • Reasoning: Detail/metadata may show routing reason (e.g., “primary unavailable → fallback DID”).
  • Recording: If recording is enabled for outgoing, the file is attached as usual.

Quick check (what to look for)

  • Primary healthy → Caller ID = primary DID.
  • Primary fails once → Caller ID = another DID you own (fallback).
  • All your DIDs unavailable & Shared Route ON → Caller ID = shared number.

Examples: when each setting helps {#examples}

  • DID Fallback: You run a renewal campaign from +91 11…. Carrier congestion hits the trunk; calls retry via +91 22… (your backup DID) and continue.
  • Shared Route: Holiday spike saturates all your DIDs. With Shared Route ON, calls proceed using a shared pool so the campaign doesn’t stall.

Edge cases & limitations {#edges}

  • Precedence: Per-campaign settings (if supported in your plan) can override global toggles.
  • Branding/CLI: Fallback/shared numbers change what recipients see. Update SMS/email templates and callback handling.
  • Compliance: Some regions require approved caller IDs; presenting an unapproved CLI can cause rejections.
  • Inventory: DID Fallback needs at least one additional active DID.
  • Reporting: Calls completed via shared route may group under a shared CLI in analytics; filter by Direction: Outbound and Caller ID.
  • Cost: Different DIDs/routes can have different rates. Review billing if usage changes.

Troubleshooting {#troubleshoot}

  • Toggles not visible → You may lack permissions or the feature isn’t on your plan. Ask an admin to grant access.
  • Changes not taking effect → Refresh, confirm you clicked Save, and re-open a fresh browser tab. Check if a campaign-level override is in place.
  • Calls still failing on primary → Ensure at least one active fallback DID exists or turn Shared Route ON.
  • Unexpected caller ID → Verify which route was used (primary/fallback/shared) in Call Logs; adjust settings accordingly.
  • Recordings missing → Confirm outgoing recording is enabled and storage limits aren’t hit