Should you use a period in a business email address?

However, periods add friction when the address must be said over the phone, printed on vans or cards, or typed from memory. Customers may drop the dot, double it, or misplace it. For a public-facing small business, simple role addresses like quotes@<short-name>.au or bookings@<short-name>.au are often clearer, then test the exact setup before printing or publishing it.

When a period helps (firstname.lastname clarity)

RFC 5321 section 4.1.2 and RFC 5322 section 3.2.3 define the dot (.) as an allowed character in the normal SMTP mailbox local part. Most mail providers, forms and business tools support it without special syntax.

A period is useful when the business wants to separate a first name and last name visibly—such as mia.chen@<short-name>.au or sam.wright@<short-name>.au. This format is clearer than miachen@<short-name>.au and easier to parse than mia_chen@<short-name>.au or mia-chen@<short-name>.au for many readers.

The format does not guarantee that the address belongs to a specific person, that the mailbox is private, or that only the named person can send from it. The local part is only a visible identifier. Mailbox access, storage, display name and send-from permission are separate setup and policy questions.

Phone, print and typing friction

Picture Silverline Electrical telling a customer on a noisy call: mia.chen@<short-name>.au. The customer hears "mia dot chen at [short name] dot A U". Do they type mia.chen, miachen, mia..chen, or mia-chen?

Now imagine the same address printed on an invoice, quote PDF, business card or van sign. The period is visible, but it is small. On a mobile screen, in bright sunlight, or when photographed from a distance, the dot may be hard to see. When a customer retypes the address from printed or PDF text, they may miss the period, add a second one, or replace it with a hyphen or underscore.

This variability does not mean every customer will mistype the address. It means there are several ways to interpret or misplace a period where none would exist if the address were mia@<short-name>.au instead. Compare this to the friction around hyphens, underscores and spaces in business email addresses, where the character may be confused, missed or rejected.

Gmail historically ignores dots in the local part

For addresses ending in @gmail.com, Google historically treats dots in the local part as cosmetic. An email sent to mia.chen@gmail.com is delivered to the same mailbox as miachen@gmail.com or m.i.a.c.h.e.n@gmail.com. From Google's perspective, the dots are ignored when routing mail.

This behaviour is specific to Gmail's own @gmail.com domain and does not extend to custom domains hosted on Google Workspace or other mail providers. An address like mia.chen@<short-name>.au hosted with any other provider will treat the dot as significant. Removing or adding a dot changes the address.

This creates a subtle confusion. A customer who uses Gmail personally may assume that mia.chen@<short-name>.au and miachen@<short-name>.au reach the same mailbox, when in fact they are 2 different addresses. The business cannot assume that customers will remember or apply this provider-specific rule correctly.

Prefer simple role addresses when the address must be said or printed

For a public customer-facing business—when the address will be given over the phone, printed on vans, cards, invoices, quote PDFs or job sheets—prefer a simple role address like quotes@<short-name>.au or bookings@<short-name>.au without periods, hyphens, underscores or other punctuation.

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 the address is for internal or private correspondence—and the recipient list is stable—a period in a firstname.lastname format is generally fine. The friction only matters when customers must say, hear, type or copy the address frequently. For the wider naming choice, see this guide to professional email address formats for small business. For guidance on what customers see, read what your business email display name should be. For the phone workflow specifically, see this guide to giving an email address over the phone without spelling.

Run a harmless test before publishing

Before printing, publishing or giving out a public business address:

1. Confirm that the provider can create or route the exact address with the period in the intended position.
2. Send harmless fictional content from an unrelated inbox and confirm that it reaches the intended destination.
3. Enter the address into the real website, quote, booking, CRM and accounting workflows the business uses.
4. Copy it from a PDF and a mobile screen. Check that the period remains visible and in the correct position.
5. 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.
6. 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. A period-containing 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 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.