Every Screen in SMS Deliverer, Explained
Six screens do most of the work: device detection, composing, contacts, reports, SIM quota and options. Each one below explains what the screen is for and when you will use it.
Six screens, one workflow
The screens below are captures from the Windows build, in the order you meet them. Every card says what the screen is for, when you use it, and what the capture itself shows.
Device detection and COM ports
What it is for. The first screen after install. It lists every modem and phone it can reach, the COM port or IP address it uses, the signal reading and whether the SIM is ready.
When you use it. Open it whenever a send fails: a missing COM port explains most 'device not found' errors before you touch the campaign.
Compose and send
What it is for. One message, one recipient list, one sending device. The counter shows GSM-7 or UCS-2 encoding and the number of segments, so you know the real cost before pressing send.
When you use it. Use it for ad-hoc messages and for proofing a template before a bulk campaign.
Contacts and lists
What it is for. The phone book stores numbers, names, groups and the opt-out flag. CSV imports map columns, skip duplicates and never overwrite an opt-out.
When you use it. Use it to keep one clean list for every campaign, or to move a list between machines.
Delivery reports
What it is for. A per-campaign view of delivered, failed and pending messages, with the carrier response for each failure and a per-SIM breakdown.
When you use it. Use it after every campaign and export the CSV when a client asks for proof of sending.
SIM quota and rate limits
What it is for. Per-device caps for messages per hour and per day, plus the current usage bar. When a cap is hit the queue moves to the next SIM instead of dropping messages.
When you use it. Use it when one SIM has a limited plan or when a carrier throttles burst sending.
Options and integrations
What it is for. The page where HTTP API, SMPP, SQL listener, webhook and mail-to-SMS are switched on, each with its own port and credentials.
When you use it. Use it on day one for the API, and later when you connect the gateway to an application or a monitoring system.
More settings and tools
The rest of the captures in the build: the main window, SIM queries, the COM port sorter and the tabs that hold the other settings.
Where each screen sits in the workflow
Detect
Confirm the hardware and the SIM before writing anything.
Compose
Write once, check the encoding, then reuse it as a template.
Select
Pull the list from the phone book and confirm the blacklist is applied.
Send and report
Watch the report, export it, and keep the local log for your records.