What emails are brought into the platform?
Any email message that is sent between a community member and an Aspire user who has sync’ed their email account with Aspire will be brought into the platform. This includes direct messages (user X sends an email to member Y or member Y sends an email to user X) and messages where the member or user is CC’d on the message.
That means that if a community member sends an email to a user whose email is not sync’ed then the email will not be brought in. Similarly, if an email is sent by a user whose email is synced, but not to a member, then the email will not be brought in.
Email is brought in:
Sync’ed user sends an email to a member
Sync’ed user sends an email where a member is CC’d
Member sends an email to a sync’d user
Member sends an email where user is CC’d
Email is not brought in:
Sync’d user sends an email with no member included
Sync’d user sends an email to another sync’d user
Member sends an email to a non-sync’d user
Member sends an email to another member
How does Aspire know which emails to bring into the platform?
The only emails that Aspire will attempt to bring into the platform are ones that contain the email addresses of community members and brand users.
What other protections does Aspire offer to ensure unwanted emails are not pulled in?
The platform includes a feature called ‘Conversation Privacy’ which can be used to prevent email addresses with the brand domain (ie. “@amazon.com”) from being used in a member email address. By default, your own domain will be blocked.