Communications Preferences

Donorfy offers very flexible options for making sure that your outbound communications reach the intended Constituents at the place and by the channel they prefer.

Channel Permissions

This allows you switch on and off the various outbound communication Channels for a Constituent. The Channels are:

  • Email
  • Mail
  • Phone
  • Mobile
  • SMS

When you switch a channel off you are prompted for a Reason and an optional Campaign.

Setting the Default Contact Details

You can set the Constituent's preference for:

  1. how you send it: selecting one of the permitted Channels (above)
  2. where you send stuff: either Personal, Work or Other

NOTE: you cannot save Communication Preferences if any conflicts exist in the settings you are trying to save. For example, if you have switched off Email in Channel Permissions, you cannot then have an email address selected in the Default Contact Details.

Setting Exceptions depending on Communication Purposes

Most of the time, the Default Contact Details will be enough to make sure the Constituent receives your communications according to their preference. But sometimes you need to be precise about where and how to send certain types of communication. And even to block certain kinds of communication.

So you can set up Exceptions - business rules which override the Default. To do this, select a comm's purpose from the drop-down list (e.g. Membership, Campaigns, Volunteering etc). And then select the the place and method by which you will send those communications (e.g. Work email address).

When "Do not contact" is selected, it means you are effectively blocking this Constituent from receiving communications of this Purpose.

You can add multiple Exceptions.

NOTE: Exceptions override the Default Contact Details and the Channel Purpose. For example: if the Constituent is blocked for Email in Channel Permissions, has Default Contact Details of "Other, by phone" yet has an Exception saying all Campaigns go to their Personal Email address, then the Exception wins.

List Overrides

These tags force the inclusion or exclusion of this Constituent into or out of a List, regardless of their qualification for appearing in that List according to its Filter.

Example: you have a list called Newsletter. The Newsletter List filter states the business rules for including Constituents - e.g. everyone that has made a donation in the last 2 years. However, for this particular Constituent you wish them to receive the Newsletter regardless of whether they have made a donation in the last 2 years. So you need to add a List Override to include them.

The reverse is also true. A Constituent who may meet the criteria for being included in the Newsletter List may have told you that they do not want to receive the Newsletter. In which case you add the List Override to exclude them.

If neither an Include or Exclude Override is specified, the inclusion in the list will be down to whether they meet the criteria in the List's Filter or not. And whether they are excluded from a List as a result of any Exceptions (see below).

NOTE: List Overrides beat Exceptions. e.g. if a Constituent has an Exception of "Do not contact" for Campaigns, but has a List Override inclusion for a specific List whose purpose is set to Campaigns, the List override inclusion wins (the Constituent will appear in the list).

Defaults for new Constituents

When new Constituents are added, the following defaults apply:

Channel Permissions

  • all channels are enabled

Default Contact Details - uses the first one of these that exist:

  • If Constituent is an Individual: Personal email (first one of the two), mailing address, phone, mobile
  • Work email (first one of the two), mailing address, phone, mobile
  • Other email (first one of the two), mailing address, phone, mobile
  • Personal, Work, Other SMS
  • Personal, Work, Other Twitter DM


  • none are set

List Overrides

  • none are set

NOTE: the same defaults apply for Constituents added via the API unless other settings are specified. 

Have more questions? Submit a request


Powered by Zendesk