34FIVE / CLIENT ONBOARDING

Aura messaging onboarding

A practical guide to registering each client’s messaging program and presenting a clear disclosure for every Aura number.

01 Register the client

Each 34Five client has its own 10DLC brand registration and a separate campaign for its approved use case. Associate each Aura number with the appropriate client campaign before sending. Do not share a number across client brands. A client may need additional campaigns for different use cases; confirm current number limits and any pooling approval with Telnyx.

02 Prepare the Aura disclosure

Replace every bracketed field below with the real Aura name, assigned number, registered client brand, specific conversational purpose, and publicly accessible client policy links. Place the completed disclosure clearly wherever the number or QR code is advertised, before a person texts the Aura.

Per-Aura opt-in disclosure template

Text [Aura name] at [Aura number] to connect with an AI Aura representing [client brand] for [specific purpose, such as conversation and introductions]. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is not a condition of purchase. Terms: [client terms URL]. Privacy Policy: [client privacy URL].

03 Define the message flow

The individual sends the first message. The Aura responds with information relevant to that request and the disclosed use case. Do not cold message. An inbound conversation does not authorize unrelated campaigns, marketing, or open-ended follow-up; obtain any additional consent required for those uses. Describe the exact flow and where the number and disclosure appear in the campaign submission.

04 Prepare and test keyword responses

Configure and test the welcome, STOP and HELP responses for each client program. The welcome should identify the client and program, frequency, rates, STOP and HELP. STOP must confirm the opt-out and suppress further program messages, subject to any permitted confirmation. HELP must identify the client and provide a working support contact. Match the registered keywords and sample messages to the actual behavior.

05 Privacy, evidence and review

Link to the client brand’s own accurate terms and privacy policy. The privacy policy should explain that mobile information is not sold or shared for third-party marketing and that SMS opt-in data and consent status are not shared for unrelated purposes. Keep evidence of the disclosure, opt-in source and time, campaign and number assignment, and opt-outs. Review actual sharing practices and applicable requirements with counsel and Telnyx before submission.

Before submitting

Verify the brand, use case, number, CTA, policy URLs, support contact, keywords and sample messages are consistent and accessible. Test the end-to-end flow and keep a reviewable URL or screenshot of the actual opt-in location. Campaign approval depends on carrier review; this guide does not guarantee approval.

34FIVE AIOS

Built around your business. Experienced through your teammates.

© 34Five · AI teammates. Human relationships.