Can a business email address contain an ampersand?
No. An ampersand (&) is not practical in a normal business email address. While the email standards define syntax that can include & in the local part, it is not reliably supported by the wider workflow. Customers cannot say or type it consistently, and most forms, CRMs and contact lists will reject it, alter it or interpret it as part of another syntax layer.
For a public-facing small business—even when the trading name includes "&" such as Smith & Co—prefer a simple role or person address that drops the ampersand, such as quotes@<short-name>.au or bookings@<short-name>.au, then test the exact setup before printing or publishing it.
Why an ampersand does not work in practice
RFC 5321 section 4.1.2 defines the normal SMTP mailbox local part using characters that do not include &. RFC 5322 section 3.2.3 permits & in a quoted-string local part, but that syntax is intended for internal or special cases, not a public business address.
Even when the standards permit it in a quoted local part, an ampersand address is not practical. Mail providers rarely create them. Website forms, booking tools, CRMs, accounting packages and imported contact lists often reject &, strip it or interpret it as an HTML entity, URL query delimiter or special character.
When speaking or reading the address, the ampersand is described as "and". Customers typically type and, n, or omit it entirely. The same workflow concerns that make giving an email address over the phone challenging are amplified when & cannot be reproduced reliably from speech.
What customers hear and type
Picture a business with the trading name Copper & Gum telling a customer on a noisy call: quotes&gum@example. The customer hears "quotes and gum at example dot ..." Do they type quotesandgum, quotes-and-gum, quotesgum, quotes&gum, or quotes-n-gum?
Now imagine the same address on a printed invoice, quote PDF or van sign. The & is visible, but it can look like a shorthand symbol or a special character. When a customer retypes the address from a mobile screen or physical paper, they may replace it with "and", drop it, use a hyphen, or assume it is not part of the address at all.
This variability does not mean every customer will mistype the address. It means there are several ways to interpret & where none would exist if the address were quotes@<short-name>.au instead. Compare this to the narrower concern around hyphens, underscores and spaces in business email addresses, where the character can be seen but may still be confused, missed or rejected.
Forms and business tools often reject or alter ampersands
Website contact forms, CRM imports, booking systems, accounting packages and quote generators often validate or normalise email addresses before storing them. An & may be rejected, stripped, HTML-encoded as &, URL-encoded as %26, replaced with "and", or split into separate parts if interpreted as a query delimiter.
The business may not see the alteration until a reply to a stored address bounces or goes missing. A customer who enters quotes&co@example into a website form may receive a confirmation message sent to quotesco@example, quotes-and-co@example or quotes&co@example, depending on how the form processed the input.
This is a different layer from the question of whether an apostrophe, plus sign or other special character may be valid. An ampersand has both technical syntax restrictions and widespread practical interpretation problems across web forms and business tools.
Trading name and email address are different
A business that trades as Smith & Co, Copper & Gum Electrical, or any name with "&" does not need to reproduce the ampersand in the email address. The trading name remains on the letterhead, website, business card, invoice PDF, quote footer and email display name. The email address is only the technical routing identifier.
Use a simpler role address—such as quotes@<short-name>.au or bookings@<short-name>.au—or a person address—such as mia@<short-name>.au—that drops the ampersand. The email display name can still show the full trading name: Smith & Co <quotes@<short-name>.au> or Mia Chen — Copper & Gum Electrical <mia@<short-name>.au>.
This separation keeps the public contact workflow simple without removing the business identity. For the wider naming choice, see this guide to professional email address formats for small business. For display name guidance, see what your business email display name should be.
Prefer a simple role or name address
For a public customer-facing business, use a simple role address (such as quotes@<short-name>.au or bookings@<short-name>.au) or a person address (such as mia@<short-name>.au) without &, spaces, quote marks or other special characters.
A role address does not create a shared mailbox or give several people access by itself. The routing rule, destination mailbox, staff login, shared access and storage policy are separate parts of the setup. The public address is only the visible entry point.
When choosing the format, prioritise what customers can hear, say and type consistently. Read the separate guide to common mistakes customers make when entering email addresses for the wider picture.
Run a harmless test before publishing
Before printing, publishing or giving out a public business address:
- Confirm that the provider can create or route the exact address without
&, quote marks or other special syntax. - Send harmless fictional content from an unrelated inbox and confirm that it reaches the intended destination.
- Enter the address into the real website, quote, booking, CRM and accounting workflows the business uses.
- Copy it from a PDF and a mobile screen. Check that the format remains visible and unchanged.
- Have someone who is not already familiar with the address hear it over a call and write down what they heard. Compare their version to the original.
- Record who owns the public address, routing rule and mailbox access. Set a retest trigger for any provider or configuration change.
This test proves only the exact route, provider and configuration tested at that time. It does not guarantee delivery or inbox placement.
The public address is only 1 layer. An ampersand-free address does not create a routing rule, mailbox, login, shared access, storage policy or permission to send from that address. Confirm mailbox access, storage, display name and reply-from behaviour separately.
Where Short Mail may fit
If your current public address is awkward to say, print or type—or if your trading name includes "&" and you want a clearer public email identifier—a Short Mail account manager can check whether a shorter matched .au address may fit and forward to the inbox you already use. Fit, availability, .au eligibility, setup requirements and provider compatibility are confirmed manually before anything changes.
The public address, routing, mailbox, access and storage remain separate parts of the setup. Sending permission and the From and Reply-To details customers see also require separate checks for your business.