How is this different from how I'd normally write to a peer?

It removes the gap between what you mean and what they'll read. You know what you intend; the Assistant knows their preferred frame. The rewrite reduces the chance your tone gets misread by the most-different communicator on your team.

Will this make my message feel formal?

Only if you set tone="formal". Defaults are casual + balanced — exactly the register most peer Slack messages live in. The output reads like you, not like a corporate email.

What about peer messages that are public (channels, threads)?

Same logic, higher stakes. Public peer messages reach mixed audiences with mixed styles — pick the most-likely-to-be-misread style of the channel, rewrite for that, and you'll land for everyone else too.

Free AI tool · No sign-up required

AI Communication Assistant for Talking to Peers and Colleagues

Disagree without picking a fight. Suggest without overstepping. Get peer messages to land the way you mean them.

Peer communication is uniquely fragile. There's no positional authority to lean on, no manager-report power dynamic that excuses bluntness or formality. Get the framing wrong and you've created a workplace tension that lasts the rest of the quarter — over a Slack message that took you 90 seconds to write.

The AI Communication Assistant rewrites peer messages so they land the way you intended. Tell it about the colleague: are they direct or diplomatic, what do they value, what's their tone? Paste your draft — disagreement, suggestion, course-correction, ask for help, whatever. Get a rewrite that respects them as a peer, not as a subordinate or superior.

Free, no sign-up, three rewrites a day. Built specifically for the situations where you can't fall back on hierarchy to clarify intent — code reviews, project disagreements, "did you see this?" pings, and anything labeled "could we…?".

Common scenarios

Disagreeing on a code review

"Your function is wrong" picks a fight regardless of recipient. The Assistant rewrites as "I think we may be looking at this differently" (collaborative) or "the function returns X when the spec says Y" (data-driven) depending on the peer's style.

Suggesting a different approach

Direct peers want the alternative + the reason in one sentence. Diplomatic peers need acknowledgment of their idea first. Same suggestion, different opening.

Asking a peer for help

Brevity-valuers want the ask + the context in two sentences. Warmth-valuers want the relational opener. Generic "got a sec?" reads as either polite or evasive depending on the peer.

Calling out a peer's mistake

This is the highest-stakes peer message. The Assistant tunes between "hey, I think this got swapped" (warm) and "the value at line 32 is unsigned but the spec is signed" (data-driven) — which sounds like generosity to one peer and condescension to the other.

FAQ

How is this different from how I'd normally write to a peer?: It removes the gap between what you mean and what they'll read. You know what you intend; the Assistant knows their preferred frame. The rewrite reduces the chance your tone gets misread by the most-different communicator on your team.
Will this make my message feel formal?: Only if you set tone="formal". Defaults are casual + balanced — exactly the register most peer Slack messages live in. The output reads like you, not like a corporate email.
What about peer messages that are public (channels, threads)?: Same logic, higher stakes. Public peer messages reach mixed audiences with mixed styles — pick the most-likely-to-be-misread style of the channel, rewrite for that, and you'll land for everyone else too.

Map your own communication style

Take the 5-minute Communication DNA survey. Anyone messaging you can then use Empatalk to phrase it in your style automatically — the inverse of what this page does.

Take the survey

Looking for the general tool? AI Communication Assistant home