How many messages does your team send by hand every day? "Your appointment is confirmed." "Reminder: your booking is tomorrow." "Your order has shipped." "We received your documents." "Your payment is due." Each one takes a minute, and together they take hours. Some get forgotten, and customers call to ask.
Automated notifications send the right message at the right moment, every time.
I'm Aldrian, an independent developer. I set up automatic emails, SMS and chat notifications for websites, stores, booking systems and web apps.
Notifications I can automate
For customers
- Booking and appointment confirmations
- Reminders the day before or a few hours before
- Order confirmations, shipping updates and delivery notices
- Payment receipts and due date reminders
- Application or request status changes
- Document requests and missing requirement reminders
- Welcome emails for new accounts and members
- Follow-ups asking for feedback or reviews
- Renewal and expiry reminders
For your team
- New lead, booking or order alerts
- Requests waiting too long without a reply
- Low stock or failed payment alerts
- Daily or weekly summaries
- Website down or error alerts
Email, SMS or chat?
Best for detailed messages, receipts, documents and anything people may want to keep. Low cost per message.
SMS
Best for short, time-sensitive messages like reminders, verification codes and urgent updates. Many people in the Philippines read SMS faster than email. Costs per message vary by provider.
Chat apps
Some businesses prefer messaging channels like Viber, WhatsApp or Messenger. These require approved business accounts and follow each platform's rules, so I'll check what's practical for your business.
Often the best setup combines them: email for the full details, SMS for the reminder.
Doing it reliably
Sent from your domain
Emails come from an address on your own domain, through a reliable transactional email service, with SPF, DKIM and DMARC set up so they reach the inbox. More on form and email fixes.
Triggered by real events
Notifications fire when something actually happens in your system, like a booking created or a status changed, not when someone remembers to send them.
Scheduled properly
Reminders are scheduled from the appointment time, with time zones handled correctly, and cancelled automatically if the booking is cancelled.
Never sent twice
Systems are built so the same event doesn't trigger duplicate messages.
Logged
Every message is recorded with its status, so you can check whether a customer was notified.
With opt-outs
Marketing-style messages include an opt-out. Essential service messages, like receipts, are kept separate.
Real-time where it matters
For apps that need instant updates on screen, I build real-time features too. My Ghostly chat app uses WebSockets on Cloudflare Durable Objects for messages, typing indicators and presence, updating instantly for everyone in the room.
Messages people actually read
- Short subject lines and first lines that say what it's about
- The key detail first: date, time, order number or amount
- One clear action, like "Reschedule" or "Track your order"
- Your branding, kept simple so it looks good on phones
- Plain language, in the language your customers prefer
Providers I can work with
Transactional email services such as Brevo, Postmark, Mailgun, Amazon SES and Resend. SMS providers and gateways that cover your customers' countries, including options that work well in the Philippines. I'll compare costs and reliability with you, and API keys are always stored securely.
Adding notifications to what you have
You don't need a new system. I can add notifications to:
- WordPress and WooCommerce sites
- Shopify stores, through apps or integrations
- Existing booking tools, through their APIs or webhooks
- Custom web apps and portals
- Spreadsheets and forms, for simpler setups
More on API integration.
Common mistakes
Sending from the visitor's address or a free email account. Hurts deliverability.
Reminders that don't cancel. Reminding someone about an appointment they cancelled looks careless.
Too many messages. Every notification should be useful. Cut the rest.
No logs. When a customer says they never got it, you need to check.
Hard-coded API keys. Keys belong in secure settings, not in code.
Templates your team can edit
Message wording changes over time: new policies, new promos, a friendlier tone. I set up notification templates so your team can edit the text of common messages without touching code, with placeholders for details like names, dates and order numbers. Changes are previewed before they go live, so nothing goes out broken.
Start with the messages that cost the most time
You don't need to automate everything at once. Start with the two or three messages your team sends most often, usually confirmations and reminders. Once those run on their own, the time saved makes it easy to see which messages to automate next.
What it usually costs
A handful of email notifications on an existing site is a small project. Full systems with SMS, scheduling, logs and many event types take more work. SMS sending costs are separate and paid directly to your provider. You'll get a fixed quote after we talk.
How we'd work
- We list the messages your team sends by hand.
- I map each one to the event that should trigger it.
- You get a quote with timeline and fixed price.
- I build and test with real scenarios.
- We review wording and timing together.
- We launch, and I monitor delivery in the first weeks.
Let's automate the repetitive messages
Tell me which messages your team sends most often. I'll reply with a plan and a fixed quote.
