If a client wants to have the same IVR service for both his numbers, is it possible? If so, how do we achieve this?

If a client wants to have the same IVR service for both his numbers, is it possible? If so, how do we achieve this?

⚡Quick answer:

Yes. Map each number to the same call flow/IVR entry point so inbound calls to any of those numbers play the same greeting and menu and follow the same routing rules.


What it means

Multiple inbound numbers (DIDs) are attached to one call flow. The IVR greeting, options, ring strategy, timeouts, and fallbacks are shared. Any change you publish in that flow affects all mapped numbers.


Prerequisites

  • You can access Numbers/Call Routing and Calls → Design Callflow.
  • The target IVR/call flow already exists (or you will create it first).
  • You have permission to edit number mapping and call flows.

Setup (step‑by‑step)

  1. Identify the primary call flow/IVR you want to reuse.
  2. Open Numbers/Call Routing in your admin panel.
  3. For Number A, set the destination to the same IVR entry (or call flow) you identified.
  4. Repeat for Number B (and any additional numbers).
  5. Open Calls → Design Callflow and review the greeting, menus, fallbacks, and business hours.
  6. Publish changes (if any), then test both numbers.

Alternative approaches

  • Per‑number greeting, shared flow: Keep a single flow but override the welcome audio per number (if your account supports per‑number audio) while keeping the same menu/routing.
  • Forwarding/alias: If external carriers are used, forward both numbers to a single service number that lands on the shared IVR. (Ensure the original caller ID is preserved.)
  • Separate flows with shared sub‑menus: If each number needs a distinct greeting or hours, create two top‑level flows that rejoin the same sub‑menu tree for common logic.

Things to note

  • One flow, many numbers: All mapped numbers will use the same rules; edits affect all.
  • Branding: If numbers represent different brands, use neutral wording or per‑number audio overrides.
  • Business hours: If hours differ by number, consider distinct top flows with a shared sub‑menu beneath.
  • Reporting: You can filter call logs and reports by dialed number to separate performance.

Verify and test

  1. Place a test call to Number A and Number B.
  2. Confirm the same greeting and menu play on both.
  3. Press a few options; ensure routing and fallbacks are identical.
  4. Check Call Logs to confirm both calls entered the same flow.

Success criteria: Both numbers follow the same path (e.g., IVR → Sales → Queue → Agent), with no unintended differences.


Troubleshooting

  • Different greeting plays on one number: Check for a per‑number audio override or an old mapping. Republish if needed.
  • Only one number reaches the IVR: Verify carrier forwarding, number mapping, and that the flow is active/published.
  • Metrics look merged: Use filters by dialed number when reporting per‑number performance.
  • Need partial differences: Split the top level (greeting/hours) and route both into a shared sub‑menu for common steps.

If you need help setting this up, please contact support.