Get a message you can copy, review, and share without making up details about the recipient. Use this page for a specific outreach, follow-up, hiring note, partnership proposal, or customer-support response. The generator works from the facts you provide and flags missing information before drafting.
Expected result: a short, specific, verifiable message with an optional subject line, a clear call to action, and a tone suited to the channel.
Facts, missing information, and risks panel
Complete this panel first:
| Field | Your information |
|---|---|
| Recipient and role | |
| Company, product, or context | |
| Confirmed facts | |
| Message objective | |
| Channel and length limit | |
| Desired tone | |
| Missing information | |
| Risks or constraints |
Core rule: use only supplied facts. Do not invent achievements, titles, customers, dates, prior relationships, problems, or outcomes. If a required detail is unconfirmed, mark it as pending or ask for it.
Five modes
- Prospecting: first contact with a person or account. Include a fact-based observation and a concrete value proposition.
- Follow-up: reopen a conversation, proposal, or shared resource without pressure. Refer to the last confirmed point and suggest a small next step.
- Hiring: contact a candidate or referrer. Explain why you are reaching out, describe the role, and request one action without promising unapproved terms.
- Partnership: propose collaboration between organizations. State the fit, expected exchange, and purpose of an exploratory conversation.
- Customer support: acknowledge the issue, explain the next step, and avoid promising a fix that has not been verified.
Fill-in worksheet
- Mode:
- Recipient:
- Confirmed fact 1:
- Confirmed fact 2:
- Confirmed need or issue:
- What you offer or request:
- Allowed proof point:
- Low-effort next step:
- Information to confirm:
- Risk of misunderstanding:
- Channel, language, and length:
Instructions
- Choose one mode and one objective. “Get a reply” is more useful than “explain everything.”
- Separate facts from inferences. A fact may be stated; a hypothesis should be phrased as a question.
- Complete the missing-information and risk fields. Stop and request clarification when an essential detail is absent.
- Specify channel, length limit, and tone. Email supports context; direct messages need tighter wording.
- Generate two versions: one direct and one more conversational. Keep only traceable claims.
- Check names, links, dates, pricing, permissions, and calls to action.
- Copy or share the final version with an internal note listing the facts used.
Worked example: prospecting
Supplied facts: Marta leads Operations at NexoLog. NexoLog announced that it opened three regional centers. Your company offers a tool that consolidates operational incidents in one dashboard. You do not know which system Marta uses or whether this is a current problem. Channel: email. Objective: book a 20-minute conversation.
Direct version
Subject: Operational incidents across NexoLog’s new centers
Hi Marta,
I saw that NexoLog opened three regional centers. As operations expand across locations, bringing incidents into one dashboard can help teams spot patterns and assign ownership.
At [your company name], we offer a tool for that kind of centralized tracking. I do not know what system you use today or whether this is a priority for you. Would you be open to 20 minutes next week to compare your current process with an alternative?
Best,
[Name]
Conversational version
Hi Marta, I saw the news about NexoLog’s three new centers. I was curious how you are coordinating incidents across regions. Quest provides a dashboard for centralized tracking. If this is on your list this quarter, would a 20-minute conversation be useful? If not, I would appreciate a pointer to the right owner.
Contrast: the first version gives more context; the second lowers the initial commitment. Neither claims that NexoLog has a problem or that Quest delivered a specific result.
Copy-ready final artifact
SUBJECT: [verifiable topic]
Hi [name],
[Confirmed fact about the person, company, or conversation.]
[One-sentence proposal, response, or request.]
[Limitation or question if information is missing.]
Would you be open to [specific, small next step]?
Best,
[name]
Pre-send scorecard
- Every claim comes from a supplied fact.
- The objective is singular and the requested action is clear.
- There is no fake personalization or invented urgency.
- Names, links, dates, and sensitive details are checked.
- The message can be copied without internal instructions.
Failure checks
Do not send if the draft contains an unconfirmed company, title, relationship, meeting, metric, or pain point. Do not invent testimonials, discounts, availability, integrations, or outcomes. Do not automate mass sending, sensitive-recipient selection, or support responses involving refunds, security, or contractual commitments without human review. For high-risk cases, use the generator only as a draft and retain explicit approval.
Next step
Keep using this generator or the prompt tester for occasional, low-risk work. Consider a business audit when message work is recurring, involves a team, carries meaningful volume or spend, uses sensitive data, or creates a clear review and sending bottleneck.