GSM-7
Standard Latin characters. Up to 160 characters per segment. Concatenated long messages bill additional units.

Bulk SMS
Reach customers on MTN, Telecel, and AT from one prepaid GHS wallet. Upload CSV contacts, build lists in the dashboard, snapshot your audience when a campaign starts, and inspect delivery by message id — not a dashboard guess.
Campaigns
The console is for operators who send regularly, not only developers wiring an API. A campaign stays a draft until you confirm. The list is snapshotted then, and the estimate uses live pricing.
Example draft
Weekend notice
Bulk queue, separate from OTP
01
Draft
Name, sender ID, and category. Nothing sends yet.
02
Snapshot
Later list edits do not change a campaign already in flight.
03
Estimate
Units and cost come from the pricing rules before you confirm.
04
Confirm
Dispatch uses the bulk queue. Cancel does not recall messages already submitted.
Open campaigns when you are signed in.
Pricing
Standard Latin characters. Up to 160 characters per segment. Concatenated long messages bill additional units.
Twi, emoji, or special symbols switch encoding. Up to 70 characters per segment. Use our character counter before you send.
Reserve funds before dispatch. Estimate segments with the cost calculator.
Use cases
Common patterns, not customer case studies. A school, a shop, and a clinic all send on the same prepaid path.
Schools and universities
Fee reminders, exam timetables, and PTA notices to parents. Upload a list, snapshot it at send time, and keep a delivery report per message id.
Churches and mosques
Service times, offering drives, and event reminders. An approved sender ID shows your organisation name instead of a random number.
E-commerce and retail
Order updates, pickup codes, and promo blasts to opted-in shoppers. Estimate units and cost before you confirm a campaign.
Fintech and payments
Transaction alerts and account notices. Bulk traffic uses a separate queue from OTP so login codes are not starved during a large send.
Healthcare and clinics
Appointment reminders and lab-ready alerts. Unicode bodies are supported — encoding is computed before a pesewa moves.
Logistics and delivery
Dispatch updates and driver PINs. Ghana numbers route to MTN, Telecel, or AT by prefix from the same prepaid wallet.
NGOs and associations
Field-staff alerts and member notices. Lists are snapshotted when a campaign starts — later contact edits do not rewrite queued messages.
Sender ID
LIVE bulk SMS needs an approved alphanumeric name, 3 to 11 characters. The networks review it through Taysend. The route is chosen from the number prefix. We do not claim inbox placement rates.
Sender ID registration →On the handset
ACMEGH
3–11 characters. LIVE waits until the name is approved.
Prefix picks MTN, Telecel, or AT.
Explore
Each page answers a different question. They are not copies of this one.
FAQ
If something here is product behaviour, it matches the dashboard and the API.
Bulk campaigns snapshot a list, estimate cost, reserve wallet funds, and dispatch on the bulk queue. OTP uses POST /v1/verify/send and a dedicated queue with hashed codes, cooldown, and attempt limits. Both share inspectable delivery reports.
When you start a campaign, the recipient list is frozen. If someone adds or removes a number later, messages already queued keep the original audience.
LIVE bulk traffic requires an approved alphanumeric sender ID (3–11 characters). TEST keys use simulated numbers and the sandbox sender TAYSEND.
GSM-7 allows up to 160 characters per segment; UCS-2 (Unicode) uses 70 characters per segment. Long messages use multiple units.
Yes. POST /v1/messages accepts a recipients array for bulk sends, or use the dashboard campaigns console. The same pipeline handles encoding, wallet reservation, and delivery reports.
Get started
API base: https://api.taysend.com · Docs at /developers