Saved contacts save typing
I save a name and number for frequent recipients. When I write a new message, I select the contact instead of typing the phone number again.
snow³
The 10 examples below were generated to demonstrate the page layout. They are not reviews from real users, and the dates are illustrative.
I save a name and number for frequent recipients. When I write a new message, I select the contact instead of typing the phone number again.
I find the separate queues useful: messages from my software wait for the daytime sending window, while manual messages take priority. Urgent notifications do not get stuck behind the regular queue.
A dedicated Android phone works well for my service messages. I can use my own SIM card and follow the queue in the dashboard.
I need a straightforward API for order collection notifications. Here I can submit a phone number, message text and message ID, then check the status.
Preparing a list in Excel is convenient: phone numbers in the first column, messages in the second. The preview helps me spot mistakes before messages join the queue.
Ten SMS a day is enough to explore the dashboard and try my workflow. I still need to account for my carrier’s SMS charges separately.
Customers do not need a separate app to receive an appointment reminder. A regular SMS with a clear message is enough.
Grouping messages by phone number makes it easy to review a conversation. It is especially useful when I have already saved the person’s name in contacts.
Seeing a customer’s reply alongside my service messages is useful. Reply forwarding needs to be enabled on the phone, and availability depends on the plan.
The dashboard shows when the phone was last connected and what is happening in the queue. This makes it easier to investigate a message that has not been sent yet.