Inbound Routes serve as the entry point for all calls coming into your phone system. An inbound route tells the system where to direct a call based either on the phone number being dialed or the caller ID of the person calling.
Inbound routes can be set up based on the number the call is coming FROM or the number the call is made TO. An inbound route should also be set up for ANY number calling to ANY number being called. This means that any call coming into your organization which doesn't fit one of the FROM patterns or one of the TO patterns, will follow this generic route.
Administrators have access to the inbound routes for your organization using the Account Center. Locate Inbound Routes in the Phone System menu and expand the heading. Here you will see options to both Manage and Create inbound routes.
The Create Inbound Routes page is where you can set up a new inbound route on your account.

To set up a new inbound route, follow these steps:
An exact match means the phone number must match the number entered in the route exactly.
A pattern match lets you create an inbound route that applies to multiple phone numbers following the same pattern, rather than specifying one exact number. This can be useful when you want calls to or from a range of numbers to follow the same route.
When entering the phone number, you MUST include a country code. Do NOT use any dashes or spaces when entering the number.
A FROM Number route looks at the phone number of the person calling you. This is useful when you want calls from a particular person, organization, or group of numbers to follow a specific path.
A TO Number route looks at the phone number the caller is dialing. For example, your company might have separate phone numbers for Sales and Support. Calls to the Sales number can be routed to the Sales team, while calls to the Support number can be routed to the Support team.
If your number hasn't ported yet, it will not show in the drop-down list of numbers. Instead, you will need to select Set Custom and type the number into the field.
An ANY to ANY route is the broadest type of route. It does not require a specific incoming or outgoing phone number to match. This is used as a general catch-all route for calls that don't match a more specific route.
Because you can create multiple inbound routes, more than one route may appear to apply to a call. Intulse uses the information associated with the call and the matching criteria you've configured to determine which route should be used.
In general, a route that identifies a specific number is more precise than a broad, catch-all route. This allows you to create general routing for most calls while also creating specific routes for particular numbers or callers.
An inbound route is the starting point for your call flow. For example, in the call flow shown below, you see three inbound routes. Two have a direct phone number so any caller dialing those specific numbers will follow that route through the system. The third is ANY to ANY so calls coming into the system that do not match the other two numbers will follow that route. Unlike other phone system features, inbound routes are not attached to another feature. They are the starting point.

Some changes related to your phone system's behavior, such as adding or editing inbound routes, are not live immediately. Rather, the changes are "queued" and waiting to be applied. This allows you to make ALL of the necessary changes and verify that all pieces of the call flow are in place and functioning together as expected before making them live. Once you've tested your changes and are confident your system is functioning correctly, select "Apply Changes" on the left-hand menu to make your system live. A confirmation popup will open asking if you're certain you wish to apply your changes.