Control who can call
Every number has an Access Mode, and it decides one thing: whether qRaptor checks the caller’s number before connecting them to your agent.
| Mode | Behaviour |
|---|---|
| Public | Anyone who dials the number reaches the agent. |
| Authorized Only | Only numbers on that number’s whitelist get through. Everyone else is rejected before the agent is involved. |
The check happens before the agent runs, so a rejected call costs you nothing beyond the number’s rental.
Which one to use
Public is right for anything customer-facing — a support line, a booking line, a number printed on packaging. You don’t know who’ll call, and that’s the point.
Authorized Only is for a small, known set of callers. An internal line for field staff. A clinic line restricted to registered patients. A number you’re testing before you publish it anywhere.
Authorized Only with an empty whitelist rejects everybody, including you. The mode denies by default — an empty list isn’t “allow all”, it’s “allow none”. Add at least one caller before you rely on it.
Switch modes
Every number’s card has a single toggle button that flips to the other mode: Set Authorized Only on a public number, Set Public on a restricted one. It’s on the detail page too, in the header.
The switch takes effect on the next call. It only works on Active numbers — a suspended number’s mode can’t be changed.
Manage the whitelist
When a number is in Authorized Only, an Authorized Callers panel appears — below the grid on the numbers list, and full-width on the number’s detail page.
Add a caller
Click Add Caller.
| Field | Notes |
|---|---|
| Phone Number (E.164) | The caller’s number, e.g. +919876543210. Required. |
| Label | Optional note — Dr. Smith, Main Office. Purely for your benefit; it’s how you’ll recognise a row six months from now. |
Click Add Caller to save. The caller can ring the number immediately.
Remove a caller
Click the bin icon on the row and confirm. That caller stops getting through on their next attempt.
Number formatting is forgiving. Matching compares the last ten digits, so +919876543210, 919876543210, 09876543210 and 9876543210 all identify the same caller. Enter it as E.164 with the +91 prefix — that’s what the field asks for and it’s the least ambiguous — but a caller won’t be turned away over notation.
What a rejected caller experiences
They hear the call fail. There’s no recorded message explaining why, and nothing tells them they’re not on a list — from the caller’s side it’s indistinguishable from a number that isn’t working.
Rejected attempts don’t appear in your call log, because the rejection happens before a call record is opened. If someone reports that your number doesn’t work and you can’t find their call, an access-mode block is the first thing to check.
Testing a restricted number? Add your own mobile to the whitelist first. It’s the most common reason a test call to a freshly-restricted number fails.
Common issues
- A whitelisted caller still can’t get through — confirm the number is on that number’s list (each number has its own), and that the number is Active rather than Suspended.
- Nobody can call after switching to Authorized Only — the whitelist is empty. That’s the mode working as designed.
- The panel says the list couldn’t be loaded — that’s a load failure, not an empty list. Callers already on it still get through. Retry with the button in the panel.
- The toggle button is greyed out — the number isn’t Active. Suspended and releasing numbers can’t change mode.