Sync email communications with donors from external email providers (Gmail, Outlook, etc.) by including your organization's Inbound Parse Email in the To, BCC or CC recipient fields. Email communication that is sent to Funraise is synced as a Supporter Interaction record.

Your organization's Inbound Parse Email can be accessed in Settings > Email Addresses > Inbound Parse Email

This is the email address you'll need to include in the To, BCC, or CC field for an email you want synced with Funraise. Your organization's email sync address is unique to your organization and can be used by any member of your team.

Your Inbound Parse Email uses your organization's Funraise Id and looks something like this: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx@parse.funraise.io

When your Inbound Parse Email is included in the To, BCC, or CC address fields on an email, the content will be synced with Funraise.

Here are three ways emails can be synced with Funraise:

When sending an email to a donor, include your Inbound Parse Email in the CC or BCC field. For example:

A donor's response to your email can be also be synced if the donor includes your organization's Inbound Parse Email in the CC, or BCC fields of their response.

Tip: If you've included your Inbound Parse Email in the CC field, when a donor selects Reply All when replying, their response will be automatically synced. For example:

You can also forward an email to your Inbound Parse Email address and that email will be synced with Funraise. It's common to forward emails to Funraise, especially in the case where a donor responds to you but does not include your organization's Inbound Parse Email with their reply. For example:

When an email is synced with Funraise, an Interaction record is created for the matching Supporter.

Synced data includes:

Opening the interaction record will display the email body content:

🤔 Should you CC of BCC?

It depends! In most cases, you'll likely include your Inbound Parse Email in the BCC field. This is because a BCC is not seen by the recipient and using a BCC may create a more personal experience.

If you include your Inbound Parse Email in the CC field, the donor will see that email address, but it also may ease your workflow when the donors sends a Reply All response because that response would then be automatically synced with Funraise.

Image files included as attachments are synced. Images that are only included in the body content of an email may not be synced. Although, some email providers will include an image the has been intentionally placed into the body of the email as an attachment, so it's possible and likely that some images in the email body are synced.

Synced email communication must include one of your team member's platform email address (the email address they use to log in to Funraise) or one of your Organization's Email Addresses.

If there are more than three email address in the To, BCC, or CC fields in total, an email interaction will not be created. This means that only direct 1:1 email communication between a donor and a member of your team can be synced.

Interactions are only created if the synced email includes an email address for a Supporter that exists in your platform. If you attempt to send an email to your Inbound Parse Email address and that email does not include an email address of an existing supporter, the email is not synced.

This is a rare case, but this rule is in place to avoid ambiguous or unnecessary interaction record creation and assignment.