The prompt
Score 10 of 10, Excellent
Use it when You need a quick answer from a busy colleague on Slack or Teams and want a message they can reply to in a few seconds from their phone.
- {{platform}}
- {{recipient}}
- {{question}}
- {{context}}
- {{deadline}}
- {{options}}
- {{where}}
Full prompt and why it works
Prompt
Write a {{platform}} message to {{recipient}} asking for what I need, so that they can answer in a few seconds from their phone between meetings, without scrolling back or asking what I mean. Busy people answer chat messages that put the question first and make the answer easy; the rest wait until later, and later is often too late. What I need to know or have decided: {{question}} Why I need it, and what I will do with the answer: {{context}} When I need it by: {{deadline}} Options I would be happy with: {{options}} Where it goes (direct message, a channel or a thread) and who else will see it: {{where}} Write it in this order: 1. The question in the first line, phrased so they can answer with a word, a letter or a number. 2. One or two lines of context after it, only what they need to answer. 3. If there are options, list them as A and B (and C if needed) so they can reply with a letter, and say which one I will go with if I do not hear back. 4. The deadline in plain words, such as "by 3 pm today", and why it matters if that is not obvious. Keep it under 80 words. It should sound like a colleague who respects their time: direct, friendly and without apologizing for asking. For example: "Can I send the client the revised quote today: A) as it is, or B) with the discount you mentioned? I'll go with A at 4 pm if I don't hear back. They asked for it by end of day." That example shows the form only. Do not open with "Hi, quick question" or a greeting on its own line, do not send a bare "Hey" before the real message, and do not write it like an email with a subject, paragraphs or a sign-off. Do not tag people who do not need to answer. In a busy channel, put the person's handle at the start. If my question is vague or could be read two ways, say so above the draft and suggest a sharper version. If there is no real deadline, leave the deadline out rather than inventing one.
Variables
- {{platform}}
- Where you are sending it, for example "Slack" or "Teams".
- {{recipient}}
- Who you are asking, and their role.
- {{question}}
- What you need answered or decided, in your own words.
- {{context}}
- Why you need it and what depends on the answer.
- {{deadline}}
- When you need the answer, or "no rush".
- {{options}}
- The choices you would accept, or "none".
- {{where}}
- For example "direct message" or "the project channel, about 30 people".
Why it works
- Format. Question first, a line of context, lettered options and a default if nobody answers: a shape someone can reply to with one letter.
- Length. Under 80 words, because a chat message that needs scrolling gets saved for later.
- What to avoid. No standalone greeting before the question and no email structure around it, because both slow the reply.