Send useful customer notifications and reminders
Keep customers informed automatically without sending duplicates, wrong-time reminders or unwanted marketing.
When to use this
When customers need a confirmation, a reminder before an appointment or deadline, and an update if something changes.
Before you start
- A working booking, order, task or membership flow with a real date, status and customer contact field.
- A connected provider for the chosen channel. Use the email-service prompt first if email is not ready.
- Your reminder timing, cancellation rules and customer time-zone policy.
- Your test email address or phone number and permission to receive tests. SMS and some messaging channels charge per message.
The prompt
This app already stores [BOOKINGS / ORDERS / TASKS / MEMBERSHIPS]. Add a small customer notification system using [EMAIL / SMS TEXT MESSAGE / IN-APP MESSAGE]. The sending service for that channel is [CONNECTED SERVICE]. If it is not connected, stop and tell me what I need to set up before building the messages. The outcome is three useful messages only: send a confirmation when [EVENT] is successfully saved, send a reminder [TIME BEFORE] before [APPOINTMENT OR DEADLINE], and send a change or cancellation notice when [RELEVANT DETAILS] change. Use the customer's saved time zone so the reminder arrives at a sensible local time. Cancel any old scheduled reminder when the booking, deadline or status changes, then schedule the correct one. Never send a reminder for something already cancelled, completed or refunded. Let me edit the subject and wording from an admin-only screen. Use these details where relevant: [CUSTOMER NAME], [SERVICE OR ITEM], [DATE AND TIME], [LOCATION OR LINK], [HOW TO CHANGE OR CANCEL]. Do not include sensitive private details in a lock-screen notification or subject line. Prevent duplicate sends and keep a simple history showing what was scheduled, sent, skipped or failed. Operational messages must stay separate from promotions. For any optional message, respect the customer's communication preference and provide the required way to opt out. The tone should feel [CALM AND REASSURING / FRIENDLY AND CONCISE]. Send all three test messages to [MY TEST ADDRESS OR NUMBER] using a test booking, then tell me what to check before enabling them for customers.
Already building? Paste this into your project. Starting fresh? Open a free account with a compatible builder below.
Build it on
What this creates
- Confirmation, reminder and change-or-cancellation messages
- Scheduling that updates when the underlying item changes
- Editable message wording in an admin-only area
- Customer communication preferences and opt-out handling where required
- A send history with duplicate protection and visible failures
Check it worked
Paste the prompt, wait for the build to finish, then confirm these — in plain language, no technical checks needed:
- Creating a test item sends one confirmation to your own address or number
- Moving the test date removes the old reminder and schedules the new one
- Cancelling the test item prevents its reminder and sends the correct cancellation message
- The displayed date and time match the recipient's selected time zone
- You can edit the wording without changing code, and a normal customer cannot open that editor
Something missing? That's normal — ask for it in one short follow-up message rather than re-running the whole prompt.
Next steps
Let customers choose their reminders
When different customers want different timing
Add communication preferences to the customer profile. Let each person choose [ALLOWED CHANNELS] and select a reminder time from [ALLOWED OPTIONS]. Use a safe default for people who do not choose. Do not let them turn off messages that are strictly necessary for account security, but keep those separate from marketing.
You'll know it worked when: A test customer can change preferences and the next reminder follows that choice.
Send the owner a daily digest
If individual owner alerts are becoming noisy
Add one daily owner summary at [LOCAL TIME AND TIME ZONE] listing tomorrow's [BOOKINGS / DEADLINES / ORDERS] and any notification failures from the previous day. Send nothing if there is nothing to report. Keep customer details to the minimum I need to act.
You'll know it worked when: You receive one readable test digest, not a separate owner alert for every item.
Add a final no-response follow-up
When customers must confirm attendance or complete a step
If a customer has not [CONFIRMED / COMPLETED THE REQUIRED STEP] by [TIME BEFORE DEADLINE], send one final follow-up explaining exactly what they need to do and linking to [PAGE OR ACTION]. Stop immediately if they complete the action, and never send more than one final follow-up.
You'll know it worked when: The test message sends once for an unfinished item and is skipped after the action is completed.
Watch out for
- Wrong-time reminders damage trust. Storing a time without the customer's time zone can move it by hours. Save the time zone with the booking and display it in every confirmation.
- Changes can leave old reminders behind. Rescheduling must cancel the previous scheduled message before creating a new one, or the customer may receive both.
- Every channel can cost money. Email, SMS and messaging providers have their own plans, limits and overage rules. Add an owner-visible send history and review usage before a large event.
- Operational permission is not marketing consent. A booking reminder does not give permission to send promotions. Keep those flows separate and honor opt-outs.
- A sent status is not the same as read or delivered. Providers can accept a message that is later blocked. Do not promise that every notification reached the person.
Platform notes
Base44 can trigger messages when stored information changes and can run actions on a schedule; its built-in email reaches registered users, while outside recipients or other channels need a suitable provider. Lovable Cloud can run scheduled jobs and private Edge Function logic; the chosen email, SMS or messaging channel may still need an external provider with separate charges. v0 uses a channel provider plus a scheduled private action on Vercel or another service. On every platform, confirm the schedule and delivery path after publication rather than only in preview.
Spend fewer credits
Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.
- Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
- Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
- Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
- One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
- Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
- Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.
The prompts on this page are written to do most of this work for you — that's the point of them.
Read the full guideRelated playbooks
Related prompts
Last reviewed: 2026-08-27