How this integration fits Flowtix
- Business messaging is managed by Flowtix at the platform level rather than requiring each subscriber to maintain a separate messaging-carrier connection.
- Supported SMS workflows become available only when the required messaging service and business-number availability are enabled for the organization.
- Messaging use remains subject to plan, provider, number, consent, opt-out, and acceptable-use requirements.
Use the Flowtix-managed business messaging setup
The public business-messaging path is based on Flowtix-managed messaging infrastructure. Subscribers should not assume they need to connect their own carrier account simply because SMS appears inside the workspace.
Require an enabled messaging service and available number
Supported SMS workflows depend on the organization having the required messaging service and business-number availability. If those prerequisites are not enabled, the presence of a communications module does not by itself make SMS sending available.
Keep messaging connected to customer context
Where the messaging workflow is enabled, SMS activity is most useful when it remains tied to the organization, customer record, ownership, and conversation context that the team is already using in Flowtix.
That shared context helps authorized teammates understand the surrounding customer history instead of treating messages as isolated carrier events.
Treat consent and opt-out handling as operating requirements
Organizations are responsible for using business messaging lawfully. Consent, identification, opt-out handling, content restrictions, permitted messaging windows, and provider rules can all matter depending on the destination and use case.
Expect service and plan controls
Plan entitlements, organization eligibility, provider status, number configuration, and usage controls can affect whether a supported SMS workflow is available at a given time.
Continue with this Flowtix integration path
Review the related Flowtix guidance before relying on the integration in production. Provider authorization, account eligibility, plan entitlements, organization settings, and service availability can still affect the workflow.