Pick the moment, not the queue
Choose a date, a time and a time zone. Nine in the morning means nine in the morning where the customer is, not where you happen to be sitting.
Appointment reminders, renewal notices, the follow-up you will forget on Thursday. Schedule a text from your business line and get on with the day.
Nobody reads a reminder about tomorrow when it arrives four days early, and nobody sends one at seven the next morning either. Writing it while you are thinking about it and letting it arrive when it lands is the whole trick.
Everything still to come, and what happened to everything that has been.
Hi Dana, a reminder about tomorrow at 10. Cancel or rewrite until thenThe hard parts are the time zone, the person’s name, and everything that might change between writing the message and sending it.
Choose a date, a time and a time zone. Nine in the morning means nine in the morning where the customer is, not where you happen to be sitting.
Every waiting message can be rewritten or cancelled right up to the moment it sends. After that it is a message you sent, and it stays honest about that.
Write Hi {{contact.name}} once. Names, numbers and the date are filled in at the moment of sending, so a message written on Monday for Friday says Friday.
A scheduled message goes through the same checks as anything typed just now. Somebody who replies STOP on Wednesday does not receive Thursday's reminder.
A scheduled message is an intention, not a queued send. Nothing is decided until the moment it fires.
Pick the line it goes from, who it goes to, and what it says.
A date, a time, and the time zone it means. Miss Blue warns you before scheduling something for the middle of somebody’s night.
Anything still waiting can be rewritten or stopped. Nothing about that is irreversible until it is.
Sent, or not sent and why — in the same sentence anybody sending by hand would have been shown.
One message to a list, sent as a separate conversation to each person, paced so a business line does not start looking like a broadcast channel.
Both. A scheduled message goes out over the same path as anything else from that line: iMessage where the recipient is on Apple, with automatic SMS or RCS fallback where they are not.
It does not send. A scheduled message runs every check at the moment it fires rather than the moment you wrote it, so blocks, opt-outs, your do-not-message list and the new-contact limit are all evaluated against the world as it is that morning. The row then says exactly why it did not go.
The one you pick when you schedule it. That is stored with the message, so the list shows 9:00 AM EDT rather than translating it into whatever zone the person reading the screen happens to be in.
Until it sends, yes — the words, the time, or cancel it entirely. Once it has gone it cannot be edited or unsent, and the list keeps showing the words that actually went.
Yes. Variables like {{contact.name}} are filled in when the message sends, and you can give a fallback for the ones you do not have — {{contact.name|"there"}} becomes "there" rather than leaving a gap.
Messages are not metered on a Miss Blue plan, so scheduling costs nothing per message. What is limited is first contacts: 50 new people per line per 24 hours, because a business line that starts messaging hundreds of strangers a day is a line that gets flagged.
Yes. Schedule, edit, cancel and read them through the same REST API as everything else, with signed webhooks when one sends or fails.
Nothing is held in memory. A scheduled message is a row with a time on it, and the scheduler asks the database what is due — so a restart loses nothing and sends nothing twice.
Build two-way blue-bubble conversations into your product or agent.
Use a complete shared conversation platform without writing code.
Call from your blue line without carrier Spam Likely labels.
Call any dialable number from your Miss Blue business line.