Do birthday messages repeat every year?

Yes. Each row in the schedule keeps its own birthday and its own delivery time, and it runs again on that date every year until you pause it. A 29 February birthday is delivered on 28 February in a non-leap year rather than skipped for three years at a time.

Can every birthday recipient have a different delivery time?

Yes, and that is the point of the schedule file: each row carries its own WAT time. One global send time would discard the per-recipient scheduling the CSV exists to express. Times outside the promotional window are reported by row number when you upload, rather than quietly moved.

When can promotional SMS be delivered?

Between 08:30 and 19:30 WAT. That window is enforced on the server, not only in the dashboard: a promotional send composed at 21:00 becomes a visible scheduled send for the next morning rather than arriving at an hour your customers did not agree to. Transactional and OTP messages are not subject to it.

Which placeholders can I use in a personalised SMS?

Exactly three: [firstName], [lastName] and [fullName], which is built from the two name columns. A birthday schedule uses [firstName] and [signature]. Anything else is rejected before the campaign is priced, because a message that goes out reading "Dear [name]" is worse than one that is refused.

Can one sender ID be used for both promotional and transactional SMS?

No. The networks approve a sender ID for one route, against the sample message in that request letter, so promotional and transactional traffic need separate requests, separate letters and separate approvals. Sendozi enforces it: a transactional request naming a promotional sender ID is refused before your wallet is touched, and the reverse is refused too.

Can I upload my existing contact list?

Yes. Import a CSV, map the columns once, and the list is ready for campaigns and personalisation. Normalise numbers to +234 format first - local 0-prefixed numbers are rejected. You are responsible for having consent to message the people on the list.

Live

Birthday SMS Schedule

Remember every customer's birthday, once

Upload one file of names, numbers, dates and times. Each row runs on its own birthday, at its own WAT time, every year, until you pause it. Nothing to diarise and nothing to re-upload next January.

Start free See pricing

Dashboard workflow

Birthday schedule

Channels

SMS

Transactional alerts and campaigns

Message body

1 SMS page each

Happy birthday, [firstName]! Enjoy 15% off this week. [signature]

Recipients

1,250 contacts

Estimated cost

₦17,500

Schedule

Each recipient's own date

Product capabilities

What this channel handles

One file, a schedule per person

Every row carries its own date and its own delivery time. There is no single campaign send time, because a shared one would throw away the per-recipient scheduling the file exists to express.

It recurs on its own

A saved schedule runs again every year. A worker claims each due birthday once a minute and hands it to the same delivery queue as any other SMS, so two overlapping runs cannot send the same greeting twice.

29 February is handled

A leap-day birthday is delivered on 28 February in a non-leap year, rather than skipped for three years at a time.

Re-checked on the day, not on upload

A year passes between occurrences. Sender ID, wallet balance, opt-outs, delivery window and production access are all checked again at the moment each birthday runs, and a row that cannot go is reported rather than dropped.

Personal without being generic

[firstName] and [signature] come from that recipient's own row, so one file can greet different customers and sign off from different branches.

Times validated before activation

Promotional delivery runs 08:30 to 19:30 WAT. A row outside it is named by its line number when you upload, rather than quietly moved to a time you did not choose.

How delivery works

Birthday messages are promotional traffic. They use a Sender ID approved on the promotional route, run between 08:30 and 19:30 WAT, and are filtered against the Do Not Disturb register like any other campaign. Each occurrence appears in Messages and Reports as a real send, with its own cost and delivery state; a future birthday never counts towards a sent or spend total.

Use cases

Where Birthday SMS Schedule fits

Each use case maps to a concrete workflow, report or next channel.

Customer birthdays

A greeting, and an offer if you want one, arriving on the day rather than in a monthly batch.

For stores and retailers For SMEs

Member and congregation milestones

Birthdays across a membership list, signed off by the branch or group that keeps it.

For religious organisations and NGOs

Student and staff dates

One roll uploaded once, greeting each person on their own date for as long as they are on it.

For schools and public services

Client relationships

For a practice or a professional service, the follow-up that keeps a client relationship warm without a reminder in your own calendar.

For professionals

Pricing note

Each birthday message is ₦7.00 per page, charged on the day it sends rather than when you upload the schedule. No setup fee, no monthly minimum and no contract See SMS pricing.

Download the schedule template

Write the greeting

Check rows and times

Activate and leave it running

Where this runs

The Birthday SMS Schedule is a Console workflow, at Send, Birthday SMS Schedule. The page also shows the birthdays coming up, any rows that could not queue, and the greetings recently delivered.

See Personalized SMS