Next step · What to do next

Send notifications to customers or staff (email, SMS, push)

What you may see

I want to alert my team about new orders and tell customers about status

Why this step

Notifications are useful when few, timely and wanted; each channel has a cost, a consent rule and failure modes you must plan for.

Before you start

Who needs which alert, how fast, and what is the monthly budget?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Send notifications to customers or staff (email, SMS, push)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Notifications are useful when few, timely and wanted; each channel has a cost, a consent rule and failure modes you must plan for.

DO THESE STEPS, IN THIS ORDER
1. List the events and for each choose the cheapest channel that works (email for most, a staff chat or push for urgent), explaining costs without quoting prices I must check.
2. Send from the server after the event is saved; queue and retry on failure; never block the main action; log every send with its result.
3. Ask for permission for customer messages, let people choose or stop, and cap the number per day and a total spending limit.
4. Test on real phones, including quiet hours and Arabic text.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A test event notifies the right people once, in the right language, and stops at the daily cap.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not send marketing messages without consent.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

List the events and for each choose the cheapest channel that works (email for most, a staff chat or push for urgent), explaining costs without quoting prices I must check.
Send from the server after the event is saved; queue and retry on failure; never block the main action; log every send with its result.
Ask for permission for customer messages, let people choose or stop, and cap the number per day and a total spending limit.
Test on real phones, including quiet hours and Arabic text.

Do not do this

Do not let a loop send thousands of messages.
Do not send marketing messages without consent.

Try another entry