Work & professional

Know what you mean.
Sound like you mean it.

The message has been open in another tab for an hour. You know the answer. What you are stuck on is how to say it without sounding defensive, junior or short.

The honest answer sounds like an excuse.
The short answer sounds annoyed.
So it has been sitting there for an hour.

Or just SayThis.

Get SayThis See the reply

SayThis writes the draft and puts it in your message box. You read it and you send it.

9:41

DDana (Manager)

morning — quick one about the pricing deck

Can you explain why this wasn't finished yesterday?

Message

SAYTHISReady

Take a screenshot

So SayThis can read the conversation

Import latest screenshot

The message you have reread four times

One line from your manager, and an hour gone.

Screenshot the thread, pick Professional, and read what comes back. The draft goes in your message box — nothing is sent until you send it.

Answering for something that slipped

It was late, and there was a reason, and saying the reason badly makes it worse.

ProfessionalPolished, respectful, and appropriate for work.

It answers the question, names the cause once without dressing it up as a grievance, and ends on a commitment. No apology loop, no corporate filler.

And if the thread is already tense

Calm

The updated numbers only came through late yesterday, so I held it rather than send something wrong. It will be with you this afternoon.

9:41

DDana (Manager)

morning — quick one about the pricing deck

Can you explain why this wasn't finished yesterday?

Message

SAYTHISReady

2 messages read

Professional

I was not able to finish it yesterday because I was waiting on the updated numbers from the team. I have those now and expect to have it with you this afternoon.

Insert

Try againKeyboard

Replies written for this page, not fixed output — SayThis writes to the conversation in front of it, so the same tone on your thread will read like your thread.

Monday to Friday

The messages that cost an afternoon.

None of them are hard to answer. All of them are hard to word.

Replying to your boss
“I need to explain this without it reading as an excuse.”
Can you explain why this wasn't finished yesterday?
Professional
Following up without nagging
“This is the third time I have asked and I still need it.”
Sorry, swamped — will get to it!
Direct
Responding to criticism
“Half of this is fair and half of it is not.”
Honestly the deck felt rushed. Not the standard I expect from your team.
Calm
Saying no professionally
“I cannot take this on and I cannot just say no.”
Any chance you could own the migration doc too? Monday would be ideal.
Firm
An unhappy client
“They are angry, they are partly right, and I am the reply.”
This is the second delay. I need to know what is actually going on.
Apologetic
Asking what they actually mean
“I have read it four times and I still do not know what is being asked.”
Can you just tidy up the approach before Thursday?
Friendly
Correcting a misunderstanding
“They have the wrong end of this and I have to say so carefully.”
Thanks for confirming you will cover the handover.
Direct
The message you have been putting off
“Every day I do not answer this makes answering it worse.”
Following up on my last two emails — is this still happening?
Apologetic

Same message, different tone

Professional, direct, friendly — pick the room you are in.

One request, four answers, all of them a no. The difference is what each one costs you with the person who asked. Tone is one choice; how long the reply runs is a separate one — Short, Normal and Detailed are lengths, not voices.

They said

Any chance you could own the migration doc too? Monday would be ideal.

You already have the launch checks. Monday is not real, and everybody in the thread knows it.

Happy to take the migration doc on. Monday is not realistic alongside the launch checks, so I can have it to you Wednesday, or hand the launch checks to someone else — whichever you prefer.

Polished, respectful, and appropriate for work.

A note on register

Professional does not have to mean robotic.

Most "professional" writing help produces the same paragraph every time: a thank-you, a passive sentence about circumstances, and an apology nobody asked for. It is safe, it is long, and it sounds like nobody wrote it.

SayThis starts from the conversation instead. It reads what was actually said — the tone it was said in, who is in the thread, what is being asked — and writes the reply to that. Professional here means what a good colleague sounds like: polished, respectful, and short enough to read on a phone between meetings.

And it stays yours. The draft lands in your message box where you can cut the sentence you would never have written, then you send it.

Before you ask

Two things worth knowing at work.

Does anything I paste in get stored?

No. Conversations and screenshots are not kept, and there is no setting that keeps them. Most screenshots are read on your phone and never uploaded at all — only the text is sent. Asking for a shorter version re-sends the conversation from your phone, because there is no copy on our side to reuse.

Can it reply to email as well as chat?

Yes. SayThis is a keyboard, so it works in any app with a text field — Slack, Teams, Gmail, your ticketing tool. It writes in the shape the medium uses: a couple of lines in a chat, a short paragraph in an email.