Out of Office Message Examples: 22 Copy-Paste Templates for Every Scenario

You came here for templates. They’re below. But first, the safest default for most people:

Subject: Out of office until [return date]

Hi,

Thanks for your email. I’m out of the office from [start date] and back on [return date]. I’ll reply when I return.

For anything urgent before then, please contact [colleague’s name] at [colleague’s email].

Best,
[Your name]

Copy that, fill in three fields, you’re done. The rest of this guide is for everyone who wants something better. Sick leave that doesn’t overshare. Parental leave that runs for six months. The OOO your support@ inbox should never send. The setup steps in Gmail and Outlook. The 14 things people forget to switch on. All of it.

A quick word on why I care about this

In 2006 I went to Argentina for a few months. Almost every internet café and ISP I tried blocked my outbound email. I couldn’t reply to clients, couldn’t tell anyone I was out of pocket, couldn’t even fire a working autoresponder. I came home, built SMTP2GO to fix the sending problem for everyone else, and I’ve spent the 20 years since watching what actually happens to business email when people go on leave.

So when I say a good OOO is mostly about the boring stuff (dates, backup contact, response window, privacy), it’s because I’ve seen the messy version. The misspelled colleague email. The “I’ll be in Bali” out-of-office that turned into a phishing call to the CFO. The support inbox auto-replying to every newsletter on the planet for two weeks. None of that is hypothetical.

Anyway. Templates.

Jump to a template

• Quick-pick by situation
• The 22 templates
• Subject lines
• Internal vs external
• Privacy: what an auto-reply actually exposes
• Out of office for support and shared inboxes
• How to set one up (Gmail, Outlook, Apple Mail, Slack, Teams)
• Before-you-leave checklist
• Common mistakes
• FAQs

What makes an out-of-office message actually work

Five elements. That’s it.

A clear greeting that sets the tone. The dates you’re away, including the return date (an actual date, not “next week”). Whether you’ll check email at all. A backup contact, if you have one and they’ve said yes. A short sign-off.

Everything else is optional. Some scenarios need more (parental leave with multiple project owners, holiday closures for a whole company, a support inbox that needs to route by topic). Most don’t.

Things you don’t need to say: where you’re going, why you’re sick, whose wedding you’re at, what time your flight lands. People sometimes feel the urge to explain. Resist it. An OOO is automated, which means it fires back to anyone who emails you. Including spam. Including phishing reconnaissance. Including the mailing lists you forgot you’re on. We’ll get to that in the privacy section.

Which OOO should I use?

The 22 templates

Pick one. Replace bracketed fields. Read it through once before you save (this is where typos happen, and your OOO goes to everyone, including your CEO).

1. The default

For most short absences when you don’t want to think about it.

Subject: Out of office until [date]

Hi,

Thanks for your email. I’m out of the office from [start date] until [return date] and will reply when I return.

For urgent matters, please contact [colleague’s name] at [colleague’s email].

Best,
[Your name]

2. Short and simple

For when you’re only away a day or two and don’t want a backup contact.

Subject: Away until [date]

Hi,

Thanks for your message. I’m out until [return date] and will reply when I’m back.

Best,
[Your name]

3. Vacation

A normal vacation. Notice what’s not in it: location, length-of-flight, the name of the resort. None of that helps the sender.

Subject: On leave until [date]

Hi,

Thanks for your email. I’m on annual leave from [start date] to [return date] and won’t be checking messages.

For anything urgent, please contact [colleague] at [email]. Otherwise, I’ll reply when I’m back at my desk.

Best,
[Your name]

4. Vacation with a backup contact you’ve actually briefed

The version most people don’t bother writing, but it’s the one that prevents the post-vacation pile-up.

Subject: Out of office until [date]: [colleague] is covering

Hi,

I’m out of the office from [start date] until [return date]. [Colleague’s name] is covering my work in my absence and is up to speed on current projects. For anything time-sensitive, please reach out to them at [colleague’s email].

I’ll reply to other messages on my return, in the order they came in.

Best,
[Your name]

5. Sick leave (privacy-safe)

You owe nobody a medical update. Keep it short.

Subject: Out of office

Hi,

Thanks for your message. I’m unexpectedly out of the office and will respond to your email when I return.

For urgent matters, please contact [colleague] at [email].

Best,
[Your name]

A note: don’t put “sick” in the subject line. It tells every spam-screening tool, every CRM, and every nosy stranger that you’re unavailable for a reason worth probing.

6. Personal leave (privacy-safe)

For anything you don’t want to explain.

Subject: Out of office until [date]

Hi,

Thank you for reaching out. I’m on personal leave until [return date]. I’ll respond to your message after my return.

If you need help before then, please contact [colleague] at [email].

Best,
[Your name]

7. Parental leave

For longer absences, give people a routing map. They’ll need it.

Subject: On parental leave until [date]

Hi,

Thanks for your message. I’m on parental leave until approximately [return month, year]. I won’t be checking this inbox during that time.

In my absence, here’s who to reach:

For [Project / function]: [name] at [email]
For [Project / function]: [name] at [email]
For everything else: [name] at [email]

I’ll be in touch when I’m back.

Best,
[Your name]

The trick with parental leave is “approximately.” Don’t pin a return date you can’t honor. Babies don’t ship on time.

8. Bereavement

Short. Honest. No details required.

Subject: Out of office

Hi,

I’m out of the office due to a family bereavement and will respond to your email on my return.

Please contact [colleague] at [email] for anything that can’t wait. Thank you for your understanding.

[Your name]

9. Business travel

The trick is setting expectations on response time, not pretending you’re offline.

Subject: Traveling for work until [date]

Hi,

Thanks for your email. I’m traveling for client meetings from [start date] until [return date], with intermittent email access. Replies may be delayed by a day or two.

For anything urgent, please contact [colleague] at [email].

Best,
[Your name]

10. Conference or event

Slightly different. Some people in your contact list might be at the same conference. Tell them where to find you.

Subject: At [event name] until [date]

Hi,

Thanks for your message. I’m at [event name] from [start date] until [return date], so replies will be slower than usual.

If you’re also attending, find me at [booth / session / hotel lobby] or message me on [LinkedIn / Slack].

For anything urgent, please contact [colleague] at [email].

Best,
[Your name]

11. Limited email access

For when you’ll glance at messages but can’t promise replies.

Subject: Limited email access through [date]

Hi,

Thank you for your email. I’m out of the office with limited email access from [start date] until [return date]. I’ll respond when I can, but expect delays.

For urgent matters, please contact [colleague] at [email].

Best,
[Your name]

12. Completely offline

Subject: Offline until [date]

Hi,

Thanks for your email. I’m offline from [start date] until [return date] with no access to messages.

For urgent matters, please contact [colleague] at [email]. For anything else, I’ll reply when I’m back.

Best,
[Your name]

13. One-day or half-day

Most people don’t bother for this. They probably should. A half-day silence in someone else’s inbox feels longer than it is.

Subject: Out of office today

Hi,

Thanks for your email. I’m out of the office today and will respond first thing tomorrow.

For anything urgent, please contact [colleague] at [email].

Best,
[Your name]

14. End-of-day or after hours

For senders who email you at 11pm and expect a same-night response.

Subject: Auto-reply: I’ll see this in the morning

Hi,

Thanks for your message. I’ve finished for the day and will respond first thing tomorrow ([next working day]).

If your message is genuinely urgent, please contact [colleague] at [email or phone].

Best,
[Your name]

This isn’t an OOO in the strict sense. It’s a sanity-preserver. Some teams set it as a recurring rule for evenings and weekends. Worth considering.

15. No backup contact available

When there’s no one to refer to. Be honest about timing.

Subject: Out of office until [date]

Hi,

Thanks for your email. I’m out of the office from [start date] until [return date] and don’t have someone covering during that time.

I’ll work through messages in the order they came in when I return, so please expect a [3-5 day] response window once I’m back.

Best,
[Your name]

16. Internal team OOO

Internal messages can be more specific. Coworkers want to know what to do, not what to feel.

Subject: OOO [dates]: who owns what

Hey team,

I’m out from [start date] to [return date]. Here’s coverage:

[Project A]: [name] is acting on decisions, ping in #[slack-channel]
[Project B]: [name] has the brief, status doc here: [link]
Open POs / approvals: [name] is approver until I’m back

Slack DMs will route to [name]. Anything I miss, I’ll catch up on my first day back.

See you on [return date].
[Your name]

17. External-only OOO

The external-only version of the same absence. Strip out anything internal.

Subject: Out of office until [date]

Hi,

Thanks for getting in touch. I’m out of the office until [return date].

For matters that can’t wait, please contact [colleague’s first name] at [colleague’s email]. Otherwise I’ll respond when I’m back.

Best,
[Your name]

If you use Gmail or Outlook, you can run two messages side by side, one for people inside your domain and one for everyone else. Use it.

18. Company-wide holiday closure

A whole-company message. This is one of the few cases where a brand voice can actually land.

Subject: [Company] is closed [dates]

Hi,

Thank you for contacting [Company]. We’re closed for [holiday] from [start date] and will reopen on [return date].

If you need urgent support during the closure, please [submit a ticket at link / email support@company.com / call our emergency line]. We monitor that channel even on closure days.

For non-urgent enquiries, we’ll respond in the order received once we’re back.

Thanks for your patience,
The [Company] team

19. Unexpected or emergency absence

When you don’t know your return date and don’t want to lie about it.

Subject: Out of office

Hi,

I’m out of the office unexpectedly and not sure when I’ll be back at my desk.

Please contact [colleague] at [email] for anything urgent. I’ll respond to other messages once I’ve worked through the backlog.

Thanks for your patience,
[Your name]

20. Leaving the company

Don’t oversell the new job. People are emailing your old address; the polite move is to forward them, not pitch them.

Subject: Out of office: I’ve moved on from [Company]

Hi,

Thanks for your email. I’m no longer at [Company] as of [date].

For [function or topic], please contact [name] at [email]. For HR or account matters, [Company]’s general inbox is [email].

You can reach me personally on LinkedIn if you’d like to stay in touch: [link].

Best,
[Your name]

A practical note: many companies will eventually disable a departed employee’s mailbox, or set up a company-wide auto-reply that redirects senders. If yours doesn’t, talk to IT before your last day. A dead inbox is a worse experience than a clear handoff.

21. Customer support / shared inbox

This is where most generic OOO advice falls apart. A support@ inbox isn’t one person; it’s a queue. The auto-reply should set ticket expectations, not pretend a person is on holiday.

Subject: We’ve got your message: [ticket reference]

Hi,

Thanks for contacting [Company] Support. We’ve received your message and our team will respond within [SLA: e.g., 4 business hours / 1 business day].

Our hours are [time zone, days, hours]. Outside those hours, we still monitor for critical incidents.

For account or billing issues, please include [account ID / order number] if you haven’t already, so we can find your record fastest.

If this is a security or outage report, please mark the subject “URGENT” and we’ll route it to the on-call engineer.

Thanks,
[Company] Support

A note for support team leads: don’t auto-reply to mailing lists, newsletters, or marketing senders. Your auto-reply gets a Precedence: bulk or Auto-Submitted header, but plenty of inboxes will still bounce or loop. We see this on the SMTP2GO platform when a support inbox auto-replies into a vendor newsletter and the newsletter platform replies right back. Mail loops are no fun.

If you’re running support@ on SMTP2GO, our support documentation covers how to set autoresponders that respect RFC 3834 (the standard for auto-submitted email). Worth a read before your team goes on holiday.

22. Sales inbox during absence

Subject: Out of office: deal continuity contact

Hi,

Thanks for reaching out. I’m out of the office until [date]. If you’re in the middle of an active conversation with me, [colleague] has the context and can move things forward in my absence.

Reach [colleague] at [email] or book directly: [calendar link].

If you’re hearing from us for the first time, we’ll be back in touch when I return.

Best,
[Your name]

10 subject lines that work

Subject lines often get ignored in OOO writing. They shouldn’t. Many email clients show the subject before the body, and a clear one tells the sender what they need in two seconds.

1. Out of office until [date]
2. Out of office: [Your name] returns [date]
3. Auto-reply: away until [date]
4. On leave through [date]
5. Limited email access until [date]
6. Offline until [date]
7. [Company] is closed [dates]
8. At [event] until [date]
9. Out of office: [colleague] is covering
10. We’ve received your message: [ticket reference]
    Avoid: anything with “VACATION!!!”, anything that names where you’re going, anything that uses “Re:” (your sender will think you’ve actually replied).

Internal vs external out-of-office messages

Gmail and Outlook both let you set two messages: one that fires to people inside your organization, one for everyone else. Almost nobody bothers with the second version. That’s a mistake.

Your colleagues need to know who’s covering, which project doc to read, which Slack channel to post in, who has approval authority while you’re away. Useful for them, dangerous for everyone else.

Your external contacts need three things: that you got the email, when you’ll reply, and who to reach in the meantime. The less detail beyond that, the better. They don’t need your Slack workspace name, your project codename, or your CEO’s first name. Each of those is a small piece of social-engineering ammunition. Phishers do their homework.

So: write the internal version with the detail your team needs to keep things moving. Write the external version short, neutral, and professional. Tools like Gmail’s vacation responder (“only send a response to people in my Contacts” toggle) and Outlook’s “Inside My Organization” tab make this easy. Walkthroughs are in the setup section below.

A small SMTP2GO opinion that probably saves more grief than people realize: the best OOO setups treat the internal-only message as a team document. Update the team Slack channel link. Update the project doc URL. If your handover doc moves, your auto-reply should move with it. We’ve seen too many onboarding-style problems caused by an OOO pointing to a doc that doesn’t exist anymore.

What an out-of-office message actually exposes (the section everyone else skips)

This is the part most generic OOO articles get wrong. They tell you not to share your travel itinerary and call it a privacy section. The actual concern is bigger.

When your auto-reply turns on, it fires back to every email that arrives in your inbox. Every spam attempt. Every phishing probe. Every newsletter, billing reminder, password-reset notification, and unsolicited cold outreach. If your message includes your job title, your direct phone number, your alternative contact’s full name and email, and the exact dates you’re away, you’ve just handed a phisher a starter kit.

Real-world examples of what attackers do with OOO information:

• CEO-impersonation phishing. Your OOO says you’re at a conference in Singapore until Friday. By Tuesday, your CFO gets a “wire request” from someone pretending to be you, claiming you’re stuck without phone access. This works more often than it should.
• Backup-contact spoofing. Your OOO names a colleague. The phisher then emails that colleague from a lookalike domain pretending to be you, with context they couldn’t have known otherwise.
• Verification harvesting. Some attacks just probe whether an inbox is monitored. An auto-reply that fires confirms the address is real, active, and unmonitored for a specific window.
  You don’t need to be paranoid. You need to be brief.

Practical rules I’d actually follow:

Use first names only for backup contacts in external messages. The phisher gets less to work with.

Skip the personal phone number. A backup contact’s email is enough. If something is genuinely urgent enough to warrant a phone call, the sender will figure it out from your company’s main line.

Don’t name the city or country you’re traveling to. Use “out of the office” or “on annual leave.” The dates are the only piece of routing information most people actually need.

Don’t put job-specific keywords or project codenames in an external OOO. Save the detail for the internal version.

If you’re in finance, legal, IT security, or another role where impersonation is high-value: consider running a more neutral message than your usual one when you’re away. Some teams use a generic “I’m out, please contact [shared inbox]” so an attacker can’t tell that the principal is unavailable.

This isn’t paranoia. It’s normal email hygiene from the same playbook that says use SPF, DKIM, and DMARC, set up proper email compliance, and don’t post your support inbox in plain text on a high-traffic website. An out-of-office is a small attack surface; it’s also one you can completely close in 30 seconds.

Out of office for support inboxes, shared mailboxes, and team aliases

This is a corner of the OOO world almost nobody writes about. It’s the corner SMTP2GO sees most of, because half the email traffic on our platform is transactional and team-routed rather than personal.

A shared inbox isn’t on holiday. The team behind it is. The auto-reply should reflect that.

Things to think about before your support team rolls out an auto-reply:

Don’t auto-reply to bulk mail. Set the autoresponder to skip senders flagged as bulk, mass-mailed, or auto-submitted. Most email platforms honor the Precedence: bulk and Auto-Submitted: auto-generated headers. RFC 3834 covers the standard. If you ignore this, your support inbox sends a “thanks for your message” to every newsletter on the planet, and you’ll burn sender reputation fast.

Cap your loop count. Two systems both auto-replying to each other is a mail loop. Your platform’s autoresponder should fire once per sender per N days (most allow this; check your settings). Loops are the most common cause of “why is my support@ blacklisted?” tickets, in my experience.

Tell the sender what to do, not just that you exist. If you have a ticketing system, include the ticket reference and a link to track it. If you’re a small team, give an SLA window. If certain topics route differently (billing vs. technical), say so. The OOO is a chance to triage at the gate.

Plan for holidays as a system, not as an inbox. Holiday closure messages should also adjust your support@ SLAs, your in-app help widget, and your status page note. The OOO is one channel. Senders will check three.

A real example. StoredTech has used SMTP2GO since 2011 for everything from phone systems to copier alerts. When their support inbox goes into a holiday closure window, the auto-reply directs senders to a self-service knowledge base and a monitored emergency channel. That works because the routing is deliberate, not improvised the morning of a long weekend. [VERIFY: confirm StoredTech specifics from customer success page before publishing]. The point is: think of the OOO as a piece of your support architecture, not a postscript.

If you’re sending transactional or device-generated email through SMTP2GO (printers, security cameras, ERPs, CRMs, anything machine-to-machine), our SMTP relay guide covers how to keep auto-reply traffic separate from your transactional stream. Mixing them is a classic deliverability mistake.

How to set up an out-of-office message

The mechanics. Quick reference for the platforms people actually use.

Gmail

1. Open Gmail. Click the gear icon (top right), then See all settings.
2. Stay on the General tab. Scroll to Vacation responder at the bottom.
3. Choose Vacation responder on.
4. Set first day, last day (optional but recommended), subject, message.
5. Toggle Only send a response to people in my Contacts if you want a privacy-safe external default. Toggle Only send a response to people in [your-domain] for internal-only. Use both if you want different messages internal vs external (you’ll need to repeat the process).
6. Click Save Changes.
   A small detail people miss: Gmail’s vacation responder only sends one reply per sender per four days. If someone emails you twice in that window, they get one auto-reply. That’s by design and stops mail loops.

Outlook (Microsoft 365 / desktop)

1. Open Outlook. Go to File > Automatic Replies.
2. Choose Send automatic replies.
3. Tick Only send during this time range and set start and end.
4. Write your message in the Inside My Organization tab.
5. Click the Outside My Organization tab. Tick the box at the top to enable. Write your external message (or leave it off and only internal senders get one).
6. Choose Anyone outside my organization vs My Contacts only. Pick the second if you want privacy.
7. Click OK.
   Older Outlook versions and Outlook on the web vary slightly. The principle is the same. If you’re on Outlook Web, the equivalent is Settings > Mail > Automatic replies.

Apple Mail

Apple Mail itself doesn’t have a built-in auto-reply for IMAP accounts. The auto-reply runs on the mail server, not the client. If your work email is Gmail or Microsoft 365 routed into Apple Mail, set the auto-reply in Gmail or Outlook on the web. If you’re on iCloud Mail:

1. Go to iCloud.com, sign in, open Mail.
2. Click the gear icon and choose Preferences (or Settings).
3. Open the Vacation tab.
4. Tick Automatically reply to messages when they are received, set the dates, write the message, click Done.
   

   Slack

Slack doesn’t have a true OOO, but it does have status. Set it.

1. Click your profile photo (top right), then Set yourself as away or Set a status.
2. Pick a preset like Vacationing or write a custom one with your return date.
3. Set Clear after to a specific date.
4. Optionally turn on Pause notifications for the duration.
   For teams that use Slack as a primary channel, mention this in your email OOO so senders know not to also ping you on Slack.

Microsoft Teams

Teams has an actual OOO that integrates with Outlook.

1. Click your profile photo > Set status message.
2. Tick Show when people message me, write the message, set a clear-after date.
3. Alternatively: Settings > General > Out of Office > Schedule to sync with your Outlook auto-reply.
   The second option is the one most people miss. Setting Outlook and Teams together means you’ve covered both inbound channels without remembering to do it twice.

The before-you-leave checklist

I’ve been writing this article from memory of the things that go wrong. Here’s the version that catches most of them.

The day before you leave:

• Confirm dates. Double-check the year on your auto-reply (people set messages with last year’s dates more often than you’d think).
• Confirm your backup contact has actually said yes and is briefed on what they might receive.
• Update the shared docs your auto-reply references. If the link points to a stale Notion page, fix it now.
• Set the Slack status with the same return date as your email.
• Set the Teams status if you use it.
• Update your calendar to show “Out of Office” so people scheduling around you can see it.
• Trigger a test email from a personal address to confirm the auto-reply actually fires.
• Read the body of the auto-reply out loud. Typos in colleague names and email addresses are the #1 cause of cleanup work on return.
  The day you return:
• Turn off the auto-reply (Outlook and Teams may auto-disable on the end date; Gmail won’t unless you set one).
• Update your status back.
• Schedule a buffer block on your calendar before client meetings start up again. An hour to triage inbox before the first call goes a long way.

Common mistakes worth avoiding

The patterns I see again and again:

The location overshare. “I’ll be in Tuscany for two weeks.” That sentence has saved zero people any time and given attackers exactly what they need to impersonate you. Drop the location.

The forced humor. A funny OOO can work if your role is informal and your audience is too. It doesn’t work if the next email in your queue is from a procurement officer, a regulator, or a grieving customer. If you have any doubt, default to neutral.

The wrong year. This is so common it’s almost a tradition. People set up a “Out of office July 14-21” auto-reply that fires for last year’s dates because they edited an old draft. The fix: always read the start and end dates out loud before saving.

Promising a same-day response on return. “I’ll respond to all messages on my first day back.” You won’t. Set the expectation honestly.

Listing a colleague without asking. Putting someone’s email in your OOO without their permission is a quiet way to make them dislike you. Ask first. Tell them what they might receive. Give them context.

Auto-replying from a shared inbox without throttling. Covered above in the shared inbox section. It’s the fastest way to nuke your sender reputation.

Forgetting to turn it off. Outlook and Teams have date-based shutoff. Gmail and many other platforms don’t. Set a calendar reminder for your first day back to manually turn it off if your platform doesn’t.

Including a phone number you’ll regret giving out. Once it fires once, your number is out there. Be deliberate.

FAQs

How long should an out-of-office message be?

Three to five sentences for most situations. Long enough to include greeting, dates, backup contact, sign-off. Short enough that the sender reads the whole thing.

Should I say why I’m out of the office?

Generally no, especially in external messages. “Out of the office” or “on leave” is enough. Specifics open you up to phishing risk and unnecessary follow-up questions.

Should I include my phone number in my out-of-office message?

I wouldn’t. Your number gets handed to anyone who emails, including bots and scrapers. If a backup contact’s email isn’t enough for genuinely urgent matters, route through a company main line instead.

Should internal and external out-of-office messages be different?

Yes. The internal one can be detailed (project ownership, Slack channel, shared docs). The external one should be short and neutral. Gmail and Outlook both make this easy in the same settings panel.

What should I write if I don’t have a backup contact?

Be honest. Set a realistic return-response window (3-5 business days is reasonable for most roles). See template #15 for the exact wording.

Is it OK to use a funny out-of-office message?

Sometimes. It depends on your role, your industry, your audience, and whether your sense of humor lands in writing. If you have any doubt, default to neutral. You can always be a normal person again on the way back.

How do I write an OOO for sick leave without sharing personal details?

Use template #5. Don’t put “sick” in the subject. Don’t describe symptoms. Don’t promise a return date you might miss.

How do I set an out-of-office reply in Gmail or Outlook?

Step-by-step instructions are in the setup section. Both take under two minutes. Don’t forget to set the end date in Outlook (it’ll auto-disable), and don’t forget to manually turn off Gmail’s responder when you return (Gmail won’t).

Should my support inbox have an auto-reply?

Yes, but a different kind. A support auto-reply should set ticket expectations, route by topic, and skip bulk senders to avoid mail loops. See the shared inbox section for the longer version.

Can my out-of-office message hurt my email deliverability?

For a personal inbox, no. For a shared inbox or a system that fires high volumes of auto-replies into spam-like traffic, yes. Loops, reputation hits, and FBL complaints are all real. If you’re sending serious volume, talk to your email provider. We’ve written about common deliverability issues and how to avoid them.

A small ask before you go

If you’re running business email for a team (whether that’s a 12-person agency, a 5,000-person enterprise, or a school district running printer-to-email alerts), the OOO is a tiny piece of a bigger problem. The bigger problem is reliable, well-routed business email that doesn’t end up in spam folders, doesn’t loop, and doesn’t expose data it shouldn’t.

That’s what we do at SMTP2GO. ISO 27001 certified. GDPR compliant. M3AAWG members. Real humans answering support tickets 24/7 from Christchurch. Trusted by businesses sending anywhere from a few hundred to over a million emails a month, including teams like Group IMD (who scaled from 10K to 1M+ emails a month over six years with us) and GlaxoSmithKline (time-critical manufacturing notifications).

If you want to see how we run, our product tour is the quickest path. If you’re comparing providers, the comparison page lays it out. And if you’d rather just hear from people who’ve made the switch, the customer success stories are honest about what we get right and what’s still rough at the edges.

Either way, enjoy the time off.

About the author

Charlie Abrahamson

CEO at SMTP2GO • Website

Charlie is CEO and co-founder of SMTP2GO. He started the company in 2006 after a trip to Argentina left him locked out of his own email (every internet café and local ISP blocked his attempts to send). Twenty years later, SMTP2GO delivers email for businesses around the world from its Christchurch, New Zealand base. Charlie has personally configured SMTP relays, debugged deliverability incidents, and led migrations for senders ranging from small businesses to enterprises moving off AWS SES, SendGrid, Mailgun, and Postmark. SMTP2GO is ISO 27001 certified, GDPR compliant and an M3AAWG member.