Luma
Log in
ProductCase StudiesPricingDevelopersBlogContactLog in

Four businesses. Four problems. One platform.

See how a boutique, a pharmacy, a school and a lender put Luma's features to work.

Luma is early, so these are illustrative scenarios showing how each business would use the product — not published customer accounts yet.
Adire & Co
Lagos, Nigeria
Retail & fashion
12 min
to first campaign sent
94%
delivery rate
3
languages used
The challenge

Adire & Co runs two boutique stores in Lekki and a 4,000-contact WhatsApp broadcast list built up over three years. Every new-stock announcement took hours to write, and close to half the list never saw it — messages went out in English only, in a customer base where plenty of shoppers read Yoruba or Pidgin more comfortably.

How they used Luma
Used the AI Message Studio to turn "new Ankara restock, 10% off this week" into three ready variants in under six seconds
Generated the same campaign in Yoruba and Pidgin for customers who preferred it, without hiring a translator
Let Channel Cascade retry on SMS for the roughly 30% of the list without WhatsApp open
The result

The first campaign went out 12 minutes after signup. Delivery settled at 94% across three sends, and the Yoruba variant outperformed the English one on click-through among Lekki-based customers.

Ilé-Ntọ́ Pharmacy
Ibadan, Nigeria
Pharmacy & healthcare
1,240
DND contacts auto-excluded
₦0
spent on messages that never sent
24–48h
sender ID approval
The challenge

Ilé-Ntọ́ Pharmacy wanted to send refill reminders and restock alerts to a 5,000-contact list built from till receipts, but the owner had read enough about NCC fines to be nervous about sending anything without knowing who was on the Do-Not-Disturb list — and a previous bulk-SMS reseller had taken payment for messages that silently failed to deliver.

How they used Luma
Registered a Corporate Bind sender ID through the guided flow and tracked approval status without calling anyone
Used the DND-aware audience preview to see exactly which contacts would be excluded before paying for the send
Relied on Luma's automatic refund for messages that failed to leave the platform, instead of trusting a promise
The result

Every campaign now shows its DND exclusions before send. 1,240 contacts are automatically excluded from promotional sends without the pharmacy lifting a finger, and refunds for failed sends land back in the wallet within 24 hours.

Greenfield Montessori
Abuja, Nigeria
Education
97%
fee-reminder delivery after cascade
41%
of parents reached on WhatsApp alone
2
languages, English and Hausa
The challenge

Greenfield Montessori sends fee reminders and event notices to around 600 parents each term. WhatsApp-only broadcasts missed the parents who'd changed numbers or never installed it; SMS-only was reliable but cost more than the school wanted to spend reaching parents WhatsApp could have carried for free.

How they used Luma
Turned on Channel Cascade so WhatsApp goes out first and SMS only follows for parents who don't open it within the wait window
Used Campaign Autopsy after the first term's fee reminder to see which delivery window worked best, and adjusted the next send time
Sent the event calendar in Hausa to the parent segment who'd asked for it, generated from the same English brief
The result

Delivery across the cascade reached 97%, with 41% of parents reached on the cheaper WhatsApp leg alone. The autopsy's resend recommendation raised the second term's read rate by double digits.

Kolo Finance
Lagos, Nigeria
Fintech & lending
30 min
from docs to first live OTP
100/s
requests sustained on send endpoints
0
duplicate charges since switching on
The challenge

Kolo Finance's lending app needed OTPs, disbursement alerts and repayment reminders sent the moment an event happened in their backend, with delivery receipts they could actually observe — and a bad experience with a previous provider's silent retries had once double-charged a customer's disbursement alert.

How they used Luma
Read the API reference and sent a live OTP inside 30 minutes, using the same live/test key pattern for staging and production
Added idempotency keys to every send call so a network retry from their queue never double-sends
Subscribed to delivery webhooks instead of polling, and used the AI generation endpoint to draft repayment-reminder copy their compliance team locked as a template
The result

Kolo Finance now runs disbursement alerts and repayment reminders entirely through the API, sustaining bursts against the 100 requests/second send limit with zero duplicate charges since switching on idempotency keys.

Yours could be next.

Free to sign up. Pay only for what you send.