Say no, chase a repair, quiet a neighbor

Some messages are hard because they can go wrong, not because they are long. You need to tell your manager you cannot take on another project. You need to remind a landlord, again, that the sink is still leaking. You need to ask the people upstairs to turn the bass down after midnight. Each one takes ten minutes to write and three days to work up to.

Any free chatbot can draft them in seconds, but only if your prompt controls the tone. Type "write an email saying I can't take on this project" and you usually get something that apologizes four times, explains too much and ends by offering to help anyway. Type "write a complaint to my landlord" and you may get something angry enough to damage a relationship you still have to live with.

The three prompts below tell the chatbot who the reader is, which facts to include, what tone to keep and how short to be. Copy one, replace the bracketed parts with your own details and paste it into any free chatbot. Then check the draft against the points further down before you send it.

Turning down extra work without apologizing

Here's the situation. Your manager or a colleague asks you to pick up a task, and you already have a deadline that the new task would push back. If you quietly say yes, you miss the deadline later. If you bluntly say no, it sounds like you don't want to help.

The naive prompt fails because chatbots lean toward being overly polite. Ask for a polite decline and you get "I'm so sorry, unfortunately I'm swamped." That reads as a personal refusal and invites a "just this once" reply. This prompt bans the apology words and turns the email into a decision for the sender: here is what I'm working on, here is what slips if I take this on, which do you want first?

Draft a concise, professional email responding to a work request that exceeds my current capacity.
Context:
- Sender: [Manager's Name / Colleague's Name]
- Incoming Request: [Briefly describe the requested task, e.g., Take over the quarterly client audit report]
- Current Priority: [Describe your existing primary deliverables, e.g., Completing the Q3 software migration rollout by Friday]
- Boundary: [Cannot take this on without delaying primary deliverables / Do not monitor emails after 6:00 PM]

Constraints:
- Tone: Professional, collaborative, calm, and firm.
- No unnecessary apologies (do not use "I'm sorry" or "Unfortunately").
- Frame the situation as a priority trade-off decision for the sender rather than personal unwillingness.
- Keep the length under 100 words.

Sender is the person's name, written the way you would address them. Incoming Request should be one line in their own words so they recognize it. Current Priority is where most people get vague. Name the actual deliverable and its date, because "I have a lot on" gives the reader nothing to weigh. Boundary is the line you won't cross: either the trade-off (this delays that) or a time limit.

A good draft stays under 100 words, opens with thanks rather than an apology, states your current deadline, says roughly how far it would slip, and ends with two options: they choose the priority, or you come back to the request after your deadline. If the chatbot makes up a number, such as "three business days", replace it with your own estimate or delete it. Never send a delay figure you haven't worked out yourself.

Chasing a repair the landlord has ignored

Here's the situation. Days or weeks ago you reported a leak, a broken heater or a faulty lock, probably by text or phone, and nothing has happened. You need a second message that gets action and also leaves a clear record if the problem gets worse or turns into a dispute.

The naive prompt fails in one of two directions. "Write a polite reminder about my sink" produces a message that is easy to ignore. "Write a strong complaint" produces threats and adjectives, which give the landlord something to argue with. This prompt asks for civil, factual language, a reference to the date you first reported the problem, and a request for the appointment in writing.

Draft a formal, polite maintenance escalation email to a property manager or landlord.
Details:
- Recipient: [Landlord / Property Management Company Name]
- Property Address: [Unit Number and Street Address]
- Maintenance Issue: [Describe issue, e.g., Water leaking under the kitchen sink]
- First Reported Date: [Date of initial report, e.g., October 12th via text]
- Impact: [Describe functional or safety impact, e.g., Unable to use kitchen sink; risk of cabinet wood rot]
- Required Action: [Request scheduled repair technician within 48 hours]

Constraints:
- Tone: Civil, objective, fact-focused, and legally clear.
- Explicitly establish a written record of previous notifications.
- Request written confirmation of the repair appointment date and time.
- Keep under 120 words.

Recipient is whoever actually handles repairs. Check your lease or past messages. Property Address includes the unit number so the message can't be filed under the wrong home. Maintenance Issue should be what you can see, not your diagnosis: "water pooling under the sink" rather than "the pipe is cracked". First Reported Date needs both the date and how you reported it. If you reported it more than once, list each date. Impact is what you can no longer do and what could get worse. Required Action is a specific deadline that's reasonable for the problem.

A good draft gives the first report date in its opening line, describes the problem in one or two plain sentences, and asks for written confirmation of a date and arrival window by a set time. Send it in writing, by email or through the landlord's tenant portal, and keep a copy along with photos. If your first report was by phone, this email may be your first written record, so make sure the date in it is correct.

Asking a neighbor to keep it down

Here's the situation. A television, a dog, late-night gaming or footsteps keep you awake, and it happens often enough that you need to say something. You'll keep passing this person in the hallway, so the note has to work without making them defensive.

The naive prompt fails because "write a note asking my neighbor to stop being so loud" assumes they already know and don't care. The chatbot follows that framing and the note comes out as an accusation. This prompt starts from what is usually true: most people have no idea how much sound carries through a wall or floor.

Draft a polite, friendly, but direct written note to a neighbor regarding recurring noise.
Details:
- Specific Issue: [Describe noise, e.g., Loud television bass / dog barking late at night]
- Timing: [Specify hours, e.g., Between 11:00 PM and 2:00 AM on weeknights]
- Impact: [Brief neutral impact, e.g., Wakes up family members / disrupts sleep before workdays]
- Goal: [Request volume reduction during designated quiet hours]

Constraints:
- Tone: Neighborly, empathetic, calm, and non-accusatory.
- Assume good intentions (assume they are likely unaware of sound transfer between units).
- Provide a polite closing that leaves room for open communication.
- Length: 60 to 90 words.

Specific Issue should name the sound, not the person: "bass from a television" goes over better than "your loud TV". Timing is the hours and days you actually hear it. If you aren't sure, write it down for a week first. Impact stays short and neutral, such as "wakes us before work". Goal is one concrete request with a time attached, like lower volume or headphones after a set hour. A request without a time is hard for anyone to follow.

A good note is 60 to 90 words, mentions how sound carries between homes, asks for one specific change and closes with a way to reach you. Decide on that before you send it. Leave a phone number only if you're comfortable with this neighbor having it. Otherwise, give your unit number and invite them to knock.

Read the draft before you send it

Each prompt sets a word limit and a tone, and chatbots usually stick to both. They don't reliably stick to your facts. Read the draft once looking only for details you didn't supply: a date, a number of days, a technician's name, a building quiet-hours rule you never mentioned. Delete or correct each one.

Then read it again as the recipient. Would your manager know exactly what to decide? Would the landlord know what to do and by when? Would your neighbor feel accused? If a sentence would annoy you, ask the chatbot to rewrite just that sentence, or rewrite it yourself.

If the first draft is close, don't start over. Ask for one change at a time: "shorter", "drop the second paragraph", "less formal, I get along with this colleague". If you'd rather not paste a real address or name into a chatbot, leave the brackets as labels and fill them in afterward. The draft will be just as good.

What this cannot do

• It can't make anyone say yes. A well-framed email gives your manager a clear choice. It doesn't guarantee they pick the option you want. If the answer is "do both", you need a conversation, not another email.
• It isn't legal advice. The landlord prompt creates a clear written record, but tenant rights, repair deadlines and options such as withholding rent vary by place. If the landlord still doesn't respond, check your local tenant rules or a tenant advice service before you take the next step.
• It doesn't know your facts. The chatbot fills gaps with plausible details. Treat any date, delay or deadline in the draft that you didn't give it as wrong until you've checked it.
• It can't read the relationship. A note that suits a neighbor you've never met may feel stiff to one you chat with every week. You know the person and the chatbot doesn't, so adjust the tone yourself.
• It isn't for emergencies. A gas smell, no heat in freezing weather, flooding or any risk to safety calls for a phone call to the right service now, not a polite email.

Related reading

• Stop Typing, Start Asking — full first chapter, free, no email required
• Full contents and what is included
• Three documents you signed without reading
• Three put-off emails, each under 120 words
• All Avalon Store products