Browse documentationNeed a hand? Contact support

Rewrite

Prompts for everyday work

Use these editable starting points for emails, notes, agent requests, and translation.

In the appSettings → Rewrite → Profiles

On this page

Create a profile for a task

  1. Set up a rewrite model and turn rewriting on.
  2. Choose New profile, give it a useful name, and replace its instructions with one of the examples below.
  3. Choose that profile before recording. Try a short dictation and adjust the instructions to suit your writing.

Save these examples as custom profiles and adapt them to your work. The sample results show the intended format; wording varies by model. If you do not want the text transformed, choose No rewrite instead of creating a profile.

An email with your sign-off

Save this as My email and replace Peter with your name.

Profile instructions
Turn the dictation into a concise, friendly email body. Use complete sentences and short paragraphs. Preserve all names, dates, requests, and uncertainties. Do not invent a subject, recipient, deadline, or promise. End with a blank line followed by “Best regards,” and “Peter” on the next line. Return only the email body.

You might say

Hi Svenja, um, could you send me the updated proposal before our call tomorrow? I just want to have a look through it first.

Example result

Hi Svenja, Could you send me the updated proposal before our call tomorrow? I’d like to review it beforehand. Best regards, Peter

The signature comes from your saved instructions. The built-in Email / message profile keeps greetings and sign-offs only when you speak them.

Structured notes

Profile instructions
Organize the dictation into clear notes. Use headings for Decisions, Action items, and Open questions only when the dictation contains that kind of information. Put one item on each bullet. Preserve names, dates, numbers, and uncertainty. Do not invent owners, deadlines, or decisions. Return only the notes.

You might say

Okay, we’re keeping the current launch date. I need to ask Michele about the revised quote. We still don’t know whether the customer wants the extra training session.

Example result

Decisions - Keep the current launch date. Action items - Ask Michele about the revised quote. Open questions - Does the customer want the extra training session?

Dictate your takeaways after a meeting, or talk through your plan for the day to turn it into an organized note.

A clearer coding request

The built-in AI agent prompt is a useful place to start. For a custom profile, try:

Profile instructions
Rewrite the dictation as a request for a coding agent. Start with the change being requested, then list the supplied constraints and observations. Keep technical terms, paths, and identifiers as given. Preserve uncertainty instead of presenting guesses as facts. Do not invent requirements, propose an implementation, or answer the request. Return only the request.

You might say

Can we add search to the customer list? Um, name or email should both work. Keep the filters we already have, and, yeah, a message when nothing matches would be good.

Example result

Add search to the customer list. - Match customer names and email addresses. - Keep the existing filters. - Show a message when no customers match.

Click the agent’s input before recording. MicMyDay prepares and inserts the request; the agent performs the coding work.

A message in another language

Profile instructions
Translate the dictated message into natural English. Keep its meaning and level of formality. Preserve people’s names, product names, and technical terms. Do not add explanations or new facts. Return only the translated message.

Change English to your target language. Choose a transcription model that understands the language you speak and a rewrite model that supports both languages. The Spoken language setting describes the recording; it does not choose a translation target.

To keep a particular name or abbreviation unchanged, include its spelling and a preservation instruction in the profile.

Improve a prompt that misses the mark

  • Too much extra wording: specify the format and ask for only the finished text.
  • Missing details: explicitly preserve names, numbers, constraints, and uncertainty. Avoid asking for a summary if you need every detail.
  • The model answers instead of rewriting: ask it to transform the transcript without answering the request.
  • Unwanted headings or Markdown: say “Use plain text without headings” or define exactly the headings you want.
  • A local model struggles: shorten the instructions and dictation, or try another model with the same example.