Brilo AI supports Existing Phone Number Compatibility by either receiving calls forwarded from your published numbers or by accepting a ported direct-in-dial (DID) into the Brilo platform, depending on your telephony setup and regulatory region. In most cases Brilo AI can be configured to handle an already-published phone number through carrier-level call forwarding (forwarding) or by number porting (porting), and workflows will preserve caller context, routing rules, and escalation behavior. Your carrier and current telephony provider determine whether forwarding or porting is the right path; Brilo AI will validate the technical details (SIP endpoint, DID mapping, or forwarding rules) during onboarding. Expect coordination with your telecom team and one scheduled test window to confirm call routing, voicemail behavior, and human handoff.

Can Brilo AI use my published number?

Yes. Brilo AI can handle published numbers by configuring carrier-level call forwarding to Brilo’s assigned number or by porting the number to Brilo’s telephony setup when available.

Can you keep my phone number and move live calls to Brilo AI?

When porting is allowed in your region, Brilo AI can accept a ported DID; when porting isn’t possible, forwarding is used to route live calls into the Brilo AI voice agent.

Will my existing voicemail and IVR work with Brilo AI?

Brilo AI can preserve voicemail and IVR behavior when workflows and routing are configured, but carrier settings and the chosen integration method (forwarding vs. porting) determine exact behavior.

Enterprises often have widely published phone numbers tied to marketing, legal notices, or emergency contacts. Buyers ask about Existing Phone Number Compatibility because changing a public number can disrupt customer trust, regulatory notices, and multi-channel identity (callers expect a known number). Financial services and healthcare teams especially need a smooth transition path so published numbers keep working while Brilo AI is deployed. Teams also want clarity on how forwarding, SIP endpoints, or porting affect call recording, caller ID, and compliance workflows.

Brilo AI supports two common paths to accept calls to an existing published phone number:

In Brilo AI, phone-number forwarding is a configuration where your telephony provider routes inbound calls for a published number to Brilo’s SIP endpoint or assigned phone number.

In Brilo AI, a ported number (DID) is a telephone number moved into Brilo’s telephony provisioning so Brilo AI becomes the direct call recipient for that number.

For concurrency, retry, and capacity behavior when using forwarded or ported numbers, see the Brilo AI capacity and concurrency guidance for inbound call routing: Brilo AI capacity and concurrency guide

Related technical terms used in this article: porting, forwarding, SIP endpoint, DID, carrier-level forwarding, SIP trunk, voicemail routing, caller ID.

For guidance on service continuity and failover behavior when using forwarding or porting, consult the Brilo AI outage and failover guidance: Brilo AI outage & failover guidance

Healthcare example

A regional clinic configures carrier-level call forwarding from the published number to Brilo AI’s SIP endpoint during business hours so the Brilo AI voice agent handles appointment scheduling and pre-visit triage. Human agents remain on the original practice phone system for escalation.

Banking / Financial Services example

A retail bank ports a published customer service DID into Brilo AI to centralize inbound routing, IVR handoffs, and automated balance inquiries. Porting allows the bank to preserve caller ID and simplifies compliance logging in a single telephony environment.

Insurance example

An insurer forwards a claims hotline number to Brilo AI for initial intake but keeps the number actively registered with their carrier to retain certain fraud-detection carrier services; Brilo AI logs caller context and then performs a warm transfer to a human claims adjuster when needed.

Brilo AI voice agent workflows can escalate in three practical ways:

To enable these handoff modes, Brilo AI requires destination phone numbers or agent endpoints and routing logic in the workflow. If you use forwarding instead of porting, confirm that your carrier supports the transfer/bridging features needed for warm transfer to avoid dropped context.

For details about capacity, concurrency, and routing considerations when you forward or port numbers, review the Brilo AI capacity and concurrency guide: Brilo AI capacity and concurrency guide

Can I keep my published number and still use my existing carrier for billing?

Yes. If you use carrier-level call forwarding, your carrier remains the billing owner of the number; Brilo AI receives calls routed to the Brilo-assigned endpoint. If you port the number, billing and provisioning transfer according to carrier processes.

How long does porting take?

Porting timelines depend on your carrier and regional regulations; Brilo AI does not control carrier approval time but will coordinate the technical cutover and testing window once port approval is confirmed.

Will caller ID show my published number when Brilo AI answers?

Caller ID behavior depends on carrier settings and whether you forward or port the number. Porting typically preserves DID ownership and caller ID more directly; forwarding may require additional carrier configuration to preserve the displayed number.

What happens to my on-carrier voicemail when I forward calls to Brilo AI?

If forwarding is used, carrier voicemail may still receive calls when Brilo AI does not answer. Decide during setup whether Brilo AI replaces voicemail or coexists, and test to avoid voicemail or forwarding loops.

Are there legal or regulatory steps I must follow to port a number?

Porting usually requires authorization and documentation with your current carrier. Brilo AI will request the necessary details but does not provide legal advice—work with your telecom and compliance teams.

Can Brilo AI support emergency routing (E911) for a ported number?

Emergency service behavior depends on regional regulations and carrier processes. Brilo AI will coordinate technical routing but cannot change official emergency address registration without completing carrier and regulatory steps.