How to Set Outbound Caller ID on a Business Phone System
How to Set Outbound Caller ID on a Business Phone System
Tom Reed · Updated 15 October 2026
Outbound caller ID is the number your customer sees when someone on your team calls them. On a small business phone system, pick it on purpose. Sales, support and accounts should each show the number that routes back to them. Only present numbers you own on your SIP trunk. Then check with your carrier that the number passes its checks: Ofcom CLI rules in the UK and STIR/SHAKEN caller ID authentication in the US. On SessionPBX you set each member's outbound caller ID from your connected numbers. Your carrier supplies those numbers and validates them.
This guide covers who shows which number, matching call-backs, changing caller ID safely and the carrier rules that affect answer rates. It is practical orientation, not legal advice.
What is outbound caller ID on a business phone system?
Outbound caller ID is the number your phone system presents when one of your team places a call to an outside line. In the UK it is usually called CLI, short for Calling Line Identification. It is a separate setting from inbound routing, which decides where calls to your numbers ring. A business phone system lets you choose the presented number per person or per team, as long as the number is one you hold. If you are still deciding which numbers to get in the first place, such as geographic, non-geographic or mobile, our guide to business phone number types covers that choice.
Which number should each person or team show?
The rule of thumb is simple: the number you present must route back to someone who can help. A customer who misses your call will usually ring back the number on their screen.
Most small teams use a main number, a few team numbers and some direct numbers. Adapt the table below.
| Caller | Number to present | Where call-backs go | Watch-out |
|---|---|---|---|
| Sales | The sales line | Sales ring group or queue | Do not present a personal direct number if deals should stay with the team |
| Support | The support line | Support queue, with an out-of-hours route | Make sure the support number's opening hours match when your team actually calls out |
| Accounts | The accounts line | Accounts team or a named person | Customers often ring back days later about invoices, so keep this number stable |
| Reception | The main business number | Reception, auto-attendant or main call flow | Avoid using the main number for everyone if reception cannot transfer quickly |
| Director | A direct number, or the main number | The director, then a colleague or voicemail | Decide whether you want customers to have a direct line before you present one |
| Remote staff | Their team number, as if they were in the office | The same team route | Remote and office staff on one team should present the same number |
Consistency matters as much as the choice itself. When five people on one team each present a different number, customers cannot tell whether the call came from you, and call-backs scatter.
How do you make call-backs land in the right place?
Every number you present needs a matching inbound route. Before you set a number as caller ID, check where a call to that number goes today, during opening hours and outside them.
Work through each presented number in turn:
- Person. A direct number should ring the person first, then go somewhere sensible if they do not answer: a colleague, a team or voicemail that someone checks.
- Ring group. A team number can ring the whole team together or in order, so a call-back reaches whoever is free.
- Queue. A busy support line can hold callers in a queue until someone is available, with an overflow route for long waits.
- Call flow. A main number can greet callers with a menu and send each choice to the right team.
Out-of-hours behaviour is where call-backs most often go wrong. If your accounts team makes calls until six but the accounts number switches to a closed message at five, late call-backs hit a dead end. Line up the opening hours on each route with the hours your team actually makes calls.
On SessionPBX, the routing side is set per number: "Give each inbound number its own route to a person, group, queue or call flow." Ring groups, queues, IVR menus, business-hours routing and visual call flows are part of Teams Business. Teams Phone and Teams Business are SessionPBX plans, not Microsoft Teams. For the wider design of inbound routing, see our guide to call routing for small businesses.
How do you set or change caller ID on a hosted PBX?
A careless change can send calls out with a number that does not work for call-backs or that your carrier rejects. Follow the same steps every time.
Set-and-test checklist
- Confirm the number is live on your trunk. Check with your carrier, or in your carrier account, that the number is active on the SIP trunk connected to your phone system. A number that is still being moved from another carrier is not ready.
- Confirm the inbound route. Call the number from an outside line and check it reaches the person, group, queue or call flow you expect, both in and out of hours.
- Set the member's outbound caller ID. In your PBX admin portal, choose the number for each member or team. On SessionPBX the admin can "set each member's outbound caller ID from your connected numbers".
- Place a test call to a mobile. Check the number shown on the screen is the one you set, in the format you expect.
- Place a test call to a landline. Some networks display numbers differently, so check a second type of line.
- Ring back the number you saw. Confirm the call-back reaches the right route, not an old destination or a dead end.
- Record the change. Note who changed what, when and why, so the next person can see which number each team presents.
Which carrier rules affect whether your calls get answered?
Caller ID is not only a phone system setting. The number you present travels through your carrier and other networks, and those networks apply their own rules. Your PBX chooses which number to present; your carrier is the party that validates it and passes it on. This section summarises the rules as of October 2026. It is orientation, not legal advice, and rules change, so check the current text and ask your carrier how it applies them.
UK: Ofcom General Condition C6 and the CLI guidance. As of October 2026, Ofcom's guidance on Calling Line Identification says that "General Condition C6 requires communications providers to provide CLI facilities" and that "Where CLI Data is provided, it must include a valid, dialable telephone number which uniquely identifies the caller." The guidance page was last updated on 15 July 2026, and Ofcom lists a current version alongside a newer version taking effect on 15 July 2027. In practice, this means the number your team presents should be a real number that a customer can dial back, and one you have the right to use. Your carrier applies these checks; calls presenting numbers that fail them may not be connected.
US: FCC STIR/SHAKEN caller ID authentication. As of October 2026, the FCC's page on caller ID authentication explains that it "requires all voice service providers to implement the STIR/SHAKEN caller ID authentication framework in their IP voice networks." Under that framework, calls can have their caller ID "signed" as legitimate by originating carriers and validated by other carriers before reaching consumers. The signing is done by your originating carrier, and how confidently it can vouch for a number generally depends on whether that number is on your account with it. Ask your carrier how it signs calls from your numbers.
The common thread: present numbers your carrier knows are yours. The PBX does not perform CLI validation or STIR/SHAKEN signing. SessionPBX does not supply numbers or porting either. You connect your own SIP trunk, and in its words, "Your carrier bills you for numbers and calls".
Why are your calls showing as "spam likely" or not getting answered?
When customers stop picking up, check the caller ID side first.
| Symptom | Likely cause | What to check | Who fixes it |
|---|---|---|---|
| Calls fail or are rejected straight away | The presented number is not on your trunk | Is the number active on the trunk you are calling through? | Carrier, then you update caller ID |
| Customers see a different number from the one you set | The carrier is overriding a number it cannot validate | Ask the carrier which numbers it will accept as caller ID | Carrier |
| Customers do not recognise the number | Each person on a team presents a different number | Is one number set for the whole team? | You |
| Call-backs reach nobody | The presented number does not route back, or is closed when calls go out | Ring the number yourself in and out of hours | You |
| Calls labelled as possible spam in the US | Signing, number reputation or calling patterns such as many short calls | Ask the carrier how your calls are signed and whether it offers registration for your numbers | Carrier, plus changes to how you call |
| Customers report calls you never made | Someone else is presenting your number | See our guide below | You and your carrier |
Some practical next steps:
- Ask your carrier about caller ID acceptance. In the UK, ask which numbers it accepts as CLI on your trunk. In the US, ask how it signs your calls, and whether it offers registration of business numbers with call analytics services.
- Look at how you call. Large batches of very short calls from one number can look unusual to networks. Spread outbound work across the right team numbers and make sure each call has a purpose.
- Keep numbers consistent. A number customers have seen before, and that rings back to you, is more likely to be answered than an unfamiliar one.
If the problem is the reverse, with someone else copying your number to make calls, that is a different issue with a different response. Our guide to caller ID spoofing of your business number covers what to do.
What should you review when people, teams or numbers change?
People leave, teams reorganise and numbers move carriers. Each change can leave someone presenting a number that no longer works.
- Leavers. If a leaver had a direct number, decide what happens to it. Point its inbound route at their team or replacement, and make sure no remaining member still presents it without a route behind it.
- Team moves. When someone moves from support to sales, change their caller ID to the sales number on the same day you change their ring group or queue membership.
- New numbers. Set a new number as caller ID only after it is live on your trunk and its inbound route is tested.
- Porting cutover. When moving numbers between carriers, re-point caller ID before the old number is released. If a member presents a number that is mid-move, outbound calls may fail or show the wrong number. Keep members on a number that is already live until the move is confirmed, then switch.
Quarterly caller ID audit
- List every member and the number each presents. Check that every team member shows the same team number.
- Ring each presented number from an outside line, in and out of hours, and confirm where it lands.
- Check every presented number is still active on your trunk, and remove any that are not.
- Confirm leavers' numbers are routed somewhere sensible and not presented by anyone without a reason.
- Review any answer-rate complaints from the last quarter and work through the troubleshooting table above.
For questions about the trunk itself, such as which numbers are on your account and how the carrier handles caller ID, see our guide to SIP trunks for small businesses.
Setting caller ID on SessionPBX
SessionPBX is a hosted PBX that uses your own SIP trunk for outside calls. In its own words: "connect the SIP trunk you already use — any SIP-compliant carrier works out of the box." Your carrier supplies your numbers; you then set each member's outbound caller ID from your connected numbers, and give each inbound number its own route. Teams Phone covers everyday calling, messaging and voicemail with your own SIP carrier for external calls. Teams Business adds ring groups, queues, IVR, call flows, recording and supervision. Both are SessionPBX plans, not Microsoft Teams. Compare plans and start a free trial on the SessionPBX hosted PBX page. For background on how hosted systems fit together, see our guides to the PBX phone system and the cloud-based phone system.
FAQ
Can I change my outbound caller ID to any number?
No. Present only numbers you own or have the right to use, normally numbers on your SIP trunk. In the UK, Ofcom's guidance says CLI data must include a valid, dialable number that uniquely identifies the caller. In the US, the FCC requires carriers to authenticate caller ID using STIR/SHAKEN. Check the current rules with your carrier.
Can different staff show different caller IDs?
Yes. On SessionPBX you set each member's outbound caller ID from your connected numbers. Most teams give everyone in a team the same number and reserve direct numbers for people customers need to reach personally.
Does SessionPBX handle STIR/SHAKEN?
No. Caller ID authentication and signing are done by your SIP carrier, not the phone system. Ask your carrier how it signs calls from your numbers.
Should we withhold our number on outbound business calls?
Generally, show a number customers can call back. Ofcom's guidance recognises that individuals have the right to withhold their number, but for business calls a withheld number gives the customer no way to return the call. This is not legal advice; check the current guidance for your situation.
Why does my caller ID show the wrong number after we switched carriers?
The new trunk may not have the number yet, or the member's caller ID still points at a number on the old trunk. Confirm the number is live with the new carrier, then set it again and test. Our guide on how to choose a SIP trunk provider for a hosted PBX covers switching carriers in more detail.
