Bing AI Writing Prompts

Draft a concise follow-up email to [PERSON] after our [MEETING]. Goal: confirm the decision, list the two actions I own, and ask one clear question about the unresolved issue. Use a warm professional tone, no sales language, and keep it under 160 words. Use only the notes I attach; mark anything that is not stated.

Rewrite the email below for a busy US customer. Keep the promised date, price, product name, and next step exactly as written. Remove defensive language, explain the delay in plain English, and make the first paragraph answer 'what happens next?' Output the subject line followed by the revised email. Do not add an apology unless the original includes one.

Turn this rough message into three versions: direct and professional, warm and collaborative, and brief for Teams. Keep the facts identical in all three. The recipient is [ROLE], the desired action is [ACTION], and the deadline is [DATE]. Flag any missing information before drafting.

Review this customer reply for tone and hidden ambiguity. Return a table with columns: original sentence, risk, why it may be misunderstood, safer rewrite. Do not make the message more formal than necessary and do not introduce a promise that the company has not made.

Write a polite decline to [REQUEST]. Context: we cannot [CONSTRAINT], but we can offer [ALTERNATIVE]. Keep the relationship positive, state the reason in one sentence, and finish with a concrete next step. Maximum 120 words. Avoid phrases such as 'unfortunately' and 'at this time'.

Create a weekly status update from the attached notes. Use four headings: Completed, In progress, Blocked, Next week. Include owners and dates only when the notes state them. Put decisions that need leadership input in a separate final section.

Read the attached report as a finance lead preparing for a 15-minute leadership meeting. Extract the three material changes, the numbers that support them, the two risks, and any decision required. Start with a 100-word brief. Then use a table with columns: issue, evidence, implication, owner or unknown. Do not infer a cause that the report does not support.

Turn this policy into a one-page employee guide. Preserve every obligation, exception, deadline, and escalation path. Use plain US English at approximately an eighth-grade reading level. After the guide, list five points where a reader could misunderstand the policy and quote the original section that resolves each point.

Compare versions A and B of this document. Return only substantive changes: changed meaning, new obligations, removed rights, changed dates, changed prices, and altered definitions. Use a table with old text, new text, impact, and review priority. Ignore formatting changes unless they change meaning.

Create an outline for a 1,500-word article from the attached research notes. The audience is [AUDIENCE]. Give each section a purpose, the evidence it should use, and one question the section must answer. Do not write the article yet. End with the three claims that need the strongest verification.

Rewrite the selected paragraph for clarity without changing any fact, number, qualification, or legal meaning. Keep the author's point of view. Return the revised paragraph, then a sentence-by-sentence change log. If a sentence is unclear because the source is missing, leave a bracketed editor note rather than guessing.

Extract every recommendation from this report and group them into immediate, next quarter, and later. Include the evidence, dependency, likely owner, and unresolved question for each. If the report does not contain a time horizon, propose one only in a separate 'editorial suggestion' column.

Research [TOPIC] for a US audience as of [DATE]. Use primary sources first and include the publication date and URL for every important claim. Separate verified facts, expert interpretation, and unresolved questions. Finish with a 150-word answer, a source table, and three claims I should not publish without further checking.

Compare [PRODUCT A] and [PRODUCT B] for a 20-person marketing team. Use each company's current pricing and documentation where available. Evaluate features, limits, data handling, collaboration, export, and likely workflow fit. Do not select a winner until you show the trade-offs for a small team with a $[BUDGET] monthly limit.

Find the strongest evidence for and against the claim: '[CLAIM]'. Prefer government, academic, company filings, or original research. Do not treat a blog repeating another article as an independent source. Return a balanced briefing with source quality, date, conclusion, and what remains uncertain.

Turn this research into a fact-checking checklist for an editor. For every statistic, named person, product claim, and date, list the source that should be checked, what wording would overstate the evidence, and a safer alternative if the number cannot be verified.

Create five interview questions for US customers who use [TOOL] for [JOB]. The questions should uncover the trigger, current workaround, cost of the problem, switching barrier, and moment of value. Avoid leading questions and do not ask whether they 'like' the product.

From this meeting transcript, extract decisions, proposals, open questions, and actions. Do not turn a proposal into a decision. For each action, include owner, due date, dependency, and transcript evidence. Use 'not stated' when missing. End with a five-bullet update suitable for someone who did not attend.

Prepare me for tomorrow's meeting using the attached agenda, last meeting notes, and open action list. Return: decisions we need, information gaps, questions to ask, likely objections, and a 60-second opening statement. Keep facts tied to the files and label preparation suggestions separately.

Turn these project notes into a RAID log: risks, assumptions, issues, and dependencies. Include description, impact, probability if stated, owner, next action, and review date. Do not invent scores. Put items that need a decision in a separate table.

Draft a Teams message that unblocks [PROJECT]. State the current status, the exact input needed from [PERSON], why it matters, and a proposed deadline. Keep it under 90 words and make the request answerable in one reply.

Review this project update as a skeptical programme manager. Identify vague status language, missing owners, hidden dependencies, and claims that need evidence. Return the original phrase, the risk, and a sharper replacement question. Do not rewrite the whole update.

Create 10 headline options for [OFFER] aimed at [AUDIENCE]. The promise is [PROMISE], the proof is [PROOF], and the main objection is [OBJECTION]. Write five direct options, three curiosity-led options, and two contrarian options. No clickbait, unsupported superlatives, or vague words such as 'revolutionary'. Explain the intended angle in one short label per headline.

Turn these customer interviews into a messaging map. Extract repeated pains, desired outcomes, current alternatives, buying triggers, and phrases customers used more than once. Separate direct quotes from your interpretation. End with three positioning hypotheses and the evidence that would disprove each.

Draft a landing-page outline for [PRODUCT]. Audience: [PERSONA]. Primary action: [CTA]. Include the problem, mechanism, proof, objections, comparison, and next step. For each section, state what evidence is needed. Do not write generic benefit claims that are not supported by the supplied product notes.

Repurpose this long article into a LinkedIn post, email, short video script, and FAQ answer. Keep the central claim and evidence consistent. Make each format native to its channel, not a shortened copy of the article. List any nuance that was removed from each version.

Audit this page for search and answer-engine usefulness. Identify the query it answers, the direct answer a reader should see first, missing evidence, confusing headings, unsupported claims, and the most useful internal link. Do not recommend adding filler or repeating the keyword.