Cenvi SMS Program - Consent & Disclosure Information

Brand: Cenvi (operated by Bookify Events Inc., Delaware) · Last updated: 2026-05-26 · Audience: A2P 10DLC reviewers, mobile carriers, and the public

Contents

1. Program Overview
2. Message Categories
3. Sample Messages
4. Opt-In Surfaces (where users provide their phone)
5. Disclosure Language Shown at Every Phone Field
6. Screenshots
7. Message Frequency
8. Cost
9. Opt-Out, Opt-In, and HELP
10. Privacy
11. Technical Compliance
12. Support

1. Program Overview

Cenvi (cenvi.events) is an event-planning and vendor-booking marketplace plus festival ticketing platform. Cenvi operates an SMS messaging program used to deliver account-related, transactional, event, and customer-care text messages to users who have provided their mobile number and consented to receive SMS through a Cenvi-hosted web form.

Cenvi uses Twilio as its SMS delivery provider. Every Cenvi SMS begins with the brand prefix Cenvi: (or a Cenvi-branded message body) and ends with an auto-appended compliance footer: "Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply."

2. Message Categories

Account & authentication: one-time email-verification codes during signup and re-verification.
Transactional vendor notifications: payment-received receipts; booking change approvals and rejections.
Event invitations & RSVP: event-host-initiated invitations to guests on a planner's guest list, including the planner's custom message and a unique RSVP link.
Ticketing: registration confirmations, ticket delivery, and event-day operational updates for ticket buyers.
AI phone assistant link delivery: when a caller on a Cenvi (or Cenvi-vendor) AI-answered phone line verbally asks for a booking or planner link, a single SMS containing that link is sent to the caller's own number in direct response to their request.

3. Sample Messages

All Cenvi SMS conclude with the auto-appended compliance footer. Sample messages, exactly as users receive them, follow.

Account & authentication

Your Cenvi verification code is 482917. Expires in 3 minutes. Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

Vendor - payment received

Cenvi: Payment received $1,250.00 for Smith Wedding Reception. Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

Vendor - booking change approved

Cenvi: Your timing change for "Garden Wedding" was approved. Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

Vendor - booking change rejected

Cenvi: Your timing change for "Corporate Gala" was rejected. Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

Event invitation (planner-initiated, third-party-consent attested)

Cenvi: You're invited to Priya & Arjun's Wedding, June 15. Please RSVP by May 30: https://cenvi.events/events/rsvp?token=xyz789 Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

Ticket buyer - confirmation

Cenvi: Your ticket for Holi Festival 2026 is confirmed. View your ticket: https://cenvi.events/ticketing/verify/abc123 Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

AI phone assistant - booking link (sent at the caller's verbal request)

Cenvi: Here's your booking link with everything filled in - review and confirm: https://cenvi.events/store/elegant-events?package=gold&date=2026-08-15 Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

AI phone assistant - planner link (sent at the caller's verbal request)

Cenvi: Here's your Cenvi planner to browse vendors and build your event: https://cenvi.events/search?eventType=wedding Prefer to talk to our team? Schedule a time here: https://cenvi.events/schedule/team-cenvi Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply.

4. Opt-In Surfaces

Cenvi collects mobile phone numbers and SMS consent on the following Cenvi-hosted forms. Each registration surface presents an explicit SMS-consent checkbox that is unchecked by default and is never pre-selected. The checkbox label names Cenvi as the sender, lists the applicable message categories, states that message frequency varies and msg & data rates may apply, provides STOP opt-out instructions, and links to our Privacy Policy and Terms. On surfaces where the SMS program is how the service itself is delivered (ticket confirmations for a purchase, account/booking notifications), the checkbox is required to submit the form - but the user must still affirmatively check it themselves. Marketing consent is always a separate, optional, unchecked checkbox and is never a condition of purchase or signup.

Surface	Live URL pattern	How the recipient reaches it
Planner email/password registration	`https://cenvi.events/signup`	Header → "Sign Up" → choose Planner → fill the form including phone
Vendor email/password registration	`https://cenvi.events/signup`	Header → "Sign Up" → choose Vendor → fill the form including phone
Vendor registration on a ticketing event page	`https://cenvi.events/ticketing/register/{registrationUrl}`	Vendor clicks the event's public link → "Become a Vendor" → fills the vendor account form
Public ticket registration	`https://cenvi.events/ticketing/register/{registrationUrl}`	Anyone with the public ticket link clicks it and fills the registration form
AI phone assistant (verbal opt-in)	(inbound phone call to a Cenvi or Cenvi-vendor line)	Caller verbally asks the assistant to text them a booking or planner link; the assistant confirms and one SMS is sent to the caller's own number
Public RSVP form (planner-shared link)	`https://cenvi.events/events/rsvp?public={token}`	Recipient clicks a planner's shared RSVP link and fills the form
Event guest list (planner-side; third-party consent)	(in-app, planner only)	Planner opens their event → Guest List section → enters guest's number after attesting to consent

5. Consent Checkbox & Disclosure Language on Each Surface

Each registration surface presents an explicit, unchecked SMS-consent checkbox adjacent to the phone input. The exact checkbox label from each surface follows. All labels link to our Privacy Policy (and Terms where shown).

Planner registration (account-transactional; unchecked checkbox, required to submit)

☐ Text me account & booking updates (codes, confirmations, receipts, reminders). Msg frequency varies; msg & data rates may apply. Reply STOP to opt out. See our Privacy Policy & Terms.

Vendor registration (vendor-transactional; unchecked checkbox, required to submit)

Shown on both the main vendor signup at /signup and the vendor signup on ticketing event pages:

☐ Text me account & booking updates (codes, receipts, confirmations). Msg frequency varies; msg & data rates may apply. Reply STOP to opt out. See our Privacy Policy & Terms.

Public ticket registration (unchecked checkbox, required to complete purchase)

The phone field carries an inline disclosure, and the Communication Preferences section presents the explicit consent checkbox the buyer must check themselves:

☐ Text me my ticket confirmation and event updates for this purchase (reminders, day-of info). Msg frequency varies; msg & data rates may apply. Reply STOP to opt out.

The ticket registration form additionally presents a separate, optional, unchecked marketing-consent checkbox (never a condition of purchase):

☐ Yes, I'd like to receive promotional emails and SMS from Cenvi with event tips, exclusive discounts, and vendor recommendations. I can unsubscribe at any time by replying STOP (SMS) or using the unsubscribe link (email). Msg & data rates may apply.

AI phone assistant (verbal opt-in during an inbound call)

Cenvi and participating Cenvi vendors operate AI-answered phone lines. When a caller verbally asks the assistant to text them a booking or planner link, the assistant confirms it will text the number the caller is calling from, and exactly one SMS containing the requested link is sent to that number. The SMS is sent only in direct response to the caller's own request within that call, never on a schedule or list basis, and carries the standard STOP/HELP footer. Numbers collected this way are not enrolled in any recurring messaging program.

Public RSVP form

By providing your number, you agree to receive event-related SMS (such as RSVP confirmations and updates) from Cenvi on behalf of the event host. Msg frequency varies; msg & data rates may apply. Reply STOP to opt out, HELP for help. See our Privacy Policy.

Event guest list (planner-side, third-party consent)

By adding a guest's mobile number, you confirm you have permission from that guest to send them event SMS via Cenvi. SMS messages will include event invitations and RSVP reminders. Recipients can reply STOP at any time to opt out. Msg & data rates may apply. See our Privacy Policy.

The Send Invites modal additionally requires the planner to confirm consent at send time:

By enabling SMS, you confirm each selected guest has agreed to receive event-related text messages from you via Cenvi. Each message includes a STOP-to-opt-out footer. Msg & data rates may apply.

6. Screenshots

Screenshots of each opt-in surface as rendered live on cenvi.events. Each registration image shows the phone-capture field with its explicit, unchecked Cenvi-branded SMS-consent checkbox visible.

Planner registration form with an unchecked SMS consent checkbox beneath the phone field — Planner email/password registration — `https://cenvi.events/signup`

Vendor registration form with an unchecked SMS consent checkbox beneath the phone field — Vendor email/password registration — `https://cenvi.events/signup`

Vendor registration modal on a ticketing event page with an unchecked SMS consent checkbox beneath the phone field — Vendor registration on a ticketing event page — `https://cenvi.events/ticketing/register/{registrationUrl}`

Public ticket registration form showing the phone field with its inline transactional SMS disclosure — Public ticket registration (contact details & phone field) — `https://cenvi.events/ticketing/register/{registrationUrl}`

Public ticket registration Communication Preferences section with an unchecked required SMS consent checkbox and a separate unchecked optional marketing checkbox — Public ticket registration (Communication Preferences) — required transactional SMS checkbox and separate optional marketing checkbox, both unchecked by default

Public RSVP form with SMS consent disclosure beneath the phone field — Public RSVP form — `https://cenvi.events/events/rsvp?public={token}`

Event guest list with third-party-consent disclosure beneath the phone field — Event guest list (planner-side; third-party consent attestation)

Send Invites modal showing the Also send SMS checkbox with a per-send third-party-consent disclosure beneath it — Send Invites modal — per-send third-party-consent disclosure

7. Message Frequency

Message frequency varies and depends on the categories of messages the recipient is eligible to receive and the recipient's activity on Cenvi. Typical ranges:

Account & authentication: 1–3 messages per signup/re-verification event.
Transactional vendor notifications: 0–10 per month depending on booking activity.
Event invitations & RSVP: 1–3 per event the recipient is invited to.
Ticketing: 1–5 per ticket purchase across confirmation, reminders, and event-day updates.

8. Cost

Message and data rates may apply, depending on the recipient's mobile carrier and plan. Cenvi does not charge recipients to receive SMS.

9. Opt-Out, Opt-In, and HELP

Cenvi honors all standard CTIA SMS keywords. Inbound replies are processed by a signature-validated Twilio webhook at POST /api/v1/twilio/sms/inbound, which writes opt-out events to a Postgres suppression table and returns the auto-reply TwiML messages shown below.

Opt-out keywords

STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT (case-insensitive). On receipt, the recipient's phone number is added to a global Cenvi suppression list. All future Cenvi SMS to that number are blocked across every campaign, every sender, and every Cenvi product.

Auto-reply sent:

Cenvi: You have been unsubscribed and will receive no further messages. Reply START to resubscribe. Support: support@cenvi.events

Opt-in / resubscribe keywords

START, UNSTOP, YES (case-insensitive). On receipt, the recipient's phone is removed from the suppression list, restoring delivery of SMS for which they have an existing relationship with Cenvi.

Auto-reply sent:

Cenvi: You have been resubscribed and will receive messages again. Reply STOP to opt out. Msg & data rates may apply.

HELP keywords

HELP, INFO (case-insensitive). Auto-reply sent:

Cenvi: Plan and book your event at cenvi.events. For support contact support@cenvi.events. Reply STOP to opt out. Msg frequency varies. Msg & data rates may apply.

10. Privacy

The full Mobile Messaging (SMS) Program section of our Privacy Policy describes how Cenvi handles mobile phone numbers, SMS opt-in status, message metadata, and subprocessor relationships. The Privacy Policy contains the following verbatim statement:

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Mobile phone numbers, SMS opt-in status, and SMS consent are not sold, rented, transferred, or shared with any third party for their own marketing or promotional purposes. We share mobile information only with subprocessors (such as Twilio) strictly to operate the Cenvi SMS messaging program and to comply with applicable law, and those subprocessors are contractually prohibited from using your mobile information for their own marketing.

11. Technical Compliance

Sender: Twilio long code provisioned to Cenvi (Bookify Events Inc.).
Compliance footer: "Reply STOP to opt out. Reply HELP for help. Msg & data rates may apply." is auto-appended to every outbound SMS by smsBodyWithComplianceFooter(); the function caps total message length at 1600 runes including the footer.
Suppression check: Every outbound SMS calls IsPhoneSmsSuppressed() against the message_suppressions Postgres table (contact_type = phone_sms) before sending. Suppressed numbers receive nothing.
Webhook signature validation: The inbound webhook validates Twilio's X-Twilio-Signature header before processing any STOP/HELP/START reply, preventing spoofed opt-out events.
Phone normalization: All phone numbers are canonicalized to E.164 before storage or comparison.
Non-production gating: Outbound SMS is disabled by default in staging and development environments via a TwilioSMSAllowed() guard to prevent accidental sends to real users during testing.
Geographic scope: US and Canada (E.164 enforced; +1 default for 10-digit input).
No third-party sharing of mobile information for marketing. See the verbatim privacy statement above.

12. Support

Questions about the Cenvi SMS program, opt-out, or A2P 10DLC compliance can be sent to support@cenvi.events.

Mailing address:
Bookify Events Inc.
Attn: SMS Compliance
1870 The Exchange SE Ste 220 PMB 505546
Atlanta, Georgia 30339
United States