CallRail Number Porting & Call Tracking Setup
Overview
CallRail is used to track inbound calls by source, route calls to the right team members, and attribute phone leads to specific marketing channels or geographies. This article covers the process for porting an existing number into CallRail, configuring call routing, and understanding the difference between tracking numbers and pool numbers.
Observed in practice with [1], who were porting an 800 number away from a third-party answering service and into their CallRail account.
Porting a Number into CallRail
What You Need
To port an existing number (e.g., an 800 number) into CallRail, you typically need:
- Two completed porting forms (provided by CallRail)
- A copy of the phone bill showing the number to be ported
The porting process moves the number out of its current carrier or service and into CallRail's system, at which point it becomes a managed tracking number.
What Happens After Porting
Once ported, the number behaves like any other CallRail number:
- It appears in the CallRail dashboard under Tracking Numbers (not as a pool number)
- You configure call forwarding — where the call actually rings
- Routing can be set up as a cascade: e.g., ring Wade first → if no answer, roll to Mike → if no answer, roll to a third contact
Note: A ported number is a tracking number, not a dynamic pool number. It will have a fixed number displayed to callers, but all activity is logged in CallRail.
Call Routing Configuration
CallRail allows flexible routing rules for each tracking number:
| Option | Description |
|---|---|
| Single destination | Forwards directly to one phone number |
| Sequential (cascade) | Rings person A, then B, then C if no answer |
| Simultaneous ring | Rings multiple numbers at once |
| Time-based routing | Different routing rules by time of day or day of week |
For BluePoint, the recommended initial setup was cascade routing: Wade's cell → Mike's cell.
Tracking Numbers vs. Pool Numbers
| Type | Use Case | How It Works |
|---|---|---|
| Tracking Number | Specific campaigns, ported numbers, offline ads | One fixed number tied to one source |
| Dynamic Number Pool | Website visitors (organic, paid, referral) | A pool of numbers swapped in dynamically based on session source |
Pool numbers are used for website-level attribution (e.g., distinguishing a Google Ads visitor from an organic visitor). Ported numbers are best used for specific, named sources where you want a consistent number displayed.
Geographic & Source Attribution
CallRail logs each call with metadata that can be used for attribution and analysis:
- Source (e.g., Google Business, Eastern Office Website, paid ad)
- Call status (answered, abandoned, missed)
- Recording (if enabled)
- Goal tracking (e.g., calls over 60 seconds counted as a conversion)
In the BluePoint setup, separate tracking numbers were assigned to the Google Business profile and the Eastern Office website, allowing the team to see which channel was driving inbound calls.
You can listen to call recordings directly in the CallRail dashboard and review goal completion — useful for assessing lead quality without manual logging.
Common Setup Pitfalls
- Old numbers still published: If a legacy number (e.g., a previous answering service number) is still live on the website or Google Business profile, calls may bypass CallRail entirely. Audit all published numbers when porting.
- Forgetting to set forwarding: A ported number with no forwarding destination will ring to nowhere. Always configure the destination immediately after porting.
- Pool vs. tracking confusion: Adding a ported number to a dynamic pool defeats the purpose of porting. Keep ported numbers as dedicated tracking numbers.
Related
- [2]
- [3]
- [4]