How to Configure Caller ID Groups

Quick answer

To configure caller ID groups in DialerBee, go to Admin console → CLI Groups → Add Group. Give the group a name and a description, choose a selection mode (Match by area code for local presence, Random selection, or Sequential cycling), enter a Default CLI as the fallback when no area code matches, and leave Active on so campaigns can use the group. Then open the group and use Add CLI to add numbers one at a time in E.164 format, or Bulk Upload to paste or upload a CSV with one number per line. Use the Test Local Presence panel to enter a lead phone number and see which CLI would be selected. Register each number under Admin console → Compliance → CLI Management so it is verified before a campaign presents it.

Local presence means presenting a number the person you are calling recognises as local to them. It is one of the few outbound controls entirely in your hands, and one of the easiest to get quietly wrong: a pool with no fallback, a rotation mode nobody chose, or a number presented before it was registered.

This guide is the admin console procedure. It covers the CLI Groups screen where pools live, the caller ID settings on each gateway, and the compliance screen that decides whether a number may be presented at all. The capability overview is on the caller ID pool control page; what follows is where to click.

Before you start

Your numbers, in E.164 format. The form shows the style it expects, for example +1 212 555 0100.
A decision about grouping. One group per market is usually right, because the selection mode is a property of the group rather than of a number.
A gateway already configured, because caller ID is presented on a trunk. If that is outstanding, do the SIP trunk setup first, and have proof that you are entitled to present each number.

Step 1: Create the group

Go to Admin console → CLI Groups. The screen lists the groups in the tenant with a count beside the title. Click Add Group to open the Create CLI Group modal, subtitled "Set up a new Caller ID pool".

Group Name, in the style the placeholder suggests, for example "US East Coast". Name it for the market it serves.
Description, which the form describes as the purpose of this CLI group.
Selection Mode, which is chosen from three buttons rather than a dropdown. It defaults to random.
Default CLI, with the hint "Fallback number when no area code match is found".
Active, on by default, with the hint "Enable this group for campaign usage".

Step 2: Choose the selection mode

The three modes are described on the screen itself.

Mode	What the screen says	When it fits
Local presence	Match by area code	You hold numbers across the areas you call and want the recipient to see a local number
Random	Random selection	One market, and you want volume spread without a predictable order
Round robin	Sequential cycling	You want each number in the pool used an equal number of times, in order

Local presence only works if the pool contains numbers in the areas you dial. That is what the Default CLI is for: when no area code matches, the fallback is presented instead of the call failing. A pool set to match by area code with an empty fallback is the configuration that produces the strangest reports.

Step 3: Add the numbers

Open the group. In the detail view, Add CLI opens the Add CLI Number form, which asks for a Phone Number in E.164 format. For a pool of any size use Bulk Upload, which opens Bulk Upload CLIs. The format is stated on the screen: one number per line, in the style +12125550100, pasted into the textarea or uploaded with Choose File.

The group card shows the first twelve numbers with a "+N more" control for the rest, and View full details opens the whole pool. Per-number daily call caps and manual deactivation are part of caller ID pool control; use the values shown on the screen.

Step 4: Test local presence before a campaign uses it

The group detail view carries a Test Local Presence panel with the instruction "Enter a lead phone number to see which CLI would be selected". Type a number from the market you are about to call and press Test. This is the cheapest check in the whole procedure and the one most often skipped.

Test three cases: a number whose area code you hold, one you do not hold (which should return the Default CLI), and one in a different country.

Step 5: Set how the identity is presented on the trunk

Caller ID is presented by a gateway, so the header matters. Go to Admin console → Gateways, edit the gateway and open the Caller ID tab.

Caller ID Type defaults to Auto-detect, with Remote-Party-ID (RPID), P-Asserted-Identity (PAI) and From Header available. Your carrier will tell you which one they read.
Privacy Mode defaults to "None - Caller ID visible", with a restricted mode and a full anonymous mode.
Default Caller ID Override is the fallback number for this gateway.

Each gateway also has a DIDs & Caller IDs section on its expanded row, where Add DID opens the Add DID / Caller ID form. It asks for the DID Number and a Jurisdiction from UAE (TDRA), KSA (CITC), Egypt (NTRA), Jordan (TRC), Global or Other, and each number then carries a Verify action.

Step 6: Register the CLI for compliance

Go to Admin console → Compliance and find the CLI Management section. Add CLI registers a number, and each pending number carries a Verify action. Status is shown as Verified, Pending or Blocked.

The admin guide sets out what registration involves: the number, the jurisdiction and the ownership type (owned, leased or delegated), proof such as a letter of authorisation, a carrier agreement or a regulatory certificate, and then Submit for Verification. A CLI is usable on campaigns once it reaches the active state and not before.

A CLI Ownership rule toggle is described on the screen as "Verify tenant owns the CLI number for the jurisdiction". In a multi-tenant deployment that is what keeps one client's numbers out of another client's calls, so give every new tenant its own numbers.

Defaults and limits

Field	Screen	Default	Accepted values
Selection Mode	CLI Groups → Create CLI Group	Random selection	Match by area code, Random selection, Sequential cycling
Default CLI	CLI Groups → Create CLI Group	Empty	One number, E.164
Bulk upload format	CLI Groups → Bulk Upload CLIs	One number per line	Pasted text or a .csv file
Caller ID Type	Gateways → Caller ID	Auto-detect	Auto-detect, RPID, PAI, From Header
Privacy Mode	Gateways → Caller ID	Caller ID visible	Visible, restricted, full anonymous
Jurisdiction	Gateways → Add DID / Caller ID	as shown on the screen	UAE (TDRA), KSA (CITC), Egypt (NTRA), Jordan (TRC), Global, Other
CLI status	Compliance → CLI Management	Pending on registration	Verified, Pending, Blocked

Verify it works

Run Test Local Presence on three numbers, including one with no matching area code, and confirm the fallback is returned for that one.
Place a real call to a phone you control from the market in question and read the number that actually displays. The handset is the authority here, not the console.
After a day of traffic, generate the outbound calls and CDR reports and check the spread of presented numbers matches the selection mode you chose. Sequential cycling that produces one heavily used number means the campaign is on a different group.
Read the compliance audit report for blocks with a CLI ownership reason. Those are numbers being presented that the tenant is not cleared to present.

Troubleshooting

Local presence never matches. The pool has no numbers in the area codes you dial, so every call falls through to the Default CLI. Add numbers for those areas or accept the fallback deliberately.
Calls fail with a caller ID error at the carrier. The number is not provisioned on the trunk. Register it under DIDs and Caller IDs and authorise it on the carrier account.
The number is blocked before the call is placed. Compliance is doing its job. Check CLI Management for a status that is not verified, and check the CLI Ownership rule.
Answer rates fell across a whole market. Caller ID reputation is decided by carrier analytics and reputation providers rather than by the platform, and it varies by carrier, device and jurisdiction. Spread volume across more numbers, and take a suspect number out of rotation yourself.

Frequently asked questions

Where do I create a caller ID pool in DialerBee?

Admin console then CLI Groups, then Add Group. The Create CLI Group form asks for a group name, a description, a selection mode, a default CLI as the fallback, and an Active toggle that is on by default.

What selection modes are available?

Three, described on the screen as Match by area code, Random selection and Sequential cycling. The field defaults to random, so local presence is something you choose rather than something you get.

What is the Default CLI for?

It is the fallback number presented when no area code in the pool matches the number being called. The screen states this directly. A pool set to match by area code with no fallback is the most common misconfiguration in this feature.

How do I load a lot of numbers at once?

Use Bulk Upload on the group. The expected format is one phone number per line, either pasted into the textarea or uploaded as a .csv file. Numbers should be in E.164 format.

How do I check which number would be presented to a given lead?

Use the Test Local Presence panel in the group detail view. Enter a lead phone number and press Test, and the screen reports which CLI would be selected. Do this before a campaign uses the group, not after.

Does a number have to be registered before a campaign can present it?

Yes. Register it under Compliance then CLI Management, where status is shown as Verified, Pending or Blocked, and the CLI Ownership rule checks that the tenant is entitled to present the number in that jurisdiction. Numbers are owned by one tenant, so a number cannot appear on another tenant's calls.

How to Configure Caller ID Groups for Local Presence