Levy Engage Overview

Levy Engage turns your Levy Fleets dashboard into a complete marketing system. Instead of exporting rider lists to Mailchimp or Klaviyo every week, you build segments against your live fleet data, send email, SMS, and push messages, and run multi-step journeys that react to ride events as they happen.

What Engage Includes

Engage ships with five connected surfaces:

Why It Beats Bolting On a CRM

Most micromobility operators end up paying $200-$500/month for Mailchimp, Klaviyo, or Twilio plus the time to keep rider lists in sync. Engage avoids that because:

• The data is already here. Ride frequency, last-ride date, wallet balance, subscription status, violations, rider score, language, city - all live attributes in your dashboard.
• No CSV sync. Segments evaluate against the database directly. There is no stale list.
• One unsubscribe. Riders manage every channel from a single preference center, so you stay compliant without juggling lists.
• Per-rider language. The pipeline picks the template variant matching customers.language and falls back to English automatically.

Channels Supported

The dispatcher handles provider routing, retries, bounce processing, and suppression list updates. You do not manage any of that yourself.

Pre-Built Templates

Engage seeds 19 Levy Recommended templates covering every common lifecycle moment:

• Welcome series (3 emails over 7 days)
• First ride congrats (push + email)
• Re-engagement 30 / 60 / 90 days lapsed
• Low balance warning (push + email when wallet drops below threshold)
• Promo code blast
• Post-violation educational nudge
• Subscription renewal offer
• Score-tier-up congrats
• Force-end apology with automatic $1 wallet credit
• Birthday / anniversary

You can clone any of these into your own library, edit the copy, and ship it the same hour. See Pre-Built Templates for the full inventory.

How a Message Gets Sent

Every send follows the same pipeline:

1. Audience compiled. Engage compiles your segment definition into safe SQL and runs it through the engage_run_segment_sql RPC.
2. Suppression checked. Each recipient is filtered against the per-subaccount and global suppression list.
3. Rate limit applied. Defaults: 1000 emails / 5 min, 100 SMS / min, 5000 push / min, configurable per subaccount.
4. Variables resolved. {{customer.first_name}}, {{wallet.balance | currency}}, and similar tokens are filled at send time, not at compose time, so the data is always fresh.
5. Provider call made. Postmark, Telnyx, or Expo accepts the send and returns a message ID.
6. Engagement tracked. Delivery, open, click, bounce, complaint, and unsubscribe events flow back through webhooks into engagement_events.

The dispatcher is idempotent on campaign_sends.idempotency_key, so retrying a send never produces duplicates.

Compliance Built In

Engage was built for TCPA, CAN-SPAM, GDPR, and CASL from day one. You do not bolt compliance on later - the framework enforces it at queue time and at dispatch time:

• TCPA - SMS quiet hours enforced 9 PM to 9 AM recipient-local; inbound STOP keywords add a global suppression instantly.
• CAN-SPAM - every pre-built email payload includes the legal address and unsubscribe link; the dispatcher sets List-Unsubscribe and List-Unsubscribe-Post headers.
• GDPR - one-click unsubscribe writes to subscription_preferences, suppression_list, and the immutable engage_compliance_audit_log. Right-to-be-forgotten cascades through every Engage table.
• CASL - opt-in method recorded on every subscription_preferences row (single / double / imported / transactional_inferred).

See Compliance: TCPA, CAN-SPAM, GDPR, CASL for the full breakdown.

Where to Start

1. Read Getting Started to set up sender identity and seed the Levy Recommended templates.
2. Build your first segment - "active in the last 30 days" is a good warmup. See Audience Segments.
3. Send a one-time campaign to that segment. See Campaign Builder.
4. Turn on the Welcome Series journey for new signups. See Journey Builder.
5. Add an A/B test to your next blast. See A/B Testing.

---