Number compatibility and migration
Call and text forwarding: verify each channel
A business number can receive a voice call and a text message through different configurations. Before forwarding or moving the number, map the destination for each channel and the method used to reply. A working forwarded call does not establish that customer texts arrive at the same phone, or that a reply uses the business number.
| Channel or action | Expected destination | Reply or return number to verify | Acceptance test |
|---|---|---|---|
| Voice call forwarding | Configured phone or answering destination | Check the approved outbound callback method separately | Call the public number and record the endpoint and greeting |
| Incoming SMS | Approved messaging app or service for that number | Send a test reply through the approved tool; record the displayed number | Text the public number and locate the message in the expected system |
| Email copy of an incoming text | Configured email address or addresses | Email delivery alone does not establish SMS reply capability | Confirm the copy arrives; test business-number replies separately |
| SMS relay to another mobile, if required | Mobile number explicitly supported by the proposed service | Ask whether replies are supported and which number is displayed | Verify relay and reply independently; do not substitute an email test |
01 / Number compatibility and migration
Specify the channel and the action you need.
For each public number, record the current provider, the proposed change and the required result. Distinguish keeping the number with its current provider and forwarding voice calls from transferring the number to another provider. Ask the providers which voice and messaging arrangements the exact number can use before scheduling a change.
Use precise language in a quote: receiving an SMS in an app, receiving an email copy and relaying an SMS to another mobile number are different requirements. If staff must reply from the business number, ask which approved app or service sends that reply. Do not infer the answer from a feature called “text forwarding.”
02 / Number compatibility and migration
Use the NumberBarn example to separate forwarding from notification.
NumberBarn’s features page describes forwarding calls to another phone number. Its Text Messaging Overview, updated October 7, 2026, separately describes an email notification that copies incoming texts to up to two email addresses. The email-setting instructions identify the receiving email addresses. These documents demonstrate separate channel controls; an email copy is not documentation of SMS relay to another mobile number or of replying by email.
The use restriction matters for a business. NumberBarn describes its own messaging as personal P2P messaging. Its business-messaging instructions instead point to String, with separate eligibility and registration requirements. The example therefore explains a configuration distinction; it is not a recommendation to use personal messaging for customer communications.
03 / Number compatibility and migration
Get compatibility answers before a migration.
Ask the proposed provider to confirm support for this exact number and business use, where incoming messages will be stored, what happens to the current messaging setup and which product staff will use afterward. Record any activation or registration dependency separately from the voice-routing change. Leave an unanswered requirement unresolved rather than marking the number ready.
Prepare a small acceptance record for both providers: the number, each requested change, the responsible account administrator and the order in which changes are expected. Ask what can be reversed and what requires support. Decide how the office will notice a failed channel during the transition instead of treating a successful voice test as completion.
04 / Number compatibility and migration
Test delivery and return identity independently.
Use consenting testers and clearly labeled test messages. After the approved configuration change, place a voice call to the public number, send a new text to that same number and check the expected receiving system. If an email copy is configured, check that copy separately. Then send a reply through the approved business-messaging tool and record the number the tester sees.
Keep the observations by channel: original number dialed or texted, destination reached, reply method and displayed return number. A delivered email cannot establish that a mobile SMS relay works. A reply from an employee’s personal number cannot establish business-number reply support. If a required result fails, pause acceptance of that channel and use the documented provider escalation or reversal process.
Common questions
Make the next step clear.
Resolve the details that matter to your team and callers.
Does forwarding voice calls also forward customer texts?
Verify messaging separately for the exact number and service. Voice-call delivery does not establish where incoming SMS is received or how staff can reply.
Is an emailed copy of a text the same as SMS forwarding to a mobile?
No. The receiving channel is email. A copy does not establish delivery as an SMS to another number, or an ability to send a business-number reply from that email.
Can NumberBarn’s personal texting example be used as evidence of business SMS support?
No. Its documented personal P2P messaging and its separate business-messaging route have different requirements. Confirm the applicable business product and number eligibility directly.
What should we check after moving messaging to another service?
Test a new incoming text, its destination and an approved business-number reply. Also repeat a voice call to confirm that the required voice route still works.
Accept a number change only after voice delivery, incoming messaging and the required reply identity have each passed their own test.
Review Revo’s current features and plans for the workflow your business needs.
Compare plans