1. thankQ Technical Conference February 2013 Automation Specification – Email and SMS

2. Requirement ● Automated sending of Emails and SMS ● Definable Rules to govern content and when to send ● Include content specific to the contact (e.g. like merge fields) ● Process on a nightly basis ● Pretty content (emails only – HTML) ● Define sender details (email only) ● Send directly or hold in “Drafts”

3. Features

4. Automated Email / SMS Features ● Sending is performed nightly ● Emails via Outlook 2012 ● SMS via thankQ’s SMS module ● New option: Automated Email / SMS ● Name of automation definition ● Type; Email or SMS ● Message definition ● Sending; direct or hold in drafts ● Validity Period; ● after a message is sent, how long to wait before another can be sent (e.g. Birthday message would have a period of 1 year)

5. Message Definition ● Email HTML definition with banner picture HTML definition with embedded fields from thankQ (e.g. name, address, pledge description, pledge instalment, etc.) HTML definition with links to website HTML definition with details of progress made on project to date including embedded pictures etc. HTML definition with details upcoming events and activities Choice of banner picture determined by set of rules defined in thankQ. Eg. Source-code of pledge will change the banner to reflect the livery of that project. Choice of banner picture determined by set of rules defined in thankQ. Eg. Source-code of pledge will change the banner to reflect the livery of that project. Choice of narrative determined by set of rules defined in thankQ. Eg. For each contact, Text & Picture based on program Description of program Value of regular giving to date Date of regular giving Payment Type Choice of narrative determined by set of rules defined in thankQ. Eg. For each contact, Text & Picture based on program Description of program Value of regular giving to date Date of regular giving Payment Type

6. Message Definition ● SMS Choice of narrative determined by set of rules defined in thankQ. Eg. Source-code of pledge will change the text to reflect the information for that project. Embed thankQ “merge” fields (e.g. {LETTERSALUTATION}, {SOURCECODE} etc. Choice of narrative determined by set of rules defined in thankQ. Eg. Source-code of pledge will change the text to reflect the information for that project. Embed thankQ “merge” fields (e.g. {LETTERSALUTATION}, {SOURCECODE} etc.

7. Would you like to know more? Contact: Cost, Development and Timescales

8. Development / Cost / Timescale ● Cost: $ 5,000 excl GST ● Specification Available ● 3 Clients can participate in development to influence / guide solution ● Purchase module ● 1 place remaining ● Timescale ● Development will commence in March ● First prototype for participating clients in May ● General release September / October