Open Caller IDs in Settings to check existing numbers or choose New caller ID → Bring your own real number.
If you bring your own phone number to Raise More, verify that you control it before using it as a caller ID. This ownership check is separate from SMS registration. When the voice-call flow reports failure, the pending number is removed and is not available for dialing. Raise More shows: “Your phone caller ID verification failed. Start a new verification request to try again.”
This article explains how verification works, the most common reasons it fails, and how to get your number verified.
How verification works
In the Twilio voice-call flow, adding a real phone number starts an automated verification call. Raise More displays a code, and you enter it on your phone’s keypad when you answer. Other provider setups can send a code by SMS or voice and ask you to enter it in the app. Follow the method shown in your form. The call-specific steps below describe the first flow.
Raise More shows you a verification code on screen, with a message like "We have placed an automated verification call to that phone number. Pick up, and enter the following verification code: 123456."
About a minute later, your phone rings. When you answer, a recorded voice asks you to enter the code. Type the code shown on your screen into your phone's keypad.
There is a short delay (about 60 seconds) between starting the request and the call ringing. That gap is there so you have time to read the code before the phone rings. Once you enter the matching code on the keypad, the provider confirms ownership, and your number is marked verified and becomes available in the dialer. You'll see "Your phone caller ID was verified successfully."
The number you verify has to be a standard 10-digit US phone number.
Common reasons verification fails
The wrong code was entered. The code on your screen has to match exactly what you type into the phone keypad during the call.
You didn't answer, or the call went to voicemail. A live person has to answer and enter the code. If the call rings out, goes to voicemail, or is declined, verification can't complete.
You hung up before entering the code. Stay on the call until you have entered all the digits and the recording confirms.
A carrier or app screened the call. Spam-screening apps, robocall blockers, and carrier-level call filtering can intercept the automated call before it reaches you, or send it straight to voicemail.
The number is a VoIP, virtual, or non-standard line. Some VoIP numbers, Google Voice numbers, and toll-free or short-code style numbers can't reliably receive the automated call, so the call may fail or never ring.
The number was entered incorrectly. A wrong digit or a missing area code sends the call to the wrong place or nowhere, so it never reaches you.
How to fix it
Double-check the number. Confirm the phone number and area code are entered exactly right, with no typos. It must be a 10-digit US number.
Be ready before the call rings. Read the code on screen, then keep the phone in hand. The call arrives about a minute after you start the request. Answer it yourself and do not let it go to voicemail.
Enter the code carefully. Type the code into your phone's keypad exactly as shown on screen, then stay on the line until the recording confirms.
Turn off call screening. Temporarily disable any spam-blocking or call-screening app on that phone, then start a fresh verification request.
Try a different number if needed. If a VoIP or virtual line keeps failing, verify a standard mobile or landline number instead. Most campaign staff use a personal cell.
Start a brand-new request. A failed attempt removes the number, so begin a new verification to get a fresh code and a fresh call. Don't reuse an old attempt.
If the call never rings, check the full number, its ability to receive voice calls, call screening, and carrier blocking. Allow for the call delay before starting another request.
When to contact support
Reach out to our support team if:
You've confirmed the number is correct, answered the call, and entered the right code, but it still fails.
The verification call never rings even after you disable call screening.
You see "Could not initiate verification. Have you already verified this number?" when you start the request.
You need to use a number type (toll-free, shared, or office system) that won't complete the standard flow.
Support can check the verification status on the carrier side and help with numbers that need special handling.
FAQ
Do I have to verify a number to make calls?
If you bring your own number, complete its ownership verification before dialing from it. A voice-capable number purchased through Raise More follows its provisioning process instead. A texting-only number cannot be used for voice calls.
Can I use my personal cell phone as a caller ID?
Yes, and most people do. A standard mobile line is the most reliable to verify.
Why is there a delay before the call rings?
The call is placed about 60 seconds after you start the request, which gives you time to read the verification code on screen before your phone rings.
The number was working before and now shows as unverified. What happened?
A caller ID can occasionally drift out of sync if the number's settings changed on the carrier side. Try re-verifying it, and contact support if it won't reconnect.
Can the same number be verified on two accounts?
A number can only be verified in one Raise More organization at a time. Successfully verifying it in a new organization removes its caller-ID entry from the old one. Use only a number you control and intend to use in the new organization.
How long does verification take?
The Twilio voice-call flow requests about a 60-second delay before the call starts. The total time depends on delivery and entering the code correctly. If it does not arrive after a few minutes, check the number and call screening, then start a fresh attempt or contact support.