Pro free for 30 days.No card.Start free →

Write business emails that get answered: a practical guide

A practical guide to writing business emails that get answered: build a subject line that works, lead with the request, make replying easy, follow up without nagging, and use a pre-send checklist. Written for small business owners and teams.

By WorkBOS Content Desk8 min read
Hand typing on a laptop keyboard at a work desk (Photo by councilcle on Pixabay)
Photo: councilcle / Pixabay

Most business emails do not fail because they are rude or badly spelled. They fail because the reader cannot tell, in the first five seconds, what you want and by when. The message sits in an inbox next to fifty others, gets marked "later", and quietly dies. You then send a second email asking if they saw the first one, and the cycle repeats.

This guide shows how to write business emails that get answered: how to build a subject line that works, how to open with the request, how to make the next step obvious, and how to follow up without sounding annoyed. Everything here is practical and takes seconds to apply. It is written for small business owners and teams who write to clients, suppliers and colleagues every day.

Start with the one thing you want

Before you type a word, finish this sentence: "After reading this, I want the person to ___." If you cannot complete it, you are not ready to write the email. You may need a call, a document or more thinking first.

Decide whether email is the right channel

Email is good for requests that need a written record, a decision someone can think about, or a message to someone outside your company. It is poor for a quick yes or no, an urgent problem, or anything emotional. A short chat message or phone call will usually beat three emails of back and forth. Sensitive news, such as a complaint or bad news about a project, is better discussed live and followed with a short written summary.

One email, one topic

Colorado College's email guide advises focusing each email on one topic or request, and that matches what small teams see in practice. When you bundle three unrelated questions, the reader answers the easiest one and forgets the other two. If you have three requests, either send three emails with clear subjects or list them as numbered questions in a single message.

Write a subject line that does the work

The subject line is the most-read part of your email. Treat it like a label on a folder.

What a good subject line contains

  • The topic, in specific words ("Invoice 1042", not "Question").
  • The action you need, such as approve, review, reply or "FYI, no reply needed".
  • The deadline, if there is one.

Colorado College's email guide suggests keeping subject lines to about seven words or fewer, stating the purpose and saying so when a response is needed. Carnegie Mellon's communications team gives a similar rule of thumb of roughly 30 to 50 characters so that mobile screens do not cut the line off.

Before and after

| Weak subject | Stronger subject | |---|---| | Quick question | Approve quote #218 by Thursday? | | Meeting | Moving Friday's client call to 3 pm | | Update | Website launch: two decisions needed | | Following up | Contract draft: waiting on your sign-off | | Hi | No reply needed: June report attached |

Notice that the stronger versions would still make sense three weeks later when someone searches the inbox. That is a quiet benefit: good subjects double as filing labels.

Open with the request, then add context

Readers skim. Put the point first, and the background after. A simple structure works for nearly every business email:

  1. Greeting by name.
  2. The ask or the news in one or two sentences.
  3. The context the reader needs to decide, in a short paragraph or three bullets.
  4. The next step, with a date, and who does it.
  5. A sign-off with your name and a way to reach you.

Keep it short, but not cryptic

Carnegie Mellon's guide recommends that non-newsletter emails run roughly 250 to 500 words, about one to two minutes of reading, and that the main call to action sit near the top. For most everyday business emails, 80 to 150 words is plenty. If you need more, link to a document or use short headed sections so the reader can jump to what matters to them.

Write in plain language

US federal guidance on plain language starts from a simple idea: write for the specific audience who will read the page. Apply that to email. Use short sentences, everyday words and active voice. Say "please send the signed form by Friday" rather than "it would be appreciated if the executed documentation could be forwarded at your earliest convenience". Skip the jargon unless you know the reader uses it too.

Example: a request that gets answered

Subject: Approve quote #218 by Thursday? Hi Dana, could you approve the attached quote for the new shelving by end of day Thursday? That lets us hold the delivery slot on the 14th. Quote total is $4,380, which includes installation. The only open choice is the oak or the pine finish (oak adds $310). If Thursday is tight, reply with "need more time" and I will ask the supplier to hold the slot until Monday. Thanks, Sam

It states the ask, gives a deadline, offers a quick path to answer, and fits on a phone screen.

Make replying easy

People answer emails that are cheap to answer. Lower the effort wherever you can.

Ask closed questions when you can

"Does Tuesday at 10 or Wednesday at 2 suit you?" gets a faster reply than "When are you free?" Offer two or three options, a default ("I will assume Tuesday unless I hear otherwise"), or a simple choice the reader can answer with one word.

Name who should act

If you write to four people, the request belongs to nobody. Put the person responsible in the first line ("Priya, can you confirm..."), and use cc only for people who need to know, not to act. Agree with your team on when to use reply-all; most replies do not need to reach everyone.

Say when no reply is needed

An "FYI, no reply needed" line saves the reader a decision and your inbox a "thanks!" chain. The opposite also holds: if you do need an answer, say by when.

Colorado College's guide recommends descriptive link text instead of "click here" and making sure recipients can open the linked file without hitting a permission wall. A link to a document the reader cannot open is a guaranteed non-answer. Where possible, share a link to the live file instead of attaching copies, so everyone is looking at the latest version.

Follow up without nagging

Silence is rarely personal. People are busy, the email was buried or the question needs thought. A calm follow-up is part of the process, not an insult.

A simple follow-up rhythm

  • Wait a reasonable time. Two or three working days for routine requests, one day for urgent ones.
  • Reply on the same thread, so the original context is right there.
  • Restate the ask in one line and add anything new that might unblock it.
  • Offer an easy exit: "If this is no longer a priority, just tell me and I will close it on my side."
  • Change channel on the second try if it matters: a short call or chat message often resolves what two emails could not.

For a longer treatment of chasing leads and clients without being pushy, see Sales follow-up that wins deals without nagging.

A checklist before you press send

  1. Does the subject line state the topic, the action and the date?
  2. Is the main request in the first two sentences?
  3. Is there only one topic or request (or a numbered list)?
  4. Is it clear who should act and by when?
  5. Would the message make sense if read on a phone?
  6. Are links working, attachments needed, names spelled correctly?
  7. Have you removed anything you would not want forwarded?

Common mistakes

  • Burying the request in the fourth paragraph.
  • Vague subjects like "Question" or "Hello".
  • Writing a mini-essay when a chat message or call would do.
  • Reply-all by reflex, filling people's inboxes with noise.
  • Asking open questions that require the reader to do the planning for you.
  • Writing when angry. Draft it, wait an hour, then decide whether it needs to be an email at all.
  • Following up the same day, then again, with growing irritation.
  • Skipping the proofread. A misspelled name or the wrong date costs more trust than any clever phrase gains.

Where WorkBOS fits

Email works best when it is one channel among several, not the place where everything is stored. In WorkBOS, decisions and project updates can live next to the tasks and client records they belong to, so you can link to the source instead of retyping context, and quick questions can go to chat rather than a long thread. Automations can send routine reminders such as overdue invoice nudges, so you are not chasing by hand. If you want the broader picture of keeping work in one place, read how to run your business from one platform, compare pricing (there is a free plan for up to five users), or browse the docs. For a related habit, see asynchronous communication that works for small teams.

Frequently asked questions

Q: How long should a business email be? A: Short enough to read in one or two minutes. Carnegie Mellon's guidance puts non-newsletter emails at roughly 250 to 500 words at most, and everyday requests are usually well under 150. Put the main point at the top so a skim still works.

Q: What makes a good subject line? A: It states the topic, the action you need and any deadline, in about seven words or fewer. "Approve quote #218 by Thursday?" beats "Quick question" because the reader knows what to do before opening it.

Q: How soon should I follow up if nobody replies? A: For routine requests, wait two or three working days, then reply on the same thread, restate the ask in one line and offer an easy way to say no or "later". For urgent items, follow up after one day and switch to a call or chat.

Q: Should I use cc and reply-all? A: Use cc for people who need to know, not people who need to act. Agree on a team habit for reply-all so that replies reach only those who need them.

Q: When is email the wrong tool? A: For quick questions, urgent issues and sensitive conversations. Use chat or a call, then send a short written recap if you need a record.

Sources are linked in the text above: Colorado College, Carnegie Mellon University, Digital.gov.

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →