If you are researching Trumpia texting, or standalone senders such as Ultimate SMS, the real decision is whether texting should run in a separate tool beside your CRM or inside the system that already holds your contacts, pipeline and bookings. This article does not review either product, and it states none of their features or prices; check those with each vendor. It answers the question behind the search for a firm of 10 to 250 people: which texting job you need done, what to check before choosing a standalone service, and how to move your texting onto the levelpartner.ai platform if one system turns out better than two.
The three jobs behind the search
Strip away the product names and texting does one of three jobs. You send one message to many people at once. You send messages automatically when something happens, such as a booking or a form. Or you hold conversations with prospects and clients. A standalone bulk sender is built mainly for the first.
The second and third jobs depend on knowing who the person is, what they bought and who looks after them, and that lives in your CRM. When the conversation sits in one system and the deal in another, advisers check two screens, notes go missing and reporting cannot tell you which texts produced revenue. That is the core trade-off of any separate texting tool.
What to check before choosing a standalone service
Put these questions to any dedicated texting vendor and write the answers down.
Where consent and opt-outs live
The tool must record when and how each person agreed to receive texts, apply opt-outs instantly and let you export consent with dates and sources if you leave. If your CRM and your texting tool hold different opt-out lists, someone will eventually text a person who asked you to stop.
Who owns the sending number
Check whether you get a number registered to your business or share one with other senders. Shared numbers inherit other people's reputation. Ask whether you can port the number in and out.
Where replies go
If replies arrive in the texting tool while your salespeople work in the CRM, replies get missed. Ask whether every inbound and outbound text appears on the contact record in full and in real time, and who keeps the integration working when either system changes.
Whether it can trigger on events
Reminders, follow ups and reactivation sequences need triggers from bookings, forms and pipeline stages. A broadcast-only tool cannot see those. If the answer involves a sync on a schedule or a second login, count that cost beside the subscription.
Before you start a move to the platform
- A contact export from your current tool, with mobile numbers in international format.
- Consent records for each contact: date, source and wording.
- A complete list of opted-out numbers, so they are never texted after the move.
- Your keywords, templates and automated sequences, written down so they can be rebuilt.
- A decision on your number: port the existing one, or start a new number and announce it.
- Custom fields for consent date and source, created before you import.
How to move your contacts and consent
Import contacts and consent first, opt-outs included, before any text leaves the new system.
- Go to Contacts and click Import Contacts.
- Choose Contacts and click Next.
- Upload your CSV file from the old texting tool.
- Choose to add new contacts or update existing ones.
- Map each column to a field, including consent date and source.
- Tick Don't update Empty Values if blanks must not overwrite.
- Optionally tag the contacts so you can find this import later.
- Review the mapping, then confirm and start the import.
Then mark every number on the opt-out list as do not disturb for SMS before any send, rebuild your sequences as workflows and check that a test reply arrives in Conversations.
Say the firm has 6,000 contacts in its CRM and 2,800 in a separate texting service, 2,100 of them in both. If eight advisers each spend around 20 minutes a day copying text conversations into CRM notes, that is about 13 hours a week, plus a monthly job of copying opt-outs back by hand. With texting on the platform and the overlap merged, the copying would stop, opt-outs would apply at once and every reply would sit on the same record as the deal. The inputs are illustrative.
The trade-off
A dedicated texting service may go deeper in specific areas, such as particular broadcast formats, that a broader platform does not match feature for feature. If your only use of text is high-volume promotion with no link to sales conversations, that depth might matter. For most firms in this size range the conversations are worth more than the broadcasts, and having them on the contact record is worth more than any single broadcast feature. For large sends on the platform, read sending bulk SMS without harming your number.
Migrating the contacts but not the opt-outs. A former subscriber who said stop in the old tool and then receives a text from the new one has every reason to complain. Mark the opt-out list do not disturb first and check a sample of numbers before any send.
What it replaces and the weekly time
The move replaces the second login, the integration, the export and import routine before each send and the manual copying of replies. Preparation takes a day or two, plus whatever time a number port needs. After that, texting is part of daily work in Conversations rather than a separate task.
When not to switch
Do not switch in the middle of a large campaign or a busy season. Do not switch if your consent records cannot be exported, until you have a plan to re-confirm consent with those contacts. If you send a handful of texts a month, never expect replies and have no CRM, a standalone sender may be enough for now. For other tool comparisons in this hub, see Yotpo SMS and Send in blue SMS. For what the platform does with texting day to day, read SMS business text messaging.
Troubleshooting
Imported contacts show without consent
The consent column was not mapped. Re-import the consent file as an update to existing contacts, matching on phone number, and map it to the custom field.
Numbers show the wrong country code
They were stored without international format. Clean them before import so every number carries its country code.
Texts from a ported number do not deliver
The port may be incomplete, or registration for the number may still be pending where your carrier requires it. Check both before resuming sends.
Old sequences behave differently
Workflow timing counts from the trigger, which may differ from how your previous tool counted. Test each rebuilt workflow on a test contact first.
Frequently asked questions
Can I keep my existing texting number?
Often, depending on the number type and your current provider. Allow time for the port and keep the old service active until it completes.
Will my contacts notice the change?
Not if you keep the same number. If you change numbers, send one text from the old number announcing the new one, and name your business in every message.
Do I need to re-collect consent when I switch tools?
No, if you migrate the consent records accurately. Keep the original source and date for each contact.
How is texting billed on the platform?
Texting usage is billed as used on top of the licence, which covers unlimited users and contacts.