Direct Answer (TL;DR)
Yes — you can keep your existing phone numbers when you deploy Brilo AI. Brilo AI supports routing incoming calls to our voice agents via carrier call forwarding, SIP endpoints, or by integrating your carrier’s porting process so your current Direct Inward Dial (DID) numbers continue to reach customers. The exact path (carrier porting versus forwarding to a Brilo-managed SIP endpoint) depends on your telephony provider and local number portability rules, and Brilo AI works with your telecom team to validate the best approach. Common technical terms to know here include number portability, SIP trunk, DID, call forwarding, and carrier porting.
Can we keep our current numbers when switching to Brilo AI? Yes — many customers retain their numbers through forwarding or porting; the choice depends on your carrier and setup.
Will Brilo AI transfer our numbers for us? Brilo AI coordinates with your team but number porting is completed through your carrier or authorized telecom partner.
Do we need new DIDs to use Brilo AI? Often you can keep existing DIDs by forwarding or porting them, but some deployments use a Brilo-assigned SIP endpoint instead.
Why This Question Comes Up (problem context)
Enterprises ask this because phone numbers are brand-facing assets tied to marketing, customer trust, and regulatory records. Banks, insurers, and healthcare providers cannot afford dropped calls or long transition periods. Buyers want clarity on whether they must reprint materials, update emergency contact lists, or change routing for call recording and compliance. They also need to understand carrier timelines and whether Brilo AI requires any temporary number changes during cutover.
How It Works (High-Level)
Brilo AI can accept calls routed from your existing numbers in one of two common workflows:
Carrier-level porting: your carrier moves the DID ownership so that calls land directly on Brilo-managed telephony resources. This requires standard porting paperwork with your carrier and coordination on cutover windows.
Carrier call forwarding or SIP forwarding: you keep number ownership with your carrier and forward calls (or use a SIP trunk) to a Brilo AI endpoint where the Brilo AI voice agent answers and runs workflows.
In Brilo AI, number porting is the process where your carrier transfers the ownership or routing of a DID so incoming calls reach Brilo-managed telephony resources.
In Brilo AI, call forwarding is when your existing carrier routes incoming calls for a number to a Brilo AI endpoint or SIP trunk so the Brilo AI voice agent answers on your behalf.
In Brilo AI, a Direct Inward Dial (DID) is a customer phone number that can be routed or ported so Brilo AI receives and handles calls intended for that number.
For more on how Brilo AI handles forwarding and routing logic, see the Brilo AI intelligent call forwarding guide: Brilo AI intelligent call forwarding guide.
Guardrails & Boundaries
Brilo AI will not and cannot complete carrier porting paperwork on your behalf; porting requires account-level authorization with your telecom provider. Brilo AI recommends these guardrails:
Do not change live marketing numbers during a transition window without a staged plan; test forwarding on non-peak numbers first.
Avoid simultaneous dual routes that cause forwarding loops at the carrier level — Brilo AI can advise on safe forwarding configurations and cutover sequencing.
Limit cutover to approved maintenance windows and validate call recordings, voicemail handoffs, and call routing before redirecting high-volume numbers.
In Brilo AI, a forwarding loop is a carrier-level condition where two or more call routes repeatedly pass the call between endpoints; Brilo AI provides guidance to avoid this while you configure carrier settings. See Brilo AI’s recovery and system-failure guidance for carrier-level forwarding scenarios: Brilo AI system recovery & forwarding guidance.
Applied Examples
Healthcare
A hospital switching inbound appointment lines keeps its published DIDs by forwarding them to Brilo AI during evenings and weekends. Brilo AI answers with patient-identification prompts and routes urgent clinical issues to on-call staff per the configured escalation rules. Before cutover, compliance and clinical teams validate how PHI is collected and logged.
Banking / Financial services
A regional bank preserves its customer-service numbers via carrier porting so account holders never notice a number change. Brilo AI answers balance inquiries and routes authentication-required transfers to human agents when the conversation needs identity verification or payment processing.
Insurance
An insurer forwards claim intake numbers to Brilo AI for first‑notice‑of‑loss triage. The Brilo AI voice agent captures structured claim data and hands complex claims to human adjusters based on severity triggers.
Human Handoff & Escalation
Brilo AI workflows are designed to escalate when configured conditions occur. Common handoff methods:
Warm transfer with context: Brilo AI opens the call to a human agent with a session summary and key fields prefilled in your CRM.
Cold transfer: Brilo AI sends the call to a phone number or queue without holding context when your telephony setup requires it.
Webhook-triggered escalation: Brilo AI can POST session metadata to your webhook endpoint so downstream systems can create tickets or trigger agent workflows.
Brilo AI recommends testing warm transfers and context delivery with a small agent team before scaling to high-volume numbers.
Setup Requirements
Provide account access: Grant Brilo AI or your telecom coordinator the necessary contact and account references for your carrier so porting or forwarding requests can be initiated.
Share number inventory: List the DIDs you want to keep and indicate which should be ported versus forwarded.
Configure forwarding/SIP: Work with your carrier to forward calls to the Brilo AI SIP endpoint or complete porting paperwork; Brilo AI will validate the SIP endpoint and call routing. See guidance on concurrent call capacity and routing: Brilo AI concurrency & routing considerations.
Test transfers: Validate warm and cold transfers between Brilo AI and your human agents; confirm caller context and CRM updates with your integration, e.g., your CRM connection: Brilo AI HubSpot integration overview.
Approve cutover window: Schedule a maintenance window for final porting or forwarding change and verify monitoring and rollback plans.
Monitor and validate: After cutover, monitor call completion rates, agent handoffs, and recording integrity for the routed numbers.
Business Outcomes
Keeping existing numbers reduces customer confusion, preserves trust, and avoids costs associated with reprinting materials and updating regulatory records. By retaining your DIDs, Brilo AI helps maintain continuity while enabling:
Faster adoption since customers continue dialing familiar numbers.
Simplified transition for compliance teams because records and contact histories remain tied to existing DIDs.
Predictable routing that allows Brilo AI to apply automation and escalation rules without changing customer behavior.
FAQs
Can Brilo AI port our phone numbers directly?
Brilo AI coordinates with your team and provides technical guidance, but number porting is completed through your carrier or authorized telecom partner and requires account authorization and carrier paperwork.
Will keeping our numbers affect call recording or analytics?
No — once calls reach Brilo AI via forwarding or porting, Brilo AI’s call handling, recording, and analytics apply the same way they do for Brilo-assigned endpoints; validate your recording retention and compliance settings before cutover.
Do we need to change our CRM or other integrations to keep numbers?
Usually no. Brilo AI can pass call metadata and context into your CRM through existing integrations or webhooks; plan a brief validation step to ensure DIDs map correctly to customer records.
What happens if the carrier port is delayed?
If porting is delayed, you can temporarily forward calls to Brilo AI’s SIP endpoint so service continuity is maintained; Brilo AI will work with you to avoid duplicate routing and forwarding loops.
Next Step
Review call routing and forwarding options in the Brilo AI intelligent call forwarding guide: Brilo AI intelligent call forwarding guide.
Validate telephony capacity and concurrency settings before cutover: Brilo AI concurrency & routing considerations.
If you have compliance or operational questions, consult Brilo AI’s compliance overview and DNC/TCPA guidance: How Brilo AI ensures TCPA & DNC compliance.
If you’d like help planning a port or forwarding cutover, contact your Brilo AI account team or open a support request via the Brilo AI FAQ: Brilo AI FAQ.