Difference between revisions of "Mail Merge"

From Charitylog Manual
Jump to: navigation, search
(Introduction)
 
(2 intermediate revisions by the same user not shown)
Line 12: Line 12:
  
 
For saved Mail Merge, you must set a set a Lawful basis for this to function. The June 2024 version made specifying a [https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/a-guide-to-lawful-basis/ lawful basis] compulsory for using this feature. An audit of the basis, e.g. consent or legitimate interests, will be logged against each person who receives the letter/email.'''
 
For saved Mail Merge, you must set a set a Lawful basis for this to function. The June 2024 version made specifying a [https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/a-guide-to-lawful-basis/ lawful basis] compulsory for using this feature. An audit of the basis, e.g. consent or legitimate interests, will be logged against each person who receives the letter/email.'''
 +
 +
The following video gives an overview of how you can set up a mail merge.
 +
 +
{{#ev:youtube|T20kI9N9pf4|790}}
  
 
=Running a Mail Merge=
 
=Running a Mail Merge=
Line 51: Line 55:
 
==Consent Based Mailings==  
 
==Consent Based Mailings==  
  
If you choose Consent as the lawful basis, you will see the below option. You will then be required to specify which consent rule should apply. This means it will only mail merge records where there is a valid response to that consent rule. It will also ignore records where that consent has expired.  
+
If you choose ''Consent'' as the lawful basis, you will see the below option. You will then be required to specify which consent rule should apply. This means it will only mail merge records where there is a valid response to that consent rule. It will also ignore records where that [https://wiki.dizions.co.uk/index.php/Consent_Rules consent] has expired.  
  
 
[[File:consentoptionsmailmerge.png]]
 
[[File:consentoptionsmailmerge.png]]

Latest revision as of 10:53, 3 September 2024

Helpheader small.png

Menu mail merge.png


Introduction

The Mail Merge function is used to create definitions for producing letters or emails to be sent in bulk. They can be used in 2 ways:

1) Directly from the Contact Management menu, for contacting people regardless of the kind of work you've done with them.

2) Via a blue folder in a report, for instance to write to everyone who's had a contact in a particular project.

For saved Mail Merge, you must set a set a Lawful basis for this to function. The June 2024 version made specifying a lawful basis compulsory for using this feature. An audit of the basis, e.g. consent or legitimate interests, will be logged against each person who receives the letter/email.

The following video gives an overview of how you can set up a mail merge.

Running a Mail Merge

Once the lawful basis has been selected/updated, you can simply choose which one to run and either click Merge Emails or Merge Letters, depending on the type.

Mailmergelist.png

This will open a new page and will list all recipients which will be included in the mail merge. You can view the letter or email to make sure it's correct and also edit individual addressees if required. Then, just click on Print All Letters.

Printalllettersmailmerge.png

Creating a Mail Merge

To edit an existing definition, click on the name on the left or to create a new one click the 'Create New Mail Merge' button. On the following screen you will be able to configure:

Branch Reporting Section (requires Branch Module)

In this section you can specify to report on records in;

  • All Branches
  • Selected Branches
  • Selected Branch Groups (views)

Report Type Filters

Mailmergerecordfilterfieldlist.png

  • Definition Name - If you are saving the mail merge it would make sense to give it a specific name so you can easily distinguish it from the others.
  • Description - optional, but allows you to add a detailed description of the filters etc.
  • Exclude anonymous and anonymised people/organisation records - Will be set to Yes as a default. It is problematic to mail merge anonymous records as you often dont have enough identifiable information to record meaningful consent.
  • Export active people/organisation records - Will default to Yes, but you can in theory mail merge to inactive records if you wish.
  • Send only one letter/email to both "related and partnered" people - When two records are linked via the relationships function, you can choose an option which states "Send only one letter to both Clients, when both are in mail merge"
  • Email/Letter Template - Here you will choose the letter or email template the mail merge will actually use. These have to be created beforehand.
  • Create Emails/Letters - If you created a template which can be both a letter and an email, you can specify which will be created.
  • Allow contact preferences for letters - If you are using the Preferred method of communication option on the record, you can specify to comply with that rule, or send letter to all.
  • Allow contact preferences for emails - If you are using the Preferred method of communication option on the record, you can specify to comply with that rule, or send email to all.
  • User recipients preferred method of communication - You can set this to honour the options specified if you are using the preferred method of communication, or send to all.
  • Lawful Basis - You will be required to specify the basis by which this mail merge is being run. You will need to choose from one of the following: Consent, Contract, Legal Obligation, Legitimate Interests, Public Task, Vital Interests.

Consent Based Mailings

If you choose Consent as the lawful basis, you will see the below option. You will then be required to specify which consent rule should apply. This means it will only mail merge records where there is a valid response to that consent rule. It will also ignore records where that consent has expired.

Consentoptionsmailmerge.png

Who to Include/Exclude

In this section you will find the list of People and Organisation types you are using on your system. The names displayed are the ones specified in Customise Orgs & People. For each record type you can choose one of the following options:

  • Who to Include - This will include this record type when running the definition.
  • Who to Exclude - This is to exclude a record type when running the definition. If a person/organisation is set to more than one record type, the exclude will not use this record for the include.
Example
You wish to send a mail out to staff and a second mail out to volunteers.  You do not want to send anyone two mail outs.  The staff mail out is only set to include staff, the second mail out would be set to include volunteers and exclude staff.  Anyone that is both a staff member and volunteer would only be included in the staff mail out.

Mail Merge Orgs Types.png

Organisation & People Filters

Mail Merge Extra Criteria.png

The extra criteria section allows you to add conditions (arguments/queries) to the records being mail merged. These arguments/queries can include items, such as "only people in a certain location or a certain client type based on demographic data". This section will display the number of arguments/queries setup in the criteria. The specified criteria will only function when running the definition directly, and does not function with if running the mail merge from a Blue Folder Lookup.

To add or edit the criteria click on the 'Add Extra Criteria' button.

The criteria page will always start with a line with the condition set to 'WHERE'.

  • Condition - The first condition will always be set to where, this is the start of the argument/query. You can add multiple lines to the argument/query using the following conditions:
    • AND - This is in addition to the first line. The system will find data based on the first line and the second line.
    • OR - This will look at the first line to match data or match data based on the second line.
Example for AND
Looking for people in specific town that have any disability.
Where 'Town' = 'Town Name' AND 'Has Disability' = 'Yes'

Example for OR
Looking for people in two postcode areas, L1 and L2.
Where 'Postcode' text begins with 'L1 ' or 'Postcode' text begins with 'L2 '
  • Field Name - This is a dropdown list of people/org fields that can be used. If you select a field that is populated from a drop down menu you will be display a selection screen where you can select the required values (will imply 'or' for each option), this will populate the 'Selection Value' for you when you click the 'Save Details' button on the pop up screen.
  • Selection Criteria - This is specify the argument/query that is to be used on that line:
    • Equals (=) - The data in the selected field must equal the 'Selection Value'
    • Not Equals (<>) - The data in the selected field must not equal the 'Selection Value'
    • Greater Than (>) - The data in the selected field must be greater than the 'Selection Value', which would be appropriate for values and dates.
    • Greater Than or Equal To (>=) - The data in the selected field must be greater than or equal to the 'Selection Value', which would be appropriate for values and dates.
    • Less Than (<) - The data in the selected field must be less than the 'Selection Value', which would be appropriate for values and dates.
    • Less Than or Equal To (<=) - The data in the selected field must be less than or equal to the 'Selection Value', which would be appropriate for values and dates.
    • Text Begins With - The data in the selected field must begin with the 'Selection Value', often used with text (postcodes, address line or notes).
    • Text Contains - The data in the selected field must contain the 'Selection Value', often used with text (postcodes, address line, notes or email address).
    • Text Does Not Contain - The data in the selected field must not contain the 'Selection Value', often used with text (postcodes, address line, notes).
    • IN (this,this,this) - a set of any required values, separated by commas, for example, Smith,Jones,Williams would find everyone whose surname was any one of these three.
  • Selection Value - Where you enter the values to be used in the argument/query. This may have been auto completed by the selection of the 'Field Name', which you can change by clicking the 'Change Selection' button.

Once you have created a line you can add a new line by clicking the 'Save Details' button. If you wish to remove a line then set the 'Field Name' to '(No Field Selected)', when saving the line will be deleted. Once you have finished specifying the criteria click on the 'Save and Close' Button.