Changelog 45: New Custom Acknowledgement Buttons, and more...

Enhancements and Fixes

Acknowledgement Notices | Customize your Response Buttons

You can now customize the Acknowledgement buttons presented to guests. Prior to today's release when you created a new notice a guest would be forced to choose between 'Acknowledge' and 'Do Not Acknowledge'. However; many users requested the ability to customize these options. And now you can.


Simply rename the button label when creating a new notice. In the example below I rename Acknowledge to I will visit lv 3 and Do Not Acknowledge to I won't visit lv 3.

Note: Due to the fact you are re-naming a button label, we have limited the number of characters to 20.


Once Published, guests signing in will be presented with your Acknowledgement Notice including your custom button response options.


Acknowledgement Notices | Request More Information with Responses

To further support the growing demand for safety and security functionality you can now request additional information when a guest selects a response option to your Acknowledgement Notice. The option to do this can be found in the bottom of the Acknowledge Notice form when creating the Notice. (see below)

Why would I do this?

Let's say in my example above a guest selects I will visit lv 3 and I want them to tell me why they are visiting level 3. Simply enable Response Required when Acknowledged (or conversely Response Required when Not Acknowledged). 


When your guest signs-in and selects (in my example) I will visit lv 3 they will be prompted for additional information.



  • Increase Font Size: You can also increase the font size of the Acknowledgement Notice so that it displays the best fit on your chosen hardware or device.
  • Preview: You can also now Preview the acknowledgement notice and button options before saving and committing.

Learn more

New Trigger based on Acknowledgement Notice Response

There is now a new Trigger based on how a guest acknowledges your Acknowledgement Notice.

When creating a Triggers Action (like 'send an sms' or 'send an email') you can include the guest's actual response that they entered if asked for 'additional information'. The placeholder that inserts their response is found under 'Matched Person' category of placeholders and is titled: {{match.notice_info}}

My Action could be to send an email to the Facilities Manager which notifies them the name of the visitor signing in and their intention to visit level 3 and why. My message might look like this: 

Visitor ({{}}) Signed in and is visiting level 3. There reasons are: {{match.notice_info}}

New Insurance Status and Auto Set options

1) New Inactive Status: Previously we only had 'Active', 'Pending', and 'Expired' as statuses for your insurance policies. With today's update you now have 'Inactive' as a status option.

Why you ask?

  • Let's say you have a Trigger setup to deny access to a contractor if their Public Liability policy has expired.
  • Now let's assume that you add a new Public Liability policy to replace the expired one. Until today when you added the contractor's new policy (thus creating two Public Liability policies; one Active' and one 'Expired') the expired Public Liability policy still existed; its just 'expired'. So every time the contractor signs in the Trigger for the 'expired' Public Liability insurance policy still fires.
  • The only way to stop this happening was to either delete the expired Public Liability policy; thus losing historical visibility, or overwrite the existing expired Public Liability policy with the new Public Liability policy's details; again losing historical visibility.
  • With the new 'Inactive Status' available we now recommend that when updating an existing Insurance Policy change its status to Inactive, then add the new one.
  • Your Trigger that you setup won't run on the Inactive Public Liability policy - only on an Expired one.

2) New Auto set to Inactive option: With the new 'Inactive' status available we have also added another option that allows an insurance policy to automatically be set to Inactive when the expiry date is reached.

Why you ask?

  • Let' say you receive an updated Policy record before the current one expires.
  • You can now add that new policy and immediately make it Active.
  • When the current one expires it's status will automatically be changed to Inactive. You won't have to remember to log back in and update it's status manually.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request