️🗂 Uploadable routing

File-based routing

Some routing changes are too large for the dashboard. If you need to update hundreds of PIN codes, replace an entire denylist, load a new set of area code rules, or roll out a completely new IVR flow — doing it one by one is not practical.

File-based routing lets you upload a single CSV, TXT, or JSON file that replaces or updates your routing configuration in bulk. Prepare the file in a spreadsheet or generate it from your own system, upload it, and the changes are live immediately.

Upload CSV, TXT, or JSON files
Update hundreds of routing rules at once
Works with PIN codes, allowlists, denylists, area codes
Generate files from your own systems

Benefits of file-based routing

Discover how our features help you work smarter, save time, and improve how your business communicates.

📁

Bulk updates in seconds

Upload a file and hundreds of routing rules are updated at once. No clicking through the dashboard one rule at a time.

📌

Works across multiple features

Use file uploads to update PIN routing, allowlists, denylists, area code rules, zip code rules, or entire IVR flows.

⚙️

Built for automation

Generate routing files from your own systems or scripts and upload them whenever your configuration changes. Ideal for teams that manage routing programmatically.

How file-based routing works

You prepare a file in CSV, TXT, or JSON format that contains your routing rules. Each row or entry defines a rule — for example, a PIN code and its destination, a phone number for the allowlist, or an area code and the team it should route to.

Send the file to our support team. The system validates the file, reports any errors, and applies the changes immediately. You can also export your current configuration as a file, make changes in a spreadsheet, and upload it back — giving you a full edit-export-import workflow.

Use cases for file-based routing

File-based routing is useful whenever you need to make changes that are too numerous for the dashboard. Common examples include loading a new set of PIN codes for a large team — one row per employee with their PIN and destination number. Or replacing an entire denylist with an updated list of blocked numbers from your internal system.

Area code routing is another common use case. If you route calls differently based on the caller’s area code — for example, sending local callers to one team and national callers to another — you can define all the rules in a single file and upload them at once. The same applies to zip code routing, time-based rules, or any configuration that involves many entries.

Generate files from your own systems

The real power of file-based routing comes when you combine it with your own software. Your HR system exports a list of employees and their phone numbers — you turn that into a routing file. Your CRM exports a list of VIP customers — you turn that into an allowlist. Your scheduling tool knows who is on duty — you generate a routing file that matches.

Because the file formats are simple (CSV, TXT, JSON), any system that can export data can produce a routing file. A basic script that runs once a day can keep your CallFactory routing in sync with your internal systems without any manual work.

Validation and error handling

Uploading a file with hundreds of rules can feel risky. What if there is a mistake? CallFactory validates every file on upload. If a row contains an invalid phone number, a duplicate entry, or a formatting error, the system tells you exactly which line has the problem before applying anything.

You can also test changes by exporting your current configuration first, making a backup, and then uploading the new file. If something goes wrong, you upload the backup and you are back to where you started — all within minutes.

Included free with every number

File-based routing is included at no extra cost with every CallFactory number.

This feature is included free with every business number or international number.

PIN code routing

Route calls based on a PIN code. Each PIN leads to a different destination — ideal for VIP clients, internal lines, restricted services, and multi-tenant setups.

DenyList routing

Maintain a list of blocked phone numbers that are automatically prevented from reaching your team. Request a block and it takes effect instantly — temporarily or permanently.

API integrations

Tell us what you need, we build the endpoints. Our private API lets you integrate CallFactory telephony into your own software — no generic library, no guesswork, no wasted development time.

CSV, TXT, and JSON. These are simple formats that any spreadsheet application or script can produce.

PIN codes, allowlists, denylists, area code rules, zip code rules, and entire IVR flows. Essentially any routing configuration that involves multiple entries.

Yes. Export your current setup, edit it in a spreadsheet or text editor, and upload the updated file. This gives you a full edit-export-import workflow.

The system validates every file on upload. If there is an invalid entry, you are told exactly which line has the problem. No changes are applied until the file is clean.

Yes. Generate routing files from your HR system, scheduling tool, or any other software that exports data. A simple script can keep your routing in sync with your internal systems.

Basic spreadsheet skills are enough for most use cases. If you generate files from scripts or internal systems, some development knowledge helps. We provide templates and support to get you started.

Immediately after the file passes validation. Upload the file, the system checks it, and the new routing is live within seconds.

No. It is included free with every CallFactory number.