Following the Beamery Comply 'Consent Management' and 'Manual Anonymization' releases, we have been busy making enhancements enable customers to achieve and maintain a state of compliance more efficiently, by:
- Integrating Consent Management and Anonymization into the Extension
- Introducing Beamery Comply Automation
Integrating Consent Management and Anonymization into the Extension
Requesting consent outside of Beamery:
Now users can generate the consent URL for contacts in Beamery directly from the Extension, allowing users to more easily share the consent link outside of direct messages or campaigns, e.g. via LinkedIn InMail. We recommend using a link shortener before sharing the URL to provide a better contact experience.
Protecting against sourcing Anonymized contacts:
Anonymized contacts will be flagged and blocked from being sourced into your CRM.
Introducing Beamery Comply Automation
We have upgraded Recipes so users can automate compliance-related workflows on a regular basis. In addition, users will benefit from additional Recipe filters that also complement GDPR Automation to better target the right candidates with automated actions. There are three key updates to Recipes:
- Scheduled Triggers: A new type of recipe trigger which will run periodic database checks (instead of only triggering a recipe at the time a contact's record is updated)
- New filters: Enables users to filter contacts by:
- When contacts were created, were last heard from, when an email is added to their profile, and which pools the contacts are NOT part of, to accurately segment and then tailor actions
- Archived contacts, and contacts marked as ‘Do not contact’; this allows for an automatic database cleanse of contacts who should not be contacted
- GDPR Automation: Users can trigger actions based on when a contact opts in or out, filter contacts by their opt in status and filter contacts according to how long it has been since time consent was provided
Run checks on the database of contacts at regular intervals of every 1, 6, 12 or 24 hours, for filters selected. For example, this enables customers to automate the following:
- Workflows based on previous updates to contacts (while standard triggers are future-facing)
- Archive contacts without consent information after a certain period of time
- Purge the database of archived, disengaged contacts after a certain period of time
- Add contacts to a campaign as soon as the sourced contact’s email is added
- Send a re-opt campaign when consent is about to lapse for contacts
The following filters have been added into recipes as part of this release, which work well with compliance workflows:
- Date created
- Marked as ‘Do not contact’
- Last heard from
- Doesn’t belong to pool
- Primary Email
Trigger actions depending on whether the candidate has opted in or out. For example, you can automatically send a confirmation email to the candidate or archive them using the consent trigger.
Filter contacts by the Consent field and the Last Consented field. For example, to run regular purges of contacts who have opted out and have been archived (used in conjunction with the scheduled trigger), or to send 're-opt in' campaigns when the candidate’s consent is about to lapse.