In this guide, we'll look at how to set up form workflows which will allow us to either add or withdraw a contacts consent within Gecko. 

As a quick primer, Consent Reasons are fully customisable options by which a contact can shape how they'd like you to communicate with them. By default in Gecko, Email, SMS and Call are the three standard types of consent that can be gathered. 

There are a number of ways to add consent to a contact. You might: 

There is another way, however.


Consent workflows

Workflows are ubiquitous in Gecko and therefore this method can apply to workflows found in broadcasts, call campaigns, events and forms. 

To apply a consent, simply set the Action side of your workflow to include the below, or any variation of the below:

Let's illustrate this with an example. If this workflow were in an event, it could stipulate in the workflow Condition that any attendee joining the event with the Registered status would automatically be assigned consent to receive Email, Call and SMS in from the workflow Action. Not only is this a popular use-case for consent workflows, it's also one that is compliant with GDPR ruling, as it is plausible that a member of the public who willingly signs-up to an event would want to be informed of information pertaining to the said event. 

Putting that example to one side, how would we go about using a form to collect consent? The easiest and most elegant solution would be, of course, to use the Consent field

But what if you don't have access to GeckoProtect

Head into the form that you'd like to collect consent on. Click Form Fields and add a Checkbox - Multiple Choice field. Click to Edit the field. 

Rename your field to 'Consent' and then, in the Options tab, rename your choices Email, Call and SMS respectively, before hitting Update in the bottom right-corner. Now click Save changes in the top-right corner. Our field is now set up. 

However, as we aren't using the Consent field, our workflows aren't automatically set up for us. The consequence is that, currently, users of this form who select Email, SMS or Call will log these picks, but their contact consent preferences won't be updated. 

Let's change that. 

Click on the Workflows tab and choose to + Add Workflow. In the Conditions section of your workflow add the following: 

Condition
---------
Type = Field
Field = Consent + contains
Value = Email

Now in the Actions section, add the following:

Action
------
Type = Assign consent value(s)
Operator = Give consent to
Consent Reasons = Email

Once done, click Save changes in the top-right corner. Your workflow should look like this:

Now repeat this set up twice more, but swapping the Value and Consent Reason in the Condition and Action for Call and then SMS respectively. Note: there must be an individual workflow for each consent reason. 

If set up correctly, you will now have 3 separate workflows which will update a contacts consent preferences based on if they have or have not selected the consent reasons on your form.

Our work is now almost done. It is important, however, to give existing contacts the opportunity to withdraw consent. Remaining in the Workflows section, create another workflow which reads the following:

Condition
---------
Type = Field
Field = Consent + does not contain
Value = Email
Action
------
Type = Assign consent value(s)
Operator = Withdraw consent from
Consent Reasons = Email

Again, duplicate this a further two times for Call and SMS. Then be sure to hit Save changes in the top-right corner.

You will now have 6 separate workflows - 3 granting consent and 3 withdrawing consent. Of course, it may be that you may not want to offer all three options for every form, so feel free to adapt the above method to suit your purpose.

***

Any questions? Feel free to start a live chat with a member of our support team or explore the rest of our academy at your leisure.

Did this answer your question?