Routing
Routing by page and topic: the call reaches the desk that can answer
The IPO page rings the IPO desk. The research page rings research sales.
How it works
Your website already knows what a caller wants before they say a word: the page they are reading. CallCeptor uses that URL as the first routing signal, then asks at most two questions, such as topic and whether they are an existing client.
Rules are set per department, with business hours and trading holidays, so the dealing desk only rings during market hours and everything else turns into a callback.
What's included
- Rules match URL patterns, the topic picked, new or existing client, and language.
- Business hours per department, with trading-day holidays built in.
- Ring all, round robin or longest idle.
- Careers and vendor enquiries go to a form instead of a person.
Questions about routing by page and topic
How is page-based routing different from an IVR?
An IVR makes callers sort themselves by pressing numbers. Page-based routing uses the page the visitor called from, so someone on the IPO page reaches the IPO desk without a menu.
Which ring strategies are supported?
Ring all agents at once, round robin, or longest idle, set per department, with a timeout and an overflow department if nobody answers.
Related features
- Browser calling: Visitors click Call and talk. No app, no number to type, desktop or mobile.
- Rings your mobile: If the agent isn't at the dashboard, the call goes to their verified mobile.
- Callbacks with a deadline: Missed calls become callback tasks with an SLA countdown and escalation.
- Two-question intake: Name, mobile, new or existing client, and topic. Optional OTP to stop spam.
- All features
Put a Call button where your phone number is today.
Free for one person and 100 browser minutes a month. Larger firms can start with a pilot on one department.