Gryphon is a compliance provider that dynamically maintains federal, state, and other do-not-contact (DNC) lists, as well as state-of-emergency statuses (e.g. of citizens affected by a natural disaster in a particular region at a particular time).
\nRegal’s Gryphon Check blocks calls to leads on DNC lists or in a state of emergency so you can respect your customers’ status and preferences. Calling customers of either status can have legal repercussions.
\nNote: At this time, the Gryphon Check is supported for all call-related tasks.
\nThe Gryphon Check is generally available on request. For access, please fill out this request form or reach out to your Customer Success Manager.
\nRegal will block calls to DNC contacts based on your setup preferences. If an agent accepts a call task or dials out to a number on a relevant DNC list, Regal will
\nAny call tasks with the disposition \"Gryphon DNC\" were blocked by Gryphon, and you can assess the total number of Gryphon-blocked calls using the Reporting dashboards.
\nLet's say you've configured a campaign called \"Sales\" in Gryphon to check against federal and state DNC lists. You requested that Regal use the \"Sales\" Gryphon campaign when blocking calls, and that this campaign only be used to block Scheduled Callback and Manual Outbound Call tasks.
\nContact Lily has opted into the federal DNC list.
\nIf Lily calls in, the call is allowed and will ring out as normal, since Inbound Call tasks are not set to check against a Gryphon campaign.
\nIf an agent manually dials out to Lily, the call will be blocked, since Manual Outbound Call tasks are checked against Gryphon's \"Sales\" campaign, which recognizes Lily as being on a federal or state DNC list.
\nRegal's Gryphon Check supports \"exemption on the fly\". If you receive exemptions from your customers allowing you to still call them even if they are on a DNC list, you can pass this exemption information through to Regal's Gryphon Check to exempt those customers from the Gryphon block.
\nYou can pass through exemption information for customers via contact attributes.
\nGryphon requires 2 pieces of information for an exemption: the exemption name and the exemption date. This information must be passed through via individual contact attributes.
\nIn Settings, create 2 new contact attributes for each of these fields, setting these names as the Attribute Keys:
\nOnce you have the 2 new contact attributes created, populate them with contacts' exemption info (eg. via manual CSV upload or journey update).
\nNote: this should NOT be a future date - requests with a future date as the exemption date value will not be considered a valid exemption.
\nIf the Regal Gryphon Check is enabled, and a call is attempted for a contact where these attributes (customProperties.exemptionName and customProperties.exemptionDate) exist, Regal will pass the data in these attributes to Gryphon. If the data indicates a valid exemption, calls will still be placed to contacts even if they are on a DNC list. If the data does not indicate a valid exemption, calls will continue to be blocked when the contact is on a DNC list.
\nLet's say you've configured a campaign called \"Sales\" in Gryphon to check against federal and state DNC lists. You requested that Regal use the \"Sales\" Gryphon campaign when blocking calls, and that this campaign only be used to block Scheduled Callback and Manual Outbound Call tasks.
Contact Mark is on the federal DNC list. However, Mark has submitted a written exemption indicating that your company still may place calls to him. This exemption info is populated in Mark's contact attributes:
If an agent manually dials out to Mark, the call will NOT be blocked, as Regal's Gryphon Check will exempt Mark from the DNC block \"on the fly\".
"}}