Cloud Call Forwarding: Setup, Routing, and Troubleshooting

Cloud call forwarding routes your inbound calls through a cloud platform that applies routing logic, then delivers the call to a phone number, SIP endpoint, or a browser agent. Unlike device-level forwarding or carrier star-codes on a single line, it centralizes control per number, adds routing rules, and gives you real-time visibility into what happened on every call.

Key takeaways

• Centralized routing per number with priority, weighted, round-robin, simultaneous ring, schedules, and geographic rules.
• Deliver calls to any phone, a SIP endpoint, or a browser agent; add queue, IVR menu, voicemail, and whisper messages.
• Real-time logs, recording, monitoring, and scheduled reports make operations measurable.
• Provision US toll-free/local and select international numbers from a prepaid wallet—no subscription.

What cloud call forwarding is (and how it’s different)

Cloud vs device vs carrier codes vs PBX seats

• Device-level forwarding: You enable forwarding on a handset. It’s per-device, fragile, and easy to forget on/off. No analytics, no shared logic for a team, and it breaks if the device loses service.
• Carrier star-codes: On some lines, codes like *72/*73 toggle forwarding. These vary by carrier, are per-line, and can’t express complex logic (no priority list, no geo rules, no caps). They also don’t produce useful logs or recordings.
• PBX/UCaaS seat forwarding: Great for forwarding calls for internal users and extensions. You get presence and desk-phone features, but off-net routing and campaign/lead distribution are not the primary use case.
• Cloud platform: You buy a business number on the platform and attach routing rules that can send calls to any mix of phones, SIP endpoints, or browser agents. Rules can be priority-based, weighted, round-robin, simultaneous ring, time-of-day, or geographic by caller state. You also get a queue with hold music, IVR menus, voicemail, and whisper messages.

How calls traverse carriers and SIP to your targets

When someone dials your number (toll-free or local), the call lands on the platform via direct SIP trunks across multiple redundant carriers. The platform applies your routing logic, then delivers the call to:

• A public telephone number (PSTN)
• A SIP endpoint (your PBX, SBC, or SIP softphone)
• A browser agent (web-based softphone)

Because routing happens in the cloud, you get real-time logs, call recording, live call monitoring, and scheduled email reports. Device- or carrier-level forwarding generally can’t give you this level of reporting. For a deeper overview of business-focused setups, see our business call forwarding guide.

When to use hosted call routing

Small teams and franchises

Typical triggers:

• You’re running ads in multiple states and want in-state callers to reach licensed teams.
• After-hours routing is required to an answering service or voicemail.
• You need city-by-city schedules, but one shared number in ads.

Example: A roofing company advertising across three states buys one local number per state. Caller-state routing sends each in-state caller to the nearest office. Each office has time-of-day windows by city; after-hours goes to voicemail or an external service. Caps prevent flooding a single office when a storm hits.

Agencies and pay-per-call

Route by priority or weighted split to share leads across buyers. Enforce duplicate-caller rules so recycled traffic doesn’t get billed. Apply per-target call windows and daily/concurrent caps to match buyer availability. Give buyers portal access for recordings and logs. Use scheduled reports for performance visibility.

Call centers and overflow handling

Use simultaneous ring to hit several agents at once. If no one answers, send the call into a queue with hold music. Use an IVR menu to collect a digit (sales vs service) or deflect simple intents to voicemail. Time-of-day rules and per-target windows make after-hours overflow straightforward.

How it compares to device and carrier forwarding

What you gain—and what you don’t need

You don’t need to reconfigure every handset or memorize star-codes. You centralize routing on the number, add rules, and choose any destination type (PSTN, SIP, browser). Here’s how common approaches compare:

Approach	Setup scope	Routing depth	Off-net flexibility	Analytics/recording	Reliability approach	Who it suits
Carrier star-codes on a line	Per line	Single forward only	Limited to one destination	None	Single carrier path	Solo users with simple needs
Device-level forwarding	Per device	Single forward; device-dependent	One destination tied to device/service	None	Depends on device coverage	Individuals, ad hoc
PBX/UCaaS seat forwarding	Per user/extension	Some rules within PBX	Best inside the PBX domain	Some PBX reports	PBX redundancy	Teams centered on internal extensions
Cloud routing platform	Per number	Priority, weighted, round-robin, simultaneous, schedules, geographic	Any phone, SIP endpoint, or browser agent	Real-time logs, recording, monitoring, scheduled reports	Multiple redundant carriers + direct SIP trunks	SMBs, agencies, pay-per-call, call centers, distributed teams

Star-codes like *72/*73 differ by carrier and aren’t programmable the way cloud routing is.

How it works in practice: numbers, routes, and targets

Numbers you can provision

Provision US toll-free and local business numbers, plus numbers in several other countries. Buy instantly from a prepaid wallet—no subscription or contract. Use different numbers for channels, states, or campaigns so you can route and measure precisely. If you rely on toll-free, review deliverability basics in our toll-free call forwarding guide before scaling.

Where calls can be delivered

Deliver calls to:

• Any phone number (PSTN)
• A SIP endpoint you control
• A browser agent (web softphone)

Mix and match within a single flow: for example, try simultaneous ring to two mobiles and one browser agent, with a SIP endpoint as a fallback.

Routing logic you actually use

• Priority lists: Try target A, then B, then C.
• Weighted split: 60/40 between two offices or buyers.
• Round-robin: Distribute evenly across a team.
• Simultaneous ring: Call multiple targets at once for fastest answer.
• Time-of-day windows per target: Different windows by city, buyer, or on-call.
• Geographic/caller-state routing: Route US calls by the state of the caller ID.

Controls and guardrails:

• Daily and concurrent caps per target to protect quality and commitments.
• Call queue with hold music for short waits.
• IVR menus to collect a digit or offer simple choices before routing.
• Voicemail and whisper messages for context.

Measurement and operations:

• Call recording and live call monitoring.
• Real-time call logs and analytics.
• Scheduled email reports for stakeholders.

Setup: a simple call-routing flow in CallFlow

Step-by-step

1. Add wallet funds (prepaid). This unlocks instant number provisioning and usage-based billing.
2. Search and buy a number (toll-free or local).
3. Add 2–3 targets: a mobile number, a SIP endpoint, and a browser agent.
4. Set time windows for each target (business hours vs after-hours).
5. Choose routing: start with simultaneous ring to all three.
6. Enable call recording and a short whisper message (“Lead from Google Ads”).
7. Add a voicemail fallback if no one answers.
8. Save, test from a few caller IDs, and review logs to confirm behavior.

Two common variants

• Variant A (ads across states): Buy one number per state. Use caller-state routing to the local teams. Add daily and concurrent caps per office so one site doesn’t get flooded. After-hours, route to voicemail or an external answering service.
• Variant B (lead-gen buyers): Define buyers as targets. Use priority routing to preferred buyers; if they’re closed or capped, fall back to a weighted split across others. Enforce duplicate-caller rules and buyer-specific windows. Give buyers portal access for recordings and logs. Use scheduled reports to keep everyone aligned.

If answer rates lag, add an IVR menu to pre-qualify (e.g., “Press 1 for sales”) or send callers to a short queue with hold music before voicemail.

Routing recipes that answer more calls

Answer-rate first

• Simultaneous ring to 3–5 agents. If no answer, roll to a short queue with hold music, then to voicemail.
• Round-robin across a team to spread load and avoid agent burnout.
• Weighted routing when some agents close at a higher rate—e.g., 50% to your top closer, 25% to each of two others.
• Avoid cutting off rings too quickly; premature fallbacks create missed connections.

Coverage by hour and location

• Time-of-day windows per target to match on-call schedules. Add a weekend backup to an external service or voicemail.
• Caller-state routing to send in-state callers to licensed teams. If state is unknown or international, fall back to a general queue or voicemail.
• Apply daily caps to keep volume commitments balanced and concurrent caps to preserve call quality during peaks.

Troubleshooting common forwarding issues

Fast checks

• Confirm target numbers and SIP URIs are correct.
• Avoid cutting off rings too quickly; let the initial ring step finish before failover.
• Verify schedules are active and time zones are correct.
• Check daily and concurrent caps; make sure targets aren’t paused.
• Confirm target devices aren’t in Do Not Disturb or out of coverage.

Deeper diagnostics

• SIP response clues: 486 (Busy), 603 (Decline), 607 (Unwanted) explain why a call failed. See our guide on SIP response codes and spam detection for interpretation.
• Spam and blocking: Monitor per-number spam scores, especially on toll-free. If a number trends negative, pause it, rest it, or replace it; update campaigns accordingly. Our primer on toll-free spam scores covers what to watch.
• Network path: Test another destination type (send to SIP instead of PSTN, or vice versa). Platforms automatically try alternate carrier-grade routes when available.
• Voicemail loops and forwarding conflicts: Disable device-level call forwarding on the target if it steals the call before your routing completes.
• Recording/monitoring checks: Use live call monitoring and real-time logs to see whether calls failed on ring-no-answer, buyer caps, or an upstream reject.
• Geo logic pitfalls: If you’re routing by caller state, verify your unknown-state fallback is set; otherwise calls can drop to voicemail more than expected.

Keeping spam and fraud out of your flows

What to enable

• HLR/line-type lookup to understand the number type you’re dialing to or receiving from.
• VoIP-caller blocking and blocklists to shut out obvious bad traffic.
• Rate limits to throttle floods or bot bursts.
• Duplicate-caller rules in pay-per-call to protect buyers from recycled traffic.

Watching your inventory

• Review per-number spam scores and use scheduled email reports to catch drift. If a number trends negative, pause it, rest it, or replace it; update campaigns accordingly.
• Schedule email reports and review real-time analytics for short-call spikes or sudden surges that signal fraud or misrouting.
• Periodically test your top numbers from varied caller IDs and networks to confirm healthy delivery.

Choosing a call-routing platform

Checklist for decision-makers

Capabilities to require:

• Instant number provisioning (US toll-free/local and select international) from a prepaid wallet.
• Rich routing: priority, weighted, round-robin, simultaneous ring, time windows per target, and geographic/caller-state routing.
• IVR menus, voicemail, and a call queue with hold music.
• Call recording, live call monitoring, real-time analytics, and scheduled reports.

Operational needs:

• Sub-accounts and agents with extensions.
• Browser softphone and/or SIP softphone registration.
• Buyer portals if you run pay-per-call or affiliate use cases.

Commercial model:

• Usage-based with a prepaid wallet; no monthly subscription; pay only for what you use.

Reliability posture:

• Multiple redundant carriers and direct SIP trunks, not a single upstream dependency.

If you’re comparing software options, this overview of call forwarding software frames the tradeoffs.

Next steps

Map your current routing on one page and pick a single improvement to ship this week—add simultaneous ring to your top number, or set after-hours routing with a voicemail fallback. Then stand up a test number in CallFlow, build a two-target flow (mobile + browser agent), and confirm answer-rate gains before layering in caller-state routing and caps.

Ready to try it? Create a wallet and provision a number in minutes at register. If you’d like help planning a migration or rebuilding a complex flow, reach our team at contact.