How to leverage email aliases alongside your core email address
For some of you, having a separation between your internal emails and customer-facing emails is important. Here is how you can use email aliases alongside your core email address, instead of spending an additional $5 per user creating a new email address with your email provider.
Step 1: Decide how you want to set up your alias
Before you add your alias to Front, think about what you want in terms of team visibility versus having a consolidated view. I'll highlight both of these options below:
Team Visibility - If you want your team to have visibility into the emails that are sent to your alias email address, consider creating your alias as it's own separate individual inbox. This way you will be able to share the contents of this inbox with your team without sharing personal emails addressed to your internal address. To do this, go to your Settings > My Inboxes > Add an individual inbox. Now, skip to Step 2.
Consolidated View - If you have aliases for different brands or even just customer-facing addresses, but want to manage all of these emails in one central view, consider adding your aliases to your existing inbox. To consolidate your alias into your individual inbox, go to your Settings > My Inboxes > select the individual inbox that has your core email address > click Add a channel.
If you have an alias for a shared inbox that you want to consolidate into one central inbox, go to your Settings > Inboxes > select the team inbox > click Add a channel. Continue to Step 2.
Step 2: Add alias as a group email
When you go through the process of adding your alias account, make sure you set it up as a group email address. For instance, if you were to add an alias account for Gmail, you would add the account as a Google Group. If you've opted for the Team Visibility option, you should also make sure you grant access to all the necessary users during the inbox creation process. The teammates who are granted access to your inbox will be able to see your alias emails by clicking on your team icon under the Teammates section in left-hand panel.
Step 3: Don't set up email forwarding
When you add your alias account as a Google Group, Front will provide you with a forwarding address. Since this is an alias account, you do not need to set up a forward as all emails that are sent to your alias address will already appear in the core inbox, which is connected in Front, so just skip the validation process.
You will have to send an email to firstname.lastname@example.org to ask us to validate that email address manually. You will want to have us validate the email address, so you can send emails from our servers. If you'd like the emails you send from your alias to go back to your email provider, you'll want to set up a custom SMTP as well - instructions here.
Step 4: Rules for Team Visibility Option
If you've set up your alias account for team visibility and want your team to have access to all messages that are sent to your alias address, you'll need to set up an individual rule to route all alias emails from the core inbox to your alias inbox. You can use this as your template:
Hi Antti Teliö , thanks for pointing that out. You're right - that rule could catch some emails we don't want to be moved.
It is possible to set a rule condition to say "equals", rather than "contains", so we could update the rule to require the "to" address to be exactly equal to "email@example.com" in order for this to work.
Antti Teliö Got it. I think we need to raise a feature request here - the only "NOT" clause available right now for recipients is "not contains", so filtering for "TO, not contains firstname.lastname@example.org" would also match on "email@example.com". We'll see if we can implement something equivalent to "TO does not equal <address>" in the future