These work as text requests for an AI assistant that accepts messages. If you still need one, choose a text assistant first. Our tool-finding bot recommends software; it does not answer these prompts itself.
The examples and reference answers below were written for this guide. They show what a useful answer should preserve; they are not screenshots or results from a tested bot.
1. Make a message clearer without changing the promise
Use this when your draft is awkward but the details are already right. Copy the whole request, including the draft:
Rewrite this as a short, friendly message. Keep Friday, 3 pm, three screenshots and the request for confirmation. Do not add an apology, an explanation or a new promise. Return only the message. Draft: Hey, about Friday, I can send the three screenshots at 3 pm, is that okay? just confirm please.
One suitable answer: I can send the three screenshots on Friday at 3 pm. Please confirm whether that works for you.
Reject this change: “I’ll send them by Friday” loses both the time and the number of screenshots. If you replace our draft with yours, list the details that must survive.
2. Shorten an announcement without losing its conditions
Summarize the announcement below in two bullets. Keep the number of places, both registration limits, when the room will be announced, and the laptop requirement. Use only the announcement. The workshop has 20 places. Registration closes on Friday at 5 pm, or earlier if all places are filled. We will announce the room on Monday. Bring a laptop: a phone is not enough for the practical exercise.
A complete two-bullet answer:
- There are 20 places. Register before Friday at 5 pm; registration may close earlier if the workshop fills.
- The room will be announced on Monday. Bring a laptop; a phone will not be enough.
“Register by Friday” sounds tidy but could make you miss the workshop. Check dates, numbers and words such as unless, before and only against the original.
3. Turn messy notes into tasks without inventing an owner
Separate these notes into Decisions, Tasks and Open questions. For each task, include the owner and deadline only if the notes state them. Otherwise write “not specified”. Do not turn a suggestion into a confirmed decision. We chose the blue cover. Nora will send three screenshots on Friday at 3 pm. We have not agreed on a launch date. Someone needs to check the mobile layout.
Swipe to compare
| Type | What the notes support |
|---|---|
| Decision | Use the blue cover. |
| Task | Nora: send three screenshots, Friday at 3 pm. |
| Task | Check the mobile layout. Owner and deadline: not specified. |
| Open question | What is the launch date? |
A neat table with a made-up launch date is worse than an unfinished one. Leave the gap visible so someone can answer it.
When the answer still gets something wrong
Point to the exact mistake: “You removed the early closing condition. Put it back and keep two bullets.” If the same detail keeps disappearing, edit the short answer yourself rather than repeatedly asking for a nicer tone.
For recordings, correct the transcript before extracting tasks. For a PDF, use questions with page references.
