What is a hello@ email address?

It is a role address on your own domain — hello@yourbrand.com — that belongs to the business rather than to one person, so whoever handles enquiries can answer it and nothing breaks when that person changes. It reads smaller and more human than info@, and because it is guessed less often by address harvesters it attracts noticeably less spam in its first year.

Should I use hello@ or info@ for my business email address?

They mean the same thing, so decide on tone and spam. info@ reads institutional and has been the default guessable address for thirty years, which means harvesting lists are saturated with it and a brand-new info@ starts receiving spam before its first real message. hello@ reads smaller and stays quieter for longer. Either is a defensible brand decision.

Which email addresses should a new business create first?

One public address (hello@ or info@), support@ if anyone will ever answer customer questions, and billing@ to keep invoices out of conversation. Add postmaster@ and abuse@ as aliases pointing at your main inbox — other mail operators use those to reach a domain owner, and a domain that bounces them looks unattended to the systems deciding whether to trust your mail.

Should I use a no-reply@ address?

No. It tells customers their reply was discarded, which is a strange thing to say to someone who just tried to talk to you, and it removes the engagement signal spam filters read as evidence that people want your mail. Send automated messages from an address a human eventually reads, even if replies simply land in support@.

Business email address ideas: hello@ vs info@

This looks like a naming question and is really a structure question. The addresses you create on day one decide who can answer what, what happens when someone leaves, and how much spam you will be reading in two years.

hello@ versus info@ versus contact@

They are interchangeable in meaning, so pick on two grounds: tone and spam. info@ reads as institutional, hello@ as small and human, contact@ as neutral. That is genuinely a brand decision and there is no wrong answer.

The spam difference is not a matter of taste. info@ has been the default guessable address for thirty years, so address-harvesting lists are saturated with it — a brand-new info@ on a brand-new domain starts receiving spam before it receives its first real message. hello@ is guessed less often, which buys you a quieter first year and nothing more permanent than that.

Addresses worth creating on day one

Address	Why	Type
`hello@` or `info@`	The public front door on your site and invoices	Mailbox
`support@`	Shared over time by different people	Mailbox
`billing@`	Invoices and receipts, kept separate from conversation	Alias or mailbox
`postmaster@`	Mail standards expect it to be reachable	Alias
`abuse@`	Where other providers report problems with your domain	Alias
`name@`	One per person who deals with anyone outside the company	Mailbox

The last two are not decoration. postmaster@ and abuse@ are the role addresses that other mail operators use to reach a domain owner, and a domain that bounces them looks unattended to the systems deciding whether to trust your mail. They cost nothing as aliases pointed at your main inbox.

The problem with personal-name addresses

jane@yourbrand.com is the right address for Jane and the wrong address to print anywhere durable. When Jane leaves, every customer who saved her address is now writing to a mailbox nobody reads, and every contract with her address in the signature block points at a dead end.

The usual fix is boring and works: personal addresses for people, role addresses for functions, and only role addresses go on the website, the invoice template and the email signature footer. When someone leaves you convert their address into an alias pointing at whoever took over, and nothing outside the company notices.

Do not build no-reply@

A no-reply@ sender tells customers their reply was discarded, which is a strange thing to say to someone who just tried to talk to you. It also removes the engagement signal that spam filters read as evidence that people want your mail. If you send automated messages, send them from an address a human eventually reads — even if replies just land in support@.

Why this used to be a budget question

Every list above assumes creating an address is free. On per-seat pricing it is not: a mailbox is a licence, so billing@ and press@ cost the same as hiring someone. Teams work around it with groups and aliases, which is fine but means learning an admin console to dodge a billing artifact rather than to solve a problem.

When mail is priced per domain the question disappears and you can name addresses for the reasons above rather than around an invoice — which is the entire point of getting the naming right in the first place.