Operating thread
Move from stored consent to recipient history.
Audience rules, template, preview, configured sending, and the recipient record make customer outreach inspectable.
- 01
Audience
- 02
Template
- 03
Preview
- 04
Send
- 05
History
See the real product
See the customer context behind the audience.
Use genuine product captures to evaluate the operating record behind the claim.
Start with customer context and stored consent.
Build an email audience from all eligible customers, a configured tier, or recent activity. Pre-send counts and audience preview make the selected recipients visible before campaign creation. Stored consent filters are one input to the merchant's responsible-use procedure.
Prepare reusable email content.
Templates can use supported customer, business, and store merge fields. The merchant remains responsible for sender identity, content, stored consent, the opt-out procedure, provider rules, and merchant policy.
Treat send state as a configured operation.
A delivery attempt requires COMMS_SEND_ENABLED, a non-demo tenant, configured email delivery, sender setup, recipient data, stored consent filters, provider rules, and merchant policy. Availability is confirmed during rollout.
Retain campaign and recipient history.
Campaign state and recipient history provide an operating record of the configured attempt. They do not establish provider acceptance, inbox placement, open or click attribution, or a marketing-automation journey.
Configuration and responsibility boundary
Customer email campaigns are not Team Messaging.
Customer campaigns are an email-only merchant outreach workflow in LiftedPOS. Team Messaging is the separate authenticated workspace for employee channels, direct conversation, announcements, and shift handoff. Delivery still depends on sender setup, stored consent, the configured provider, recipient data, provider rules, merchant policy, and rollout.
Inspect it
Build a safe audience before configuring delivery.
Use the demo for product context, then confirm deployment-dependent behavior during a scoped rollout review.
- 01
Open Customers in a seeded store and inspect profiles, tiers, and recent activity.
- 02
Review how an all-eligible, tier, or recent-activity audience is selected through stored consent filters.
- 03
Inspect a reusable email template, supported merge fields, pre-send count, and audience preview.
- 04
During rollout, verify configured provider and sender setup, then inspect campaign and recipient history.
Workflow FAQ
Keep email outreach specific and permission-aware.
Which audiences can a customer email campaign use?
LiftedPOS supports all eligible customers, configured tiers, and recent-activity audiences, with stored consent filtering, a pre-send count, and audience preview.
Can a campaign use reusable email templates?
Yes. Templates can use supported customer, business, and store merge fields before campaign creation.
What is required before an email campaign can send?
Sending requires COMMS_SEND_ENABLED, a non-demo tenant, configured email delivery, sender setup, recipient data, stored consent filters, provider rules, merchant policy, and rollout verification.
Is customer outreach the same as Team Messaging?
No. Customer email campaigns are a merchant outreach workflow. Team Messaging is the separate authenticated workspace for employee channels, direct conversation, announcements, and shift handoff.
Public station terms
Know the price. Plan the way your team will use it.
Software is $100/month for the first station and $50/month for each additional station. A standard station is $499.99 to purchase or $39.99/month to lease. Cancel anytime with no long-term software contract. Leased equipment must be returned after cancellation or it is billed at the full purchase price. Payment terminals, processing, and separately scoped rollout work are separate from station pricing.