Campaign SMS your customers agreed to receive

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.

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.

The most common cause is the Do Not Disturb register: the networks block promotional traffic to DND-active numbers, and no provider can override that. Transactional messages travel a separate corporate route and are not filtered as marketing. Other common causes are an unapproved sender ID, a number that is not in valid +234 format, and a handset that was unreachable until the message expired. The delivery report names which applied.

You can build and test in sandbox immediately. A production send with an unapproved sender is refused rather than delivered under another name. Alphanumeric sender IDs must be registered per network, we handle the submissions, and the dashboard shows the status of each.

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.

No. An alphanumeric sender ID is one-way, and Sendozi does not receive inbound SMS, so a reply - including a STOP reply - is not captured. Put a contact route in the message for anyone who needs to respond or opt out, and record opt-outs on your suppression list.