Investigate missing email
The proposed view would help staff check a confirmed subscriber’s relevant subscription state.
Integrations MailerLite
MailerLitePlanned
MailerLite context without surprise subscriptions.
Plan a MailerLite connector for selected subscriber context, helping support understand email issues while preserving consent.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Email marketing
What we’re planning to connect.
- 01MailerLite
- 02Planned connection
- 03Message support
Explain group membership
Selected group context can help diagnose which communication the customer expected to receive.
Keep consent unchanged
Reading subscriber context must never silently subscribe a customer or override an unsubscribe.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Confirmed subscriber
Selected groups
Subscription state
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Decide which subscriber fields help resolve support requests and exclude unrelated marketing data.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Use an unsubscribed test contact and verify a support lookup leaves that choice unchanged.
Before you connect
MailerLite integration questions
Can I connect MailerLite to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Use an unsubscribed test contact and verify a support lookup leaves that choice unchanged.