To write an email to a support team, put the problem and one identifier in the subject line, then say what you need in the first sentence. Underneath, give three things: what happened, what you expected, and what you’ve already tried. Add the details they’d otherwise have to ask for, like an order or account number, the date, and a screenshot. End with one clear ask. That’s an email a support team can act on in one reply, instead of three.
This guide gives you that email as templates you can copy. Then it turns around. If you run a firm of two to five people, you probably have a support address of your own: a help@, info@ or support@ that two or three of you answer. The second half is how to run that address so you keep up with it. It covers routing, the automatic acknowledgment, and reply templates the whole team can share. Microsoft and Google settings were checked against their own help pages on October 4, 2026.
How to write an email to a support team
A support person reads your email once and decides what to do. Give them everything for that decision in the order they need it.
- A subject line that names the problem. “Invoice #4471 charged twice” beats “Help please.” Put an order, invoice or ticket number in it if you have one.
- What you need, first. One sentence. “I was charged twice for invoice #4471 and need one charge refunded.”
- What happened. The steps, in order, with dates and times.
- What you expected instead. This is the line people skip, and it’s often the one that settles it.
- What you’ve tried. It saves them suggesting it back to you.
- The details. The email on the account, the device or browser, the exact wording of any error message, and a screenshot.
- One ask, and how to reach you. A refund, a call back, a fix by a date. If you want a phone call, give the number and the hours.
Keep it to short paragraphs. If you have two unrelated problems, send two emails. Most support teams handle one issue per thread, and two problems in one email often get half an answer.
Tone matters less than you’d think, and calm still helps. A support person can’t fix the past. They can fix the next step, and a plain email gets them there faster. For more on the line that gets an email opened, see subject lines that get opened, and then answered.
Templates for an email to a support team
Copy one, fill the brackets, and delete any line that doesn’t apply.
Something isn’t working
Subject: [Product or account]: [what’s broken] since [date]
Hi,
Since [date], [what happens], and I need [what you need].
What I did: [steps, in order]. What I expected: [what should have happened]. What I’ve tried: [restart, another browser, reset, and so on].
Account email: [address] Device and browser: [details] Error message: “[exact wording]” A screenshot is attached.
Could you [the one ask] by [date, if it matters]? I’m at [phone] between [hours] if a call is quicker.
Thanks, [Name]
A billing or account question
Subject: Invoice [number]: [charged twice / wrong amount / question]
Hi,
I have a question about invoice [number], dated [date], for [amount].
[One or two sentences on what looks wrong and why.]
Could you [refund the duplicate charge / send a corrected invoice / explain the line for X]?
Account: [name and account email]
Thanks, [Name]
Asking for help with something new
This is the one to use when nothing is broken and you just need a hand.
Subject: Help setting up [feature] for [what you’re trying to do]
Hi,
I’m trying to [goal], and I’m not sure how to [the step you’re stuck on].
So far I’ve [what you’ve done or read]. Is there a guide for this, or could someone walk me through it?
Account email: [address]
Thanks, [Name]
Following up when nobody has answered
Reply on the same thread, so your first email and its details travel with it.
Subject: Re: [original subject]
Hi,
Following up on my email of [date] below. [The problem] is still happening, and [what it’s costing you, briefly].
Is there anything else you need from me? If this should go to a different team, could you pass it on or tell me where to send it?
Thanks, [Name]
Send it after the reply time the company promised, if it named one. If it didn’t, two business days is a fair wait for anything that isn’t urgent.
When you’re the support team
Now the other side. A small firm’s support address is rarely called “support.” It’s info@, hello@, office@ or the address on your website’s contact page. Clients, prospects and vendors all write to it. Two or three of you answer it, between the actual work.
Microsoft lists exactly this among the things its shared mailbox is for, in its own description:
Use shared mailboxes when multiple people need access to the same mailbox, such as for: Company information addresses. Support email addresses. Reception or front-desk mailboxes.
On Google Workspace, the same job is usually a Google Group set up as a Collaborative Inbox. Which kind of address fits a firm your size is laid out in team email when the team is two or three people. How two people work one address without answering the same message twice is in team email management.
What follows is the part specific to a support address. It’s three pieces of work you do once: ask for what you need, acknowledge every email, and write your replies ahead of time.
Ask senders for what you need
Everything in the first half of this guide is what you’d like to receive. Most people won’t send it unprompted. So ask, in the two places people look just before they write.
On your contact page, under the address, add a short line:
To help us answer in one reply, please include your name, your company, and what you need. If it’s about an invoice or a document, the number or the date helps.
In your automatic acknowledgment, which comes next, ask again for anything that’s missing.
This does most of your routing for you. An email that says “Invoice 2291” in the subject goes straight to whoever handles billing. An email that says “Hi” needs someone to read it first.
Routing the support address
At two to five people, routing is a short written list. It says which kinds of mail go to whom. Here’s a starting point to adjust.
| Kind of email | Who takes it | First reply by |
|---|---|---|
| Existing client, about their work | That client’s lead | Same business day |
| Billing, invoices, payments | Whoever runs the office | One business day |
| New inquiry or prospect | The owner, or whoever takes new work | One business day |
| Vendor, supplier, sales pitch | Whoever runs the office, or nobody | When convenient |
| Something urgent, or a complaint | The owner, whatever the topic | Within hours |
Two rules keep the table honest. Whoever opens an email that matches a row passes it to that row’s person, rather than answering because it’s in front of them. And anything that matches no row goes to one named person, so it never sits there waiting for a volunteer.
Moving mail between people once it’s routed is ownership. The habits that make it visible, like claiming a thread before you draft, are in one owner for every thread.
The automatic acknowledgment
An auto-reply tells the sender three things: the email arrived, when they’ll hear back, and what to do if it can’t wait. It buys you the hours in your table above. It also catches the email with nothing in it, by asking for what’s missing.
Here’s one to adapt.
Subject: We’ve got your email
Thanks for writing to [Firm name]. This is an automatic reply to let you know your message arrived.
One of us will reply within one business day. Our hours are [days and times, with time zone].
If you haven’t already, please send your name, your company, and any invoice or document number. It helps us answer in one go.
If it’s urgent, call us at [phone].
[Firm name]
Keep the promise one you can keep on a busy week, not your best week. “Within one business day” kept every time does more than “within the hour” kept most days.
On a Microsoft 365 shared mailbox, an admin sets it in the Microsoft 365 admin center. Microsoft’s steps are:
- Go to Teams & groups, then Shared mailboxes.
- Select the shared mailbox, then Edit under Automatic replies.
- Tick the box to send automatic replies to senders inside the organization, if you want those too.
- Enter the replies for people inside and outside your organization, then Save.
The reply is text only. Microsoft says, “You can’t add images, only text.”
On a Google Group or Collaborative Inbox, the setting lives on the group. Google’s help page says it needs the Owner or Manager role and a work or school account. Open the group in Google Groups, go to Group settings, then Email options, and fill in the Auto replies section. You can write separate replies for people inside and outside your organization. If the group moderates messages, Google notes that “an auto reply is sent only after a message is approved.”
Reply templates the whole team can use
Most support email asks one of a handful of things. Write those replies once, agree them, and everyone answers in the same voice. These are the examples of customer support emails people usually need first.
A person picks it up
Hi [name],
Thanks for this. I’m [your name], and I’ll be looking after it. I’ll come back to you by [day and time] with [what they’ll get].
[Your name]
You need more information
Hi [name],
Thanks for getting in touch. So I can sort this in one go, could you send [the one or two things you need]?
As soon as I have that, I’ll [next step].
[Your name]
It’s done
Hi [name],
[What you did], so [what’s now true for them]. [Anything they need to do, if anything.]
If anything still looks wrong, reply to this email and it’ll come straight back to me.
[Your name]
It’s taking longer than promised
Hi [name],
A quick update on [topic]. It’s taking longer than I said, because [the honest reason, in one line]. I now expect to have it to you by [date].
Sorry for the wait. I’ll write sooner if anything changes.
[Your name]
It belongs somewhere else
Hi [name],
Thanks for writing. [Who or what] handles this, and the quickest way to reach them is [address, link or number].
I’ve [forwarded your email / copied them in] so you don’t need to start over.
[Your name]
If something went wrong on your side, the reply needs more than a template. How to apologize by email covers what carries the repair.
Where to keep the templates
Templates in Gmail and Outlook belong to each person, not to the shared address. Microsoft says so plainly about its My Templates add-in in classic Outlook:
templates created with the My Templates add-in from the shared mailbox are only available to your account. Other users with access to the shared mailbox can’t view or edit the templates you create.
Gmail’s templates work the same way, saved in each person’s own account and turned on in Gmail’s advanced settings.
So keep one master copy where everyone can read it: a shared document or a pinned note. Each person loads the current set into their own templates. When you change a reply, change the master first, then tell the others. Without that, three people slowly drift into three versions of “we’ve got it.”
The sent folder you can’t see
On a Microsoft 365 shared mailbox, your replies go out under the firm’s name. Microsoft’s setup page says the email “appears to be from the shared mailbox, not from the individual user.” Microsoft also says a copy lands in your own Sent Items by default, not the shared mailbox’s. On a support address, that’s the gap that causes a second reply. Your colleague opens the thread, sees no answer, and writes one. The fix is a setting, and where your replies from the shared mailbox end up walks through it.
On Gmail, the equivalent questions are in how a Gmail team shares one address.
When the support address outgrows the mailbox
A shared mailbox or Collaborative Inbox carries a small firm’s support address for a long time. Some signs say it’s stopped carrying it:
- You’ve promised clients a response time in a contract and can’t show whether you met it.
- Customers write in about one thing several times a month, and you can’t see their history in one place.
- Routing has grown past what a short table can hold.
- Someone keeps a spreadsheet of open requests on the side.
That’s when a help desk or shared inbox tool earns its price. Shared inbox software: what it is and how to choose compares them. Many firms of two to five never get there, and alternatives to a shared inbox tool makes that case.
Point and the client who writes to you directly
Point connects each person’s own Gmail or Microsoft 365 account, one seat each. It isn’t the support address. Keep that in the shared mailbox or Collaborative Inbox that suits your firm.
Support mail doesn’t stay at support@, though. A client gets your reply from the shared address, then writes back to you by name next time. Or a colleague forwards you a thread to finish. That mail lands in your own inbox, between everything else.
There, Point reads it as it arrives and ranks it. A client who’s waiting on you sits near the top, above the newsletters. A short summary tells you what they need before you open it. Point can also draft your answer to that client, in the words you’d use. The draft sits ready for you. The client gets it when you’ve read it and pressed send. If you’d like it to handle more, you widen that one kind of action at a time. Seats and invites are in per-seat billing, and the rest is on the benefits page.
Common questions
How do I write an email to a support team?
Name the problem and an order or account number in the subject line. Say what you need in the first sentence. Then give what happened, what you expected, and what you’ve tried. Add the account email, the date, any error message and a screenshot. End with one clear ask and how to reach you.
How do I write an email to ask for support?
Say what you’re trying to do and where you’re stuck, in the first two lines. Mention what you’ve already tried or read, so they don’t send it back to you. Include your account email. Ask one specific question, such as whether there’s a guide or whether someone can walk you through it.
How do I write a professional email to my team?
Put the action and any deadline in the subject, like “Decision needed by Thursday: new client intake form.” Open with what you need from them. Keep the background to a short paragraph. If different people need to do different things, list each name with its task, so nobody has to guess.
Can you provide some examples of customer support emails?
The common ones are an automatic acknowledgment, a person picking up the request, a request for more information, a “this is done” reply, a delay update, and a redirect. Each one has a template above, under reply templates the whole team can use. Keep them short, name who’s handling it, and give a date for the next step.
How long should a support team take to reply to an email?
There isn’t one standard. What matters is that you name a time and keep it. For a small professional firm, a first reply within one business day is a promise most teams can keep. Say it in your automatic acknowledgment, so the sender knows what to expect.
Should a small firm’s support address be a shared mailbox or forwarded to everyone?
A shared mailbox or Collaborative Inbox keeps one copy of each email that everyone sees, so you can tell when it’s been answered. Forwarding gives each person their own copy, and nobody can see what the others did. For two or three people answering one address, a shared mailbox is usually the better fit.