Draft a business letter from [SENDER AND ORGANIZATION] to [RECIPIENT AND ROLE]. The purpose is [PURPOSE AND REQUEST]. Use these facts only: [FACTS AND SUPPORTING DETAILS] Relationship and delivery context - Prior relationship or correspondence: [RELATIONSHIP CONTEXT] - Required tone and sensitivity: [TONE] - Deadline, response method, or next step: [NEXT STEP] - Any policies, attachments, or boundaries to mention: [REQUIREMENTS] Write the letter in a formal business-letter format suitable for email or letterhead: date line, recipient block with placeholders where details are absent, subject line, salutation, 3-5 concise body paragraphs, closing, sender name/title block, and an enclosure line if applicable. Keep it to 350-500 words unless the facts require less. Structure the body carefully: open with the purpose and why it matters to the recipient; state relevant facts in chronological or decision-ready order; make one precise ask; explain the requested response or deadline; close respectfully without repeating the whole letter. If this is a complaint, distinguish observed facts from conclusions and state the remedy sought. If it is a proposal or request, avoid claims not supported by the supplied facts. If it is a notice, state effective dates and actions plainly. Give me the final letter first, followed by a short “Items to confirm” list only for unknown details that could change the wording. Do not invent names, dates, policy terms, commitments, pricing, legal conclusions, or attachments. Before finalizing, check that the recipient can identify the action, owner, deadline, and response channel in one read; also flag language that could be interpreted as a legal promise or admission. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [SENDER AND ORGANIZATION] | Enter the sender’s name, title, organization, and contact details if known. | Maya Chen, Operations Director, Pine Street Foods, 18 Willow Avenue, Providence, RI 02903 |
| [RECIPIENT AND ROLE] | Enter the recipient’s name, title, organization, and address or email context if known. | Daniel Ortiz, Account Manager, Meridian Cold Storage, 550 Harbor Road, New Bedford, MA 02740 |
| [PURPOSE AND REQUEST] | Enter why the letter is being sent and the exact action requested. | Request a written corrective plan for repeated late deliveries and confirmation of the next two delivery windows. |
| [FACTS AND SUPPORTING DETAILS] | Enter verified dates, amounts, events, reference numbers, and other facts that support the letter. | Purchase order PSF-1842; deliveries scheduled for August 4, 11, and 18 arrived on August 5, 13, and 20; the August 20 delivery left us short of frozen produce for two days. |
| [RELATIONSHIP CONTEXT] | Enter the relevant history with the recipient and prior communications. | We have used Meridian for 18 months. Maya discussed the August 13 delay with Daniel by phone on August 14. |
| [TONE] | Enter the required level of formality and any relationship sensitivities. | Firm and professional, preserving the supplier relationship. |
| [NEXT STEP] | Enter the response deadline, preferred channel, and what happens next. | Please reply by September 2 by email with the corrective plan and confirm delivery windows for September 4 and 11. |
| [REQUIREMENTS] | Enter required policy references, attachments, limitations, or approval language. | Reference the existing service agreement only by name; attach the delivery log; do not threaten termination. |
How to use
- Paste verified facts and write the ask as one observable action, such as “confirm by September 2” or “sign and return.”
- Check dates, names, amounts, attachments, and the authority of the sender before sending.
- For sensitive disputes, have the appropriate legal or policy owner review language about liability, breach, settlement, or rights.
- Follow up with: “Make a 150-word email version that preserves the same request and deadline.”
Variations
Request letter
Use when asking another organization for a decision, document, exception, or support.
Write a formal request letter from [SENDER] to [RECIPIENT] asking for [SPECIFIC REQUEST]. The decision context and verified facts are [FACTS]. The recipient’s likely concerns are [CONCERNS], and the requested response date is [DEADLINE]. Use a respectful, direct tone. Write a subject line, salutation, three body paragraphs, closing, and sender block, under 400 words. Explain the benefit or basis without overstating it, make the requested action unmistakable, and state what information is attached. Do not invent authority, deadlines, or prior commitments. Check that the letter has only one primary ask and a usable response path.
Complaint letter
Use when documenting a service, product, billing, or contract problem and asking for a remedy.
Draft a business complaint letter to [RECIPIENT] about [ISSUE]. Use only these dated facts: [EVIDENCE]. We have already tried [PRIOR STEPS], and we seek [REQUESTED REMEDY] by [DEADLINE]. Maintain [TONE]. Format it as a formal letter under 500 words. Separate facts from impact, identify any relevant order or account reference, and state the remedy without threats or unsupported legal conclusions. Mention attachments only if supplied. Do not invent damages, policy terms, or admissions. Check that a third party could reconstruct the timeline and identify the exact remedy requested.
Proposal letter
Use when opening a formal commercial proposal before a full statement of work or contract.
Write a business proposal letter from [SENDER] to [RECIPIENT] regarding [OPPORTUNITY]. The recipient’s stated need is [NEED], our verified capability is [CAPABILITY], and proposed scope or commercial terms are [TERMS]. The desired next step is [NEXT STEP]. Keep it under 450 words in a confident, professional tone. Connect two supplied capabilities to two recipient needs, identify exclusions or assumptions plainly, and invite a specific discussion or approval action. Do not invent case studies, savings, delivery dates, or contractual commitments. Check that promises are limited to approved terms and that the next step has an owner and date.
Tips
- A business letter should have one primary ask; a cluster of unrelated requests makes it easy for the recipient to answer none of them.
- Use exact dates, order numbers, and prior-contact references when documenting a problem, but keep interpretation separate from evidence.
- Match formality to the relationship: a vendor dispute may need a subject line and record-ready facts, while a long-standing partner may need warmer context.
- Do not let an AI draft create legal admissions, guarantees, or policy statements that an authorized person has not approved.
FAQ
Should I use a letter or an email?
Use a letter when formality, record keeping, or a signed document matters. An email can carry the same structure when speed and a reply thread matter more.
Can AI write a complaint letter?
Yes, if you provide a factual timeline and exact remedy. Have counsel or the responsible leader review language that could affect legal rights or liability.
How long should a business letter be?
Most fit within 350-500 words. Add length only when the recipient needs a documented timeline or specific technical details to make a decision.