With this latest enhancement to QwikFlow, you now have the ability to embed system data into the Subject Line, Email Body, and Email Footer when setting up and sending Flow documents.
There have been some customer inquiries looking into the process of sending validation notices via email, while a few are exploring the idea of offering a handshake letter program for their clients. Both use cases benefit from having the ability to embed system data.
By embedding system data you will be able to minimize the number of Flow documents that may need to be set up, customize the message you want to send to consumers, and reduce your printed mailing costs.
When setting up the flow document in the QwikFlow Documents menu option, you’ll notice an Edit button next to the Subject Line now. You have the ability to edit the content of the Subject line and also add system data fields like the Client Name or the Original Creditor Name.
For the Email Body and Footer, you will still have access to the same text editor as before; however, you now have an Insert Field button on the bottom left-hand side of the Editor screen. This button allows you to choose the data you want to use.
When any of the text editors are open, you can Right-Click and select the Insert Field option to select what data points you want to include in the message.
Once the Insert Field option has been clicked another box will pop up that will allow you to select a few system data fields that can be populated in either the Subject Line, Email Body, or Email Footer.
There are two options for the Validation End Date field when using Validation data in the email body or footer. The first option is the field on the Validation screen in Beyond, and the second option is called CalculatedEndDate.
This Calculated End Date field has the same behavior as when calculating the Validation End Date with a normal Beyond or 1st Alert validation notice. The only difference with this field is that since the end date is calculated at the time of letter print or LTRDOWN creation, that process did not work for sending emails. We added the field so that it will be calculated when the letter code was printed, prior to sending the information off for the email to be sent.
If you would like to explore sending the model validation notice via email, the email body could look something similar to the example below. All of the required information for the notice can be added and displayed in the email body. You also have the option to provide a link that the consumer can click to get access to the model validation notice in which you could send out via mail as well.
With this build, we updated the Action Matrix screen to work with both the Legacy Action and the Consumer Contact Action event nodes in Action Maintenance.
The Legacy Action event is primarily associated with the LEGACY action on the action line and the Consumer Contact event is mostly used in the COMTRCK action.
Shown below is the updated screen for the different communications and actions used in both of the events. A decision was made to keep both event actions since there are some customers not bound to Regulation F requirements due to their type of business outside of the 3rd party debt collection space.
We made the update to the associated stats that your clients may have access to when viewing accounts through QwikClient.
The ability to disable the Verification PIN requirement when consumers are accessing a Flow sent by PDCflow has been added.
Additional customizable fields can be presented on the verification page when requiring the Verification PIN.
Once a consumer clicks the link that is sent when requiring the Verification PIN, here is an example of the Verification Header and Footer.
IMPORTANT NOTE: If you choose to disable the Verification PIN, PDCflow will completely bypass the verification page and will take the consumer straight to the Flow document that you sent for them to view. Due to this, you will also not be able to edit the Max PIN Attempts, Verification Header, or Verification Footer.
For text messages, PDCflow allows you to pass over a “Flow Title” that can be embedded into a text message. This is for Flows sent via text message.
You can give each Text Flow a unique Flow Title. This title will help the consumer know what the flow text is for and why you are sending it to them to view.
The Flow Title will appear like this when sending a Flow via text.