It is technically possible to have emails sent from &frankly (email@example.com) coming from a customized email address (e.g. firstname.lastname@example.org). Since emails from your own domains are typically always allowed to be delivered to the end-users - this may mean emails can be guaranteed to be delivered to all end-users.
In order to allow &frankly to send emails using your domain-customized email address, you need to have been granted access in your own organization to update global email configurations or get help from someone who has this kind of access, typically, someone from the IT Department. This is because there may be additional configuration required on your side - specifically SPF/DKIM settings that you would have to change to make us considered an “authorized” sender of email from your domain (in this example customer.com).
To fully set up a custom email sender, the following steps needs to be taken:
You need to add &frankly as an authorized sender by adding us to your own SPF records. The following record should be added on your side:
v=spf1 include:_spf.andfrankly.com ~all
- The custom sender email must be configured on your &frankly account. For this step, simply send us an email to email@example.com notifying what is the custom email address we should use for our communications.
We will then set up DKIM keys to ensure we can identify ourselves as a sender of email for your domain. This is done internally and after making initial configuration on the &frankly side to generate a key, you will need to add additional DNS records on your domain to point to ours to ensure our keys are considered valid (a link will be sent to you to add you as part of this step).
Note that setting up SPF and DKIM records may not be necessary to completely guarantee delivery, if you are already trusting anyone who sends emails via your domain. If this is the case, the steps 1 & 3 are not necessary to take - however if this is the case, then it is absolutely important that you do consider introducing these email security measures, as it means you are currently allowing anyone on the internet to send emails from your domain which is a huge security risk.
Note that by adding our sending IP address as an authorized sender via SPF & DKIM, it means that you are allowing us to send emails from your domain (not only to internal recipients, but to anyone) and this in itself is a potential security risk that you would have to assess and accept. We are comfortable that we will not be abusing these sender privileges, and that we have adequate security in place for the above - however it may mean less risk for you to simply whitelist us.