Network inter-flow
Definition
Network inter-flow
Network inter-flow is call routing technology that hands a live call from one contact center site or team to another without making the caller redial. It holds the call leg open across networks so the next agent picks up mid conversation.
The term covers two moves. One is a transfer between agents on the same floor when the first can’t resolve an issue. The other is a transfer between separate sites — say a Manila floor handing an escalation to a Cebu specialist team.
Cloud platforms run inter-flow over Session Initiation Protocol (SIP) signalling. ITU-T Recommendation Q.1912.5 specifies how SIP interworks with ISDN user part signalling, which is what lets a call leg cross carrier boundaries without dropping.
The routing brain is usually an automatic call distributor reading customer relationship management (CRM) records and a live skills database, a pattern documented back to early private branch exchange systems.
Key takeaways
- Inter-flow routes live calls across sites, so callers stay on the line.
- SIP signalling under ITU-T Q.1912.5 keeps the call leg intact across carriers.
- Automatic call distributors pick the destination using skill tags and queue depth.
- Shared CRM records and real-time presence data prevent blind transfers.
- Business Process Outsourcing (BPO) operators use it to lift first-call resolution without new hardware.
How it works
Network inter-flow runs as a rule set on top of the contact center’s routing engine. When a call lands, the platform checks caller identity, queue depth, agent skill tags and time of day, then picks the best landing spot for that call.
The sequence usually looks like this:
- The caller dials a published number and reaches the first site’s interactive voice response menu.
- The menu captures intent: account question, billing, technical support or escalation.
- The routing engine checks live agent availability and queue depth at every linked site.
- If the origin site is full or lacks the right skill, the leg redirects over SIP to the next best site.
- The receiving agent gets a screen pop carrying the caller’s CRM record and prior call history.
- The customer stays on the same call, with no ring-back, no hold-music restart and no audible hop.
The table below shows where inter-flow sits against neighbouring routing techniques.
| Routing type | What it does | Best for |
|---|---|---|
| Network inter-flow | reroutes live calls across sites and teams | multi-site BPOs defending queue times |
| Skills-based routing | sends calls to agents tagged with the right skill | specialist tech, billing and fraud desks |
| Round-robin distribution | spreads calls evenly across available agents | flat single-site teams |
| Priority queueing | pushes VIP or escalated calls up the queue | tiered customer programmes |
| Time-of-day routing | switches the destination as shifts open and close | follow-the-sun desks spanning time zones |
| Overflow to an outsourcer | bursts volume to a contracted partner site | seasonal peaks and disaster cover |
Two foundations sit underneath every inter-flow setup. The first is a shared real-time presence feed, so the routing brain knows who is genuinely free. The second is a unified CRM, so the receiving agent inherits the full call history.
Without those two, inter-flow degrades into blind transfers — callers repeat themselves, which defeats the point of moving the leg at all.
Two engineering details decide whether it holds up in production. Carrier redundancy keeps a second path live so a single site outage does not drop the leg. Codec matching across sites stops audio quality stepping down at the handover.
Cloud platforms sold as contact center as a service ship inter-flow by default, with computer telephony integration linking the routing engine to the CRM in real time.
The more sophisticated setups add cost-aware overflow logic, pushing spillover to lower-cost sites during peak hours to protect margin while holding service level agreement targets.
Examples
Large operators run network inter-flow as a default routing pattern rather than an exception. The three below are customer experience majors that route across dozens of countries, and each one uses inter-flow for a different reason.
TP (formerly Teleperformance) is the world leader in outsourced customer experience management, with over 485,000 people in nearly 100 countries at the end of 2025. It routes overflow from a booked Lisbon site to a quieter Bogotá or Cairo floor.
TP’s 2024 Integrated Report puts the group at more than a billion interactions a year — the scale at which a few seconds of queue time turns into a margin question.
Concentrix, headquartered in the United States and operating in more than 70 countries, uses cross-site routing to push spillover from one regional hub to another when demand spikes. Routing flexibility is how it follows demand across time zones.
TaskUs, NASDAQ-listed and headquartered in New Braunfels, Texas, ran roughly 60,400 staff across 30 locations in 13 countries as of 30 June 2025. It inter-flows trust and safety work by language and time zone rather than by queue depth.
None of this comes free. Each added site multiplies the integration work, which is why plenty of operators book an advisory review of the platform shortlist before they sign anything.
Related terms
Inter-flow sits inside a small cluster of routing and platform terms. The entries below cover the engine that makes the decision, the front door that gathers intent, the delivery model that ships it, and the metric operators watch afterwards.
- Automatic Call Distributor: the routing engine that picks the receiving agent or site.
- Interactive Voice Response: the front-end menu that captures caller intent before routing.
- Skills-Based Routing: rules that match calls to agents by tagged competency.
- First-Call Resolution: the metric inter-flow is most often deployed to lift.
- Contact Center As A Service: the cloud delivery model that ships inter-flow by default.
- Computer Telephony Integration: the layer linking routing decisions to customer records.
FAQ
What is network inter-flow in simple terms?
It is a live transfer between contact center sites or teams that happens without the caller hanging up. The routing platform moves the call leg over the network while the customer keeps talking. Providers often sell it as follow-the-sun or virtual queue routing.
How is inter-flow different from a warm transfer?
A warm transfer is a manual handoff between two named agents, arranged in the moment. Inter-flow is automated and decided by routing rules, often before a human picks up at all. The gap matters at volume, because rules scale and hallway handovers do not.
Does network inter-flow add latency to the call?
Modern SIP platforms add latency in the low tens of milliseconds, below what a caller can hear. The bigger risk is a dropped leg if a site loses connectivity mid-transfer. Redundant carrier paths and a fallback queue are the standard mitigations.
Is inter-flow only useful for big BPOs?
No. Even a two-site operation with a daytime team in Manila and a night team in Cebu benefits, because the routing brain stops one site queueing while the other sits idle. The break-even point is usually the second site — not the tenth.
What metrics improve when inter-flow is switched on?
First-call resolution, average speed of answer and abandonment rate usually move first. The analyst firm Metrigy rates contact center platforms in its MetriRank studies, a useful cross-check on vendor claims. Gains depend on how mature your routing was.
Can inter-flow work across outsourcing vendors?
Yes, if both vendors run interoperable SIP routing and share a customer record or ticketing layer.
Explore more outsourcing terms and provider guidance at Outsource Accelerator.
Independent
