Customer broadcasts versus order and booking confirmations
Use a subscriber broadcast for shared news people chose to receive. Use order or booking records for individual acceptance, payment, readiness, transfers, and private details. An interest topic is not a record of a purchase.
Identify what makes someone an intended recipient
For a bread-run announcement, interest in bread updates is enough. For ‘your order is ready,’ the recipient must have an actual confirmed order. That difference determines the contact route before you write the message.
KeepMPosted message types match customers' chosen content interests. They do not synchronize a till, attendance list, stock reservation, or payment record. A topic called ‘Order reminders’ does not automatically identify this week's buyers.
Before you send
- Ask whether the notice is a shared fact or an individual commitment.
- Use actual order or attendee records for exact affected customers.
- Keep names, balances, references, and personal arrangements private.
- Label any broad pickup notice ‘for customers with confirmed orders’ rather than assuming every subscriber bought.
Message examples to adapt
These are original examples. Replace bracketed details and check every promise before using them.
Shared broadcast
Subject: [Business] [date] collection arrangements
For customers with confirmed [run] orders, collection uses [window and location]. This is a general arrangement notice, not confirmation of a new order. Your individual record is handled through [order route]. Questions about that record: [contact].
Private confirmation
Subject: Your [Business] order [reference] is confirmed
Order [reference] is confirmed under [verified terms], with [specific collection arrangement]. [Private order details as appropriate]. Please use [contact] for changes. General future announcements are a separate optional subscription at [signup URL].
Use both routes when a shared change affects buyers
A moved pickup site can need a broad public update and private contact to actual buyers. The broad notice helps other interested customers; the private process ensures the exact commitment is handled.
Maintain each record in its own system. Delivery status and email opens do not prove order readiness, acceptance, attendance, or collection.
Common questions
Can I use topics as arbitrary tags for people?
Topics reflect customer-selected content preferences. Do not treat them as hidden purchase or attendance filters.
Is KeepMPosted a booking system?
No. It provides opt-in broadcasts by email and Telegram, with purchases and bookings handled through your own processes.
Put this into practice
Use KeepMPosted where the shared-news workflow fits, with order and attendee records retained for individual commitments.
KeepMPosted collects subscribers through a QR signup page and sends updates by email or Telegram using prepaid credits. Customers can choose the message types you offer. You write and send each update; SMS and scheduled sending are not available.