Send Tanzania SMS using the Sender IDs assigned to your business.
Every card is clickable.
These are sent-message counts. AutoSave Today / Yesterday cards count saved contacts instead.
Low-balance alerts use recent sending activity to estimate how long your SMS may last. Alerts are in-app; no owner SMS is sent by this feature.
Auto-learning foundation: the system studies your own delivery, balance and follow-up signals and recommends actions. It never changes settings or sends SMS automatically.
Choose a card and its contacts open directly below. Upload tools stay hidden until you need them.
New saved contacts appear here automatically without leaving or reopening this page. The live feed checks the client Contacts cache every 30 seconds while this page is active and does not rescan old AutoSave history.
| Phone | Saved name | Country | Source | Arrived |
|---|---|---|---|---|
| No live contacts loaded yet. | ||||
Choose which contacts you want to view. 10 contacts are shown per page.
| Phone | Name | Country | Source | Added | Status | SMS Sent | Last Sent | Details |
|---|
Hidden by default. Open only when manually importing a list.
All valid E.164 numbers are stored. Tanzania (+255) is tagged TZ and is SMS-eligible; every other valid country is stored as OTHERS and is not used for SMS.
Hidden until opened, keeping this page fast and light.
Today, Yesterday, This Month and All Time open saved contact details directly under their cards.
New contacts from your connected AutoSave devices appear here automatically. Tanzania (+255) contacts can receive SMS and automatic follow-up. Other valid contacts are stored safely.
No page refresh is needed. This business checks for newly routed AutoSave contacts every 30 seconds. The latest global AutoSave number can be different because each contact is routed to its matching business.
| Phone | Name | First added to client | Latest AutoSave sync | Source |
|---|---|---|---|---|
| Waiting for recent AutoSave arrivals… | ||||
Your connected AutoSave devices sync automatically. Choose ALL DEVICES or one source when you want to filter the view. The same phone number saved on multiple devices stays one contact.
Prepare AutoSave contacts saved this month for one exact send date. No SMS is sent until you review the message and create the campaign.
Contacts from all connected AutoSave devices are merged by phone number. The source device remains visible on each contact.
Maximum 160 characters. Emoji are blocked to keep one predictable SMS unit per recipient.
Nothing is sent while reviewing. Confirm the exact audience, SMS balance, cost, schedule and Follow-up rule before creating the campaign.
Create, import, preview and reuse SMS templates. Max 160 characters; no emoji.
Choose when new contacts receive the first message and later follow-ups. Sending limits, pause rules and owner summaries help protect your SMS balance.
Choose whether new AutoSave contacts are eligible for automatic Follow-up. Turning this source OFF does not delete contacts and does not change manual campaigns.
Your current rule appears first. EDIT loads a saved copy. STOP removes a rule from new use, RESUME restores it, and DELETE hides it safely. If the CURRENT rule is stopped or deleted, the newest available rule becomes CURRENT automatically. Existing locked campaigns keep their saved snapshot.
For campaign-led journeys, S0 is the campaign message. Provider-confirmed delivery moves to D1 immediately. If DLR is still waiting at 72 hours, it is counted as Delivered for reporting and enters D1. Provider-confirmed failed/expired recipients remain excluded.
Preview Today, Yesterday, This Week, This Month, All Time or a Custom range. Only eligible contacts that never entered Follow-up are added; existing, paused, suppressed or already-messaged contacts are left unchanged.
| Phone | Name | Saved Day | Source | Status |
|---|---|---|---|---|
| No preview yet. | ||||
Route the immediate D0 message by the name used when the number was saved. Example: AFYA can use one message/Sender ID, FURSA another. If no keyword matches, the Default First Message can cover everyone else.
Each active step must stay within 160 characters and contain no emoji. Import the approved D0-D100 bank from Excel/CSV, load it instantly, or edit a step manually.
These caps apply to Follow-up automation for each individual phone.
Contacts that repeatedly fail are paused automatically. They receive no next follow-up until you review and restart them.
| Phone | Failures | Status | Last Campaign | Action |
|---|---|---|---|---|
| No stopped contacts. | ||||
Optional: add a short greeting only when an already-due follow-up is sent on Friday, Saturday or Sunday. This does NOT create an extra weekend SMS.
Optional date-specific prefixes. They are added only to an already-due Follow-up message and never create an extra SMS. One rule per line: YYYY-MM-DD | Greeting.
Required for every active Bulk SMS by SMM account. The in-app report is generated once each day even when Follow-up is OFF.
Search campaigns, pin or favorite important work, and review sending progress. Follow-up activity stays grouped under its Journey.
Each saved Follow-up Journey keeps its own stages and recipients together.
Delivery confirmations are checked after sending. Confirmed delivered recipients move to the next eligible Follow-up step, while pending recipients wait for a delivery update.
| Campaign | Sender | Mode / Route | Send Status | Recipients | Sent | Delivered | Waiting DLR <72h | Failed | Schedule | Action |
|---|
Open real campaign details, export recipients and monitor sent / failed activity by period.
Download a client report or CSV for the selected period. Opening or downloading a report does not send SMS.
Choose a period. The summary opens in a clear stacked format and shows sent, delivered, failed, value used and current balance.
Sent, delivered, failed and estimated value for each period. Today and Yesterday use Africa/Dar_es_Salaam calendar days.
| Period | Campaigns | Recipients | Sent | Delivered | Failed | Waiting DLR <72h | Estimated Value |
|---|---|---|---|---|---|---|---|
| Loading report periods… | |||||||
Shows actual SMS sent from recipient timestamps for Today and Yesterday. This is separate from cumulative campaign totals.
| Campaign | Today Actual | Yesterday Actual | Daily Limit | Remaining Today |
|---|---|---|---|---|
| Refresh Reports to load the daily limit check. | ||||
Open Campaigns and tap VIEW to inspect recipients, statuses and export ALL / SENT / FAILED. Failed or rejected recipients are also available from Contacts → FAILED.
Estimate campaign and follow-up cost before sending. Opening pages, cards and exports does not use SMS balance.
SMS balance, top-up requests and transaction history.
Read-only billing documents from your saved commercial plan and existing transaction ledger. Invoice is not proof of payment; receipt is enabled only for a verified/recorded payment with a positive amount.
Your Balance page shows the active SMS credit and billing information for this account.
Your saved plan shows the included SMS allowance and billing cycle. The balance above remains the amount currently available to send.
| Plan | Cycle | Included | Status | Grant Mode |
|---|---|---|---|---|
| Loading cycle history... | ||||
| Date | Type | Status | Amount | SMS | Reference | Document |
|---|---|---|---|---|---|---|
| Open Balance to load payment history. | ||||||
Enter the SMS quantity. We calculate the amount using your current SMS rate. Payment is manual through Selcom; SMS is added only after admin verification.
| Date (EAT) | Type | Status | SMS | Amount | Balance | Reference |
|---|
Review your access role, system audit trail and data-retention state. Do Not Send numbers are suppressed only for this Bulk SMS by SMM account and are not deleted from Contacts.
OWNER / MANAGER / OPERATOR / VIEWER with server-side role checks. Existing owner access remains unchanged.
| Member | Role | Status | Action | |
|---|---|---|---|---|
| Loading... | ||||
In-app popups are automatic while the portal is open. Enable Web Push once on this device so Bulk SMS by SMM can alert you about campaign completion, balance and Sender ID events even when the installed PWA/page is closed, subject to browser/device notification support.