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.

How is a personalised campaign priced?

Per recipient, after their own details are merged in. A longer name can push one recipient's message from one page to two, so the dashboard renders every row, counts its pages and shows the exact total in naira before you send. An average would over-charge some recipients and under-reserve for others.

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.

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.

Can I send SMS in Hausa, Igbo or Yoruba?

Yes. Those languages send correctly as Unicode. Because their orthographies use characters outside the GSM-7 alphabet, the SMS standard carries 70 characters per segment rather than 160, so plan message length accordingly.

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.

Live

Personalized SMS

One campaign, a message written for each person in it

Upload a CSV, write the message once with [firstName], [lastName] or [fullName], and every recipient receives their own rendered copy. Each row is validated, rendered and priced separately, so the total you approve is the total you pay.

Start free See pricing

Dashboard workflow

Personalized composer

Channels

SMS

Transactional alerts and campaigns

Message body

1 SMS page each

Hi [firstName], your Northstar plan renews on Friday. Reply STOP to opt out.

Recipients

1,250 contacts

Estimated cost

₦17,500

Schedule

Rendered per recipient

Product capabilities

What this channel handles

Three placeholders, and only three

[firstName], [lastName] and [fullName], which is derived from the two name columns. Anything else is refused before the campaign is priced, because a message that goes out reading "Dear [name]" is worse than one that never left.

Your spreadsheet's own headers

Phone_Number, phone_number, first name, firstName, first_name, last name, lastName and last_name are all read as what they are. Download the template if you would rather start from ours.

Priced per recipient, not per campaign

A longer name can push one recipient's message from one page to two. Every row is rendered and counted on its own, so nobody subsidises anybody, and the wallet reserves the real amount.

Every bad row named by its line number

Invalid numbers, duplicates and opted-out recipients are reported by CSV row before anything is charged, rather than discovered afterwards in a delivery report.

See it as your customer will

The rendered preview shows real rows with real values merged in, along with the page count and cost of each. What you read is what is sent.

A promotional workflow

Personalized SMS is promotional traffic: it uses a promotional Sender ID and the 08:30 to 19:30 WAT delivery window, like every other campaign.

How delivery works

Personalized SMS is promotional traffic. It uses a Sender ID approved on the promotional route, is delivered between 08:30 and 19:30 WAT, and is filtered against the Do Not Disturb register like any other campaign. Each recipient's rendered message is stored with their delivery record, so a report shows what that person actually received.

Use cases

Where Personalized SMS fits

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

Offers addressed to the customer

The same promotion, opening with the recipient's own first name rather than "Dear customer".

For stores and retailers

Renewals and fee notices

A reminder that names the person it is for, sent from one file to a whole list.

For schools and public services

Member and donor care

Thank-yous and follow-ups that read as though they were written one at a time.

For religious organisations and NGOs

Greetings on the day

When the message should arrive on each person's own date rather than all at once, the birthday schedule handles it.

See the Birthday SMS Schedule

Pricing note

Personalized SMS is ₦7.00 per page, priced after each recipient's message is rendered. No setup fee, no monthly minimum and no contract See SMS pricing.

Download the CSV template

Write with placeholders

Check rows, pages and cost

Send the campaign

Where this runs

Personalized SMS is a Console workflow, at Send, Personalized SMS. Download the CSV template on the page, upload your file, and the Console validates, renders and prices it before anything is reserved.

See Promotional SMS