Not features chosen from a competitor's checklist. Each one exists because the question below was asked, repeatedly, by someone senior enough that the answer had to be structural.
“Why does this say noreply?”
An announcement about people's jobs, arriving from an address nobody can answer. Staff read the sender line before the subject, and a relay address tells them this is broadcast, not conversation.
So it sends from the real person's mailbox, and replies go back to them.
“Who hasn't read it?”
Asked in good faith, usually by someone who just wants reassurance. But per-person open and click reporting on your own employees is not lawful everywhere, internal messages included, and once the report exists it is evidence whether or not anybody is allowed to read it.
So there is no recipient column in the tracking tables. Not switched off, not configurable, not there, which is the only version of that answer a works council can check.
“Can you send me the staff list?”
Every marketing tool begins by asking you to upload your people, so the most sensitive file the company has ends up in a vendor's database, in whatever country their servers are in, in order to send an announcement.
So there is nowhere here to put one. No table holds a recipient, and the question cannot be asked because the answer would have nowhere to go.
“Who deleted the legal line?”
Someone in a hurry, at 17:40, on the template everyone copies. By the time it is noticed it has gone to twelve thousand people and the correction email is worse than the mistake.
So regions can be locked, and approval blocks the send until a named person signs off.
“It looked fine when I sent it.”
It did, in the preview. Then Outlook rendered it, and the carefully built layout collapsed into a single column with the logo three times too large.
So the output is MJML, which is built specifically to survive Outlook.
“Can you re-export the list?”
Export from the directory, clean it, import it into the vendor. Two weeks later somebody joins, somebody leaves, somebody moves department, and the copy you uploaded is wrong. The tool's whole job was to reach everyone who works here, and the only way it could was to keep its own stale idea of who that is.
So there is no import step at all. Campaigns are addressed to the distribution lists you already run, and your mail provider expands them at delivery, which means the list is right on the day it is used.
Four things worth establishing before a procurement conversation rather than during one.
Your support contact is the person who wrote the code and who has run a platform at your scale. There is no first-line queue and no ticket triage, and equally, no 24/7 desk. For internal communications, where the send is scheduled and the deadline is yours, that trade usually favours you. Confirm it against your own requirements.
Senders, collaborators, admin addresses, the lists you save and an audit log are all stored. The what we store section prints all of it, by database column, including the ones people usually hide.
It sends internal email beautifully and it does nothing else. No intranet, no chat, no employee app, no survey suite. If you want one vendor for all of it, this is the wrong product.
Because your own mailbox does the sending, your own Gmail limits apply. That is the trade for never being the sender, and it is the trade that makes the rest of it possible.
If any of the above sounded like your job, the tool was built for you specifically.
Start sending
SlipperySign Mail