Fixed an error when previewing reports.

Fixed

Fixed an issue when purging accounts that had Flow Documents attached to the consumer.

Fixed

Added a feature to change the buttons seen by a consumer in a Flow

PDCflow has enhanced the consumer experience when interacting with the received Flow documents.

With this new setup, when a Flow Document employs an Overlay to collect consumer input, such as a signature, the Flow will display options for the consumer to either Accept or Deny the signature request.



In cases where the Flow document does not utilize an Overlay, the consumer will be presented with a "Continue" button.

New

Adding functionality to display the Original Creditor Name in the initial text with Flows

PDCflow now provides the capability to display the originating creditor to consumers. This information will only appear in the initial SMS message sent via Flows when a consumer opts in to receive text messages from your company.

You can configure each Flow document to send either the Client Name, Creditor Name, or the Original Creditor Name as desired.



The image below is what the message will look like to the consumer when choosing one of the three fields listed above. If the account that you are sending a text message on does not have the data that you selected, the system will treat that as “None” which is discussed next.



When you select “None” or the account does not have the data you have selected to use, the consumer will receive a different message that will look similar to the following.

New

Fixed an issue where consent was not being updated after a consumer replies STOP after receiving a text message for QwikFlow.

Fixed

Fixed an issue where an error would display when saving a new VIC3 machine in the Dialer Setup screen within Beyond.

Fixed

Fixed an issue with updates from IDI Bankruptcy return data.

• Both the bankruptcy filing date and chapter conversion date are used to determine if an account should be updated.
• If the date of service is before the most recent of the filing date and chapter conversion date, the account will be updated.

Fixed

Fixed the Dialer Setup screen to update the list of machines after creating a new machine interface.

Fixed

The Action Summary screen has been removed as the Action Matrix stores all the same data and more.

• When receiving this update the Action Summary is automatically removed as an available aux screen for all clients.

Changed

Fixed an issue where the Company to Company Move program would copy the original InvoiceID for moved transactions.

Fixed

Fixed the help manual to further explain the summary totals in Account Summary.

Fixed

Fixed the help manual to better explain how client variable commission rate tables behave.

Fixed

Fixed an error when setting up QwikDial in the Dialer Setup option.

Fixed

Fixed an error that would cause segmentation fault messages.

Fixed

Fixed an issue where deleting a letter in Report Designer does not properly check if the report is a Beyond Letter.

• Report Designer now checks for queued letters before allowing a report to be deleted.
• Report Designer will delete the associated Beyond letter code when the report is deleted.
• Beyond letter codes will be allowed for future reuse after it has been deleted.

Fixed

Fixed an issue where Visual Intercept did not load custom plugins.

Fixed

You can now embed data into the subject, body, and footer of a Flow.

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.

Beyond Setup

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.



Please Note

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.



Consumer view

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.

New

Changed the minimum password requirement to allow a value higher than 13.

Changed

Updated Action Matrix with Consumer Contact Action event data

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. 

Beyond

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.



QwikClient

We made the update to the associated stats that your clients may have access to when viewing accounts through QwikClient.

Changed

Fixed an issue when setting up credentials for cell phone scrubbing.

Fixed

Fixed an issue where the mail return flag was not updating correctly if blocked by first alert or state restrictions.

Fixed

You now have the ability to customize a Flow.

Changed Items

• You can add a verification header and footer when the consumer attempts to enter their verification code.
• You can bypass the verification code altogether.
• You can add some additional customization to the body of a text message.

---

New Pin Setup tab

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.

• Verification Header - limited to 160 characters
• Verification Footer - limited to 320 characters



 

Once a consumer clicks the link that is sent when requiring the Verification PIN, here is an example of the Verification Header and Footer.



Disable Pin Verification

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.



Text customization

For text messages, PDCflow allows you to pass over a “Flow Title” that can be embedded into a text message. This is only 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.

New

Fixed an issue that was causing QwikFlow payments/reminders to fail due to token not authorized.

Fixed

Fixed an issue where failed and errored ACHs are not providing a response.

Fixed

Fixed an issue where the Client A/R screen wasn't properly showing check boxes as being checked when they should be.

Fixed

Fixed an issue with ACH and credit card payments not working properly when multiple processors are setup.

Fixed

Fixed an issue when double clicking a program's name when scheduling a new job wasn't setting a valid start date.

Fixed

Fixed an issue where accounts with no validation end date would get reported to the credit bureaus.

Fixed

Fixed an issue where the user name of the person that printed a letter was getting truncated in the Print Beyond Letters option.

Fixed