Guides
Show your business number on calls
Current documentation
Set a verified caller ID for outbound voice calls without changing Beam messaging or inbound routing.
Voice onlyA verified caller ID changes the number a recipient sees on an outbound voice call. Some teams call this caller-ID masking. It does not change the sender for Beam blue messages, SMS/MMS, email, inbound-call routing, or consent obligations.
When to use this
Use it when your team places calls from an existing business number and wants customers to recognize that number. Keep the Beam-assigned line attached to the Beam conversation; do not replace it or paste external carrier credentials into Beam.
Choose the right place to set it up
| If the client places calls from… | Set up the verified caller ID in… | Keep in Beam |
|---|---|---|
| A HighLevel sub-account | That client's HighLevel sub-account | The Beam-assigned messaging line and its inbound receptionist mapping |
| A direct Twilio account | That client's Twilio account | The Beam-assigned messaging line and its inbound receptionist mapping |
Do not add an agency's or another client's number to the wrong sub-account. The person or business that owns the number must complete verification.
HighLevel setup
- Switch to the correct client sub-account.
- Open Settings → Phone Numbers and add a verified caller ID.
- Enter the business number. The number owner answers the verification call and enters the one-time code.
- Open the configuration for the outbound voice number and select Use verified number as caller ID for outbound calls.
- Place one safe call to a team member. Confirm the displayed number, intended agent behavior, and Beam timeline.
Direct Twilio setup
- In the correct account, open Numbers and Senders → Verified caller IDs.
- Add the business number and complete the verification call or code.
- Use the verified number only as the
Fromidentity for outbound voice calls. - Run one safe outbound-call test before using it with leads.
Do not mistake this for number masking
- It does not let an unowned number send Beam SMS or blue messages.
- It does not make inbound calls arrive in Beam; inbound forwarding and the Beam receptionist mapping remain separate.
- It does not change the selected Beam line for an existing customer conversation.
- It does not replace messaging registration, consent, opt-out, or caller-identification requirements.
Verification checklist
- Confirm the client owns and can answer the business number.
- Complete verification in the correct client account or sub-account.
- Attach it to the intended outbound voice number only.
- Call a safe team phone and confirm the displayed caller ID.
- Keep the result in the client's launch checklist. If the test fails, leave it off and use the assigned number until corrected.
Official setup references: HighLevel verified caller ID and Twilio outgoing caller IDs.