Structuring Email Accounts in a growing Company?
Hey IH,
Does anyone have any good examples of how to structure email addresses in a growing company?
We did the usual start with G Suite on our root domain thing, but now it's become a bit of a mess to maintain.
We have :
- personal email addresses for staff members (~20)
- old staff email accounts (for archiving), but forwarding address to a group inbox
- shared team inboxes (via other SaaS products)
- shared email addresses for various logins (Google Analytics)
- notification (uptime, warnings) email addresses going to individual Slack channels
These are already across our root domain, some subdomains, and another TLD, or 2..
Is it crazy to move your team to a firstname.lastname@team.companyname.com format hosted on G Suite/365, and put your root domain behind an email gateway (Mailgun/Sendgrid/etc.) to have that better granular control for future? Will that affect deliver-ability?
Would you move all notification emails addresses to a new TLD/domain or subdomain, and keep your root domain super clean with just the usual suspects (info/sales)?
Even take a simple example like a work PayPal account - should that have a dedicated email address like paypal[@companyname](/companyname) .com, or paypal@foo.companyname .com, or paypal[@companyname](/companyname) .othertld, and share email notifications and access that way? (Ignoring any password management for now).
I should add that we're happy to pay for any solutions. Not looking for a hack setup to bypass any product fees.
Would love any pointers or examples - thanks in advance!
