Heritage Connect SMS
Fits an eligible phone-system user who needs one-to-one business texting inside the same desktop and mobile application used for calling.
Review Heritage ConnectBusiness Messaging
Business texting that belongs to the business.
Give employees an accountable way to send and receive messages from approved company numbers—through Heritage Connect, CloudMessage.io, email, or a software-driven workflow.
Set the calendar honestly: A complete 10DLC Campaign commonly needs one to two weeks for review. Requests for corrections, additional evidence, carrier review, and final number registration can extend that window.
Before the first message
Brand + Campaign + eligible number- 1Describe the real workflow
- 2Show how people consent
- 3Publish aligned policies
- 4Submit and respond to review
- 5Enable, test, then launch
Choose the working surface
One texting need does not imply one application.
Start with who sends the message and what must happen next. The approved number and registration are shared foundations; the user experience follows the workflow.
CloudMessage.io
Fits teams that share messaging numbers, coordinate conversations, reuse responses, and add approved campaign or integration features.
Compare its plansSMS API
Fits an authorized workflow where business software must send, receive, or react to messages. Exact API behavior, implementation, ownership, and billing require discovery.
Scope the workflowTargeted comparison
Match the interface to the job.
| Need | Heritage Connect SMS | CloudMessage.io | SMS API |
|---|---|---|---|
| Best fit | Individual user messaging | Shared team workspace | Software-triggered workflow |
| Human conversation | Primary fit | Primary fit | Must be designed |
| Shared team access | Not the primary model | Primary fit | Must be built |
| Lists, blasts, and drips | Not the primary model | Professional plan | Custom implementation |
| Keyword auto replies | Configuration-dependent | Starter and Professional | Custom implementation |
| Trigger from business software | Limited | Supported integrations vary | Primary fit |
| Billing unit | Phone-system user plus messaging services | Per user plus messaging services | Discovery, service, and usage |
CloudMessage.io
A business messaging workspace for a team.
Use eligible existing Heritage numbers or new dedicated numbers. A supported number can also be shared with Heritage Connect when the approved design calls for both user and team access.
- SMS and MMS conversations
- Number sharing and multiple-number access
- Canned responses, away messages, and keyword replies
- Mobile applications for iOS and Android
- Professional campaigns, reminders, and supported integrations
Synthetic demonstration · fictional data
CloudMessage.io plans
Start with the collaboration the team needs.
Both plans are billed per user. Registration, number enablement, and message usage remain separate so the customer can see what drives the total.
Starter$15per user/month
For direct team conversations and repeatable responses without campaign tooling.
- SMS and MMS messaging
- Away messages
- Number sharing
- Canned responses
- Keyword auto replies
- PBX single sign-on
Professional$25per user/month
For teams that need scheduled outreach, lists, multi-step campaigns, or supported integrations.
- Everything in Starter
- Blasts and lists
- Drip campaigns
- Scheduled messages and reminders
- Supported integrations
- Click-to-call
Additional billing units10DLC Brand and Campaign chargesSMS enablement per numberSMS and MMS usageApproved implementation or integration work
10DLC readiness
Approval starts before the application is submitted.
10DLC registration tells the messaging ecosystem who is sending, what they intend to send, and how recipients authorize and stop messages. Heritage helps organize the submission; the customer owns the truth and operation of the campaign.
- 01
Define the use case
Name the people receiving messages, what they will receive, why they receive it, and whether the program is conversational, informational, or marketing.
- 02
Choose authorization paths
Document every way a person can opt in—website form, signed form, verbal permission, keyword, QR code, or a consumer-initiated conversation.
- 03
Prepare public evidence
Align the website, opt-in language, privacy policy, messaging terms, contact details, and representative message samples.
- 04
Register the Brand
Submit the customer’s accurate legal identity and business details for verification. A Campaign cannot proceed until the Brand is verified.
- 05
Submit the Campaign
Register the actual use case, authorization flow, samples, HELP and STOP behavior, and required public URLs for review.
- 06
Enable and test numbers
After approval, associate eligible numbers, test consent and opt-out behavior, confirm users, and launch only the registered workflow.
Public pages must match the submission.
A reviewer needs to reach the business website, opt-in method, privacy policy, and messaging terms without a login. Brand names, domains, contact details, samples, and use cases should tell one consistent story.
Review time is not implementation time.
The planning window begins after a complete Campaign is submitted. Corrections, evidence requests, special use cases, carrier review, and number registration can add time.
Operate the campaign that was registered.
New message purposes, authorization methods, audiences, numbers, or content may require updated disclosures, registration, and review.
Prepare the evidence
Use the readiness guide before Heritage submits the Campaign.
Adaptable privacy, messaging-terms, consent, HELP/STOP, and campaign examples live in one working resource.
Common questions
Reasonable expectations are part of the service.
Can Heritage guarantee Campaign approval in one to two weeks?
No. One to two weeks is a planning expectation after a complete submission, not a guarantee. Reviewers may request corrections or evidence, and some use cases require additional review.
Does CloudMessage.io pricing include registration and messages?
No. Starter and Professional are per-user application charges. 10DLC Brand and Campaign charges, per-number enablement, SMS/MMS usage, and approved implementation work are separate.
Can an existing business number be used?
Often, yes, when the number, carrier path, registration, and selected interface are eligible. Heritage validates the number before committing to the design.
Does a privacy-policy template guarantee approval?
No. The actual policy and opt-in flow must accurately describe the customer’s practices, campaign, industry, and applicable requirements. The guide provides working examples, not legal advice or an approval shortcut.
Can a customer start sending while approval is pending?
The production workflow should launch only after the required Brand and Campaign approvals, number enablement, and end-to-end testing are complete.
Design before registering