Quick Actions are a series of servicing actions that will run on an account when initiated by a user or automation. These actions can either guide an agent through a task or automatically update the account. 

To give you granular control over when and how each Quick Actions is used, set up involves three steps:

1. Creating the Quick Action
2. Giving agents access through Quick Action Groups
3. Enabling the Quick Action on specific programs.

This article will cover those three steps, and to see how agents use them, check out our article on Using Quick Actions.

Configuring Quick Actions

To configure a Quick Action, navigate to Settings > Line of Credit > Quick Actions. 

Click ‘Add’ at the top right to create a new Quick Action. You'll need to give the Quick Action a name and write a Clojure rule for it. This rule will determine if the line of credit account qualifies for the Quick Action to run. After you've filled out the ‘Name’ field and set up a rule, click ‘Save’. 

You'll then be brought to the creation page, which is separated in two tabs—Quick Actions and Quick Actions Groups. We'll go into more detail about Quick Actions groups below, but for now we're going to focus on the ‘Quick Actions’ tab.

At the top of the page, you can edit the name, program type and rule. Below these options are the configuration tools for your Quick Action—Actions, Group Enrollment, and Program Enrollment. We'll go over each of these tools in more detail below. 

In our example, we will create a Quick Action that will log a payment and notify the customer through email that a payment has been posted to their account.

Begin by clicking the ‘+ Add’ button in the ‘Actions’ tab to add a series of actions. Clicking the ‘Action Type’ dropdown menu will display the current available action types we have in the software.

Depending on the action type you've chosen (guided or automatic), you'll be presented with different pages for configuration. We'll go over how to configure a guided action (Log a Payment) and an automatic one (Send Customer Communication).

Guided Action

‘Log a Payment’ is a guided action, meaning that it requires user input to complete the action. Similar to an Agent Walkthrough, it will bring up the relevant page in the customer's account, but Quick Actions provides more customization on what the user can do on this page. 

Start by writing a short description of the step, then scroll down to Page Settings and Page Instructions.

Page Settings

The ‘Page Settings’ tab is where you can manage what information is displayed and accessible on each page. The columns under the Page Settings are:

In our example above, we've configured the following settings:

• Amount will override the default and set the due amount as the placeholder according to the variable. The user will have the ability to write in a different payment amount if needed. 
• Apply Date will override the default and set the next payment due date as the placeholder according to the written Clojure rule. The user will have the ability to write in a different apply date if needed. 
• Info will not override the default, but the user will have the ability to write in the information on their own.
• Split Payment will override the default and the placeholder will be 'No'. The user will not be able to view the Split Payment option because their access is set to 'None'. The system, however, will still evaluate that there will be no payment splitting when this Quick Action runs while the option is hidden from the user. 
• Payment Type will override the default and be set to ‘Regular’. The user, however, won't be able to edit it—they can only view what the placeholder is set at. 

Each guided action will have different properties that are relevant to the action.

Page Instructions

The ‘Page Instructions’ tab lets you write out instructions for your agent users to complete the action. The instructions will display in the Smart Panel when the Quick Action goes through a guided action, similar to the instructions on an Agent Walkthrough. Your instructions can be formatted in any way that makes sense to your company's operations.

If you want agents to see account-specific information as they go through the Quick Action,  you can add widgets that will display information like customers or linked accounts.

Once you've written out the instructions and enrolled your widgets, click ‘Save’. 

Automatic Action

When a Quick Action hits an automatic action type, the specific action will occur automatically.

To add an automatic action type, click the ‘Add’ button and select any of the automatic actions. For our example, we'll select ‘Send Customer Communication’. 

There are no ‘Page Settings’ or ‘Page Instructions’ tabs. Instead, we’ll choose a template that we want to send from the ‘Notifications Template’ dropdown menu (other automatic actions would have their own options). When we’re done, we’ll click ‘Save’. 

Group Enrollment

The ‘Group Enrollment’ tab will show you a list of the active Quick Action groups in your tenant. Enrolling a group for a Quick Action will give the group access to run the Quick Action on an account that satisfies the requirements. Users who are not enrolled in the Quick Action Group will not be able to access the Quick Action. 

To enroll a group, click the toggle button so that it turns green. If you aren't seeing a specific group under this tab, make sure that your group is set to ‘Active’ in the ‘Quick Actions Group’ tab. 

Program Enrollment

The last step to create your Quick Action is to decide which programs to enroll it on. This is an additional layer of access control, limiting the Quick Action to the selected programs.

To enroll your Quick Action into a program, click the toggle button next to the program so that it turns green.

Once the program is enrolled, any agent who belongs to the appropriate Quick Action Group will be able to access it on accounts from that program.