Rewrite selected text with team context.
Highlight a draft in Slack, Gmail, docs, or support. Rewrait runs the shared shortcut, reads the approved sources, and replaces the text in place.
Rewrait shortcut
Customer reply
Use the company voice guide, keep policy language intact, and add meeting slots if the draft asks for scheduling.
Replaced text
Thanks for the patience. The delay came from the billing sync review, and we are keeping the rollout paused until the account data is verified. I can walk you through the plan on Tuesday at 10:30 or Wednesday at 14:00.
Rewrites happen where the draft already lives.
Attach Notion, docs, calendars, CRM notes, and macros.
Give everyone the same approved writing moves.
Shortcut path
Write the instruction once. Run it anywhere text is selected.
A shortcut is part instruction, part approved source list, and part desktop action. The writer stays in Slack, Gmail, docs, the CRM, or the support desk while Rewrait handles the rewrite.
Customer reply
Use the voice guide, keep policy language intact, and add meeting slots from Calendar.
Thanks for the patience. The delay came from the billing sync review. I can walk you through the plan on Tuesday at 10:30 or Wednesday at 14:00.
- 1 Select text
- 2 Run shortcut
- 3 Read sources
- 4 Replace draft
-
1
Write the shortcut
Describe the job once: use the company voice guide from Notion, keep support policy intact, and check Calendar when the draft asks for a meeting.
-
2
Select text anywhere
Highlight a draft in Slack, email, docs, a CRM, a support desk, or a browser field. Rewrait opens over the app you are using.
-
3
Run the shortcut
Pick the shortcut for the job, such as customer reply, sales follow-up, executive update, or meeting response.
-
4
Review and replace
Accept the rewrite, make a quick edit if needed, and replace the original without moving the work into a chat tab.
Shortcut recipes
Turn repeated writing jobs into named moves.
Start with one messy recurring draft. Support replies, sales follow-ups, meeting responses, launch notes, and internal updates all become shortcuts with the right context already attached.
Use the company voice
Use the company voice guide and support policy. Rewrite the selected text as a calm customer reply.
Handle scheduling when it appears
If the selected text asks for a meeting, check Calendar and include two available slots.
Keep claims approved
Use the sales messaging guide. Remove unsupported claims and rewrite as a concise follow-up.
Native desktop layer
Keep the writing in the app where the work started.
Rewrait appears over the current app, returns the rewrite, and lets the writer replace the selected text. No copy-paste detour, no prompt archaeology, no manager fixing the same tone issue again.
Best first rollout: choose one high-volume draft type, connect the source that governs it, and turn it into a team shortcut.
Integrations
Shortcuts read from the places your team trusts and run where people type.
Use context sources for rules and facts. Use app targets for the actual draft. Rewrait connects those two worlds in one keystroke.
Sources shortcuts can read
- Notion docs
- Google Docs
- Confluence
- Calendar
- CRM notes
- Prompt libraries
- Support macros
Read context, rewrite selected text, replace it in place.
Apps where shortcuts run
- Slack
- Teams
- Gmail
- Zendesk
- Intercom
- Linear
- HubSpot
- Browser fields
Team shortcuts
One rewrite layer for every team that writes.
Each team keeps its own shortcut names, source rules, and accepted output shape. The daily action is still the same: select text, run Rewrait, replace the draft.
Support
Rewrite rushed replies with policy, tone, and next-update rules from the support playbook.
Support policySales
Turn rough follow-ups into approved positioning and add meeting slots when the buyer asks.
Sales messaging + CalendarCustomer Success
Convert account notes into customer updates that use the right tone for renewals, risk, and adoption.
Success playbookProduct and Ops
Turn raw bullets into launch notes, incident updates, and decision summaries that match internal rules.
Release rulesTrust model
Company text should not disappear into a black box.
The public promise is concrete: on-demand processing, no model training on company text, and team control over shared shortcuts.
Runs only when selected
Rewrait works when someone selects text and triggers a shortcut. It is not an always-on writing monitor.
No model training on company text
Selected text is processed to return the rewrite. It is not used to train Rewrait or third-party models.
Team-controlled shortcuts
Teams can standardize approved shortcuts, manage history behavior, and use bring-your-own-key options where enabled.
FAQ
Questions before your team tries Rewrait
Is Rewrait only for individual writers?
No. The team version is built around shared shortcuts, approved prompts, connected context, and rewriting selected text inside the tools where work happens.
Can a shortcut use our Notion style guide?
That is the direction of the team product: use writing rules from sources like Notion, docs, playbooks, and prompt libraries so rewrites match company guidance.
Can a shortcut check a calendar?
Calendar-aware instructions are part of the shortcut model. For example, a shortcut can rewrite a reply and include available meeting slots when the selected text asks for scheduling.
Does Rewrait replace our existing tools?
No. Rewrait sits on top of the tools your team already uses. People keep writing in Slack, email, support desks, docs, CRMs, and browsers.
Do you train models on company text?
No. Text is processed to produce the requested rewrite and is not used to train Rewrait or third-party models.
What should a team start with?
Start with one repeated writing job: support replies, sales follow-ups, meeting responses, internal updates, incident notes, or brand voice rewrites.
Build your first team shortcut around one messy draft.
Start with company voice, support replies, sales follow-ups, meeting responses, or any draft your team rewrites every week.