Forwarding Portal — setting up a flow

Create a flow: pick the master + DIDs, add destinations (slaves and/or toll-free), set the routing rules.

Go to Forwarding in the dashboard and click New flow.

Master + inbound DIDs. Choose the server calls arrive on and enter the DIDs your carrier sends there. DIDs can be alphanumeric (letters, digits and _ - . * # +, up to 50 characters) — enter them exactly as your carrier delivers them.
Destinations. Add where calls go — slave servers, toll-free numbers, or a mix:
- + Add slave: pick the server, then set priority (lower is tried first), weight (split within a priority tier), max live (cap on that server's live calls), and where the call lands (an existing in-group — we mint the transfer DID for you — or an existing DID).
- + Add toll-free: enter the toll-free number to forward to, plus priority/weight/max-live. The original caller's number and CNAM pass through; carrier trunks are managed for you. (If this button is greyed out, toll-free termination isn't enabled on your account yet — contact support.)
A flow needs at least one destination; you can run a master that forwards only to toll-free numbers with no slave at all.
Routing rules. Choose how calls spread (round-robin or weighted), stickiness (send returning callers back to the same destination — same day, a rolling window, or never), the fallback if the routing API is briefly unreachable, and an optional repeat-caller rule. Defaults are sensible — skip if unsure.
Review & build. We provision the trunks, whitelist the master, install the on-box router, and start routing (or build paused if you toggle that).

On a flow's page you can pause or disable individual destinations at any time — changes take effect within a minute. Toll-free calls bill at your termination per-minute rate.

Test it first. Use the Test call button on the flow page to place a real call through your routing — it rings your destination but is never billed and never counts in your reports (look for the Test tag). The Live tab shows which destination is next in line; the Call Log shows one row per call (rapid redials collapse together) — expand any row for a step-by-step timeline (received → sent to … → answered → ended) with talk time.