Aliases, Roles & Teams

How to Create hello@ and support@ for Your Company — 2026

1,681 VIEWS
5 COMMENTS
June 1, 2026

How to Create hello@ and support@ for Your Company

hello@yourdomain and support@yourdomain are the two role addresses most small brands need first: one for first contact, one for issues that already happened. On MailShrine Free you can cover both as aliases on your single mailbox — Free includes 1 mailbox + 2 aliases.

You do not need a second paid seat just to put hello@ on Instagram.


Real-life example: Ember Clay Studio

Chioma sells hand-thrown mugs online. Shoppers DM from Instagram to hello@emberclay.studio; broken-shipment tickets go to support@. Both land in Chioma’s one Free mailbox until she hires a part-time CX person — then support@ becomes its own mailbox or shared-access setup.


Choose the right pair for Free’s 2-alias cap

Public needRecommended addressOn Free
Bio / first contacthello@Alias #1
Tickets / after-salessupport@Alias #2
Website formPrefer hello@ or info@ — don’t invent a third on FreeRemap form → existing alias
Founder / bankingyou@ mailboxUses the 1 seat

If you need billing@ too, either replace support@ or upgrade for more aliases (how many emails).


What you need

ItemWhy
Verified domainMX + SPF/DKIM so mail delivers
One mailboxAliases attach to it
Free alias slots2/2 for hello@ + support@

Alias basics: Alias vs mailbox. Product limits: Free plan.


Step 1: Create the owner mailbox

Example: chioma@emberclay.studio. Complete domain verification first (setup).


Step 2: Add alias `hello`

Mailbox settings → Aliases → local part hello on your domain. Save. This becomes the public brand address.


Step 3: Add alias `support`

Second alias uses Free’s remaining slot (2/2). Do not create support@ as another Free mailbox.


Step 4: Point every public surface at the right role

  1. Instagram / TikTok bio → hello@
  2. Checkout confirmation / FAQ → support@
  3. Website contact form → one of the two (stay consistent)
  4. Keep you@ off marketing creatives

Step 5: Test delivery and Reply-As habits

Send from a personal Gmail to both aliases. Confirm both appear in the mailbox. When you reply, choose the address customers wrote to so threads stay branded (Send As / identity options in webmail).


Checklist

  • Mailbox existsCompleted
  • hello@ alias liveCompleted
  • support@ alias liveCompleted
  • Bios and forms updatedCompleted
  • Test messages deliveredCompleted
  • Team notified which address is for sales vs ticketsNot completed

Common mistakes

  1. Publishing five mailto links on Free — only two aliases land.
  2. Creating hello@ as a mailbox then wondering why Free is “full.”
  3. Sharing the owner password with temps instead of planning shared access (shared mailbox guide).
  4. Relying on catch-all so “any@domain works” — catch-all risks.

Next steps

Related on YouTube · 1 of 4
How to create a business email account in 5 minutes?

Citations & References


Written by Elena M., Business Email Specialist. Elena designs role-address maps so tiny brands look organised without buying a mailbox per department.

Discussion

A

Amaka Eze

June 3, 2026

Set up hello@ and support@ on Free in under ten minutes. Bios updated the same afternoon.

L

Luis Romero

June 12, 2026

Wish I had read the part about not inventing a third alias for the contact form. Remapped the form to hello@.

F

Fatima Yusuf

June 21, 2026

Support tickets were landing in my personal Gmail before this. Customers take us more seriously now.

N

Noah Berg

July 1, 2026

Step 5 on testing both aliases should be mandatory. Caught a typo in support@ before we printed packaging.

Z

Zainab Lawal

July 14, 2026

Going to upgrade when we hire CX — using aliases until then as you recommended.