Actions in Logixx CRM are designed to execute specific tasks within the system. They allow users to perform a variety of operations, such as applying specific functions to an applicant, they can also include transitions, enabling seamless updates to an applicant's workflow status while maintaining efficiency and clarity.
Location
You can configure and manage Actions by navigating to:
Admin > Site Setup > System Config > Actions
Basic Information
Active
The Active switch allows you to activate or deactivate an action.
Category
The Category field provides predefined classifications for actions, enabling users to assign appropriate contexts. Available categories include:
Call
Dead
Email
Holding
Inbound Call
Outbound Call
Processing
Researching
Waiting
Appointment
Application
Does Not Qualify
Not Interested
Assign
Submitted
Approved
Update
Submit App
Return App
Execute Webhook
Title
The Title represents the name of the action. Users can define a concise, meaningful title for each action.
Group
The Group field defines whether an Action belongs to the Actions workflow or is tied to Dispositions.
Group 1 (Actions) → Standard system actions that drive workflow changes, assignments, submissions, and automations.
Group 2 (Dispositions) → Used for tracking call outcomes and categorizing resolutions
Action Requirements are grouped into three main categories: Conditions, Validators, and Post Functions, with detailed tooltips provided for each.
Categories Overview
Post Functions: Automatically carry out additional processing required after an Action is executed.
Validators: Check that specified requirements for the app are met before the user attempts to execute the Action.
Conditions: Define requirements that the user must fulfill on the action screen before the Action can be processed.
Options | Category | Description (Tooltip) |
Assign to User | Post Functions | Assigns the app to the user executing the action, provided another user with the same App Role is not already assigned. |
Reset Automated U.W | Post Functions | Resets the most up-to-date Automated Underwriting results, including Manual Reviews. |
Trigger a Webhook | Post Functions | Triggers the specified webhook profile after executing the Action. You must specify a webhook already defined in Webhook Profile settings. |
FORTH Submission | Post Functions | Triggers the submission of enrolled and unenrolled creditors to FORTH via API. Requires pre-configured integration by the Logixx support team. |
Backend Submission | Post Functions | Triggers a full submission of all application data to another Logixx back-end organization. Requires pre-configured integration by the Logixx support team. |
Run Credit (ALV Workflow) | Post Functions | It will pull the credit report and send to ALV for normalization. |
Run ALV Underwriting | Post Functions | It will run the ALV underwriting. |
Field Value | Validators | Allows the action to execute if the specified value of a field is set. |
Automated U.W | Validators | Allows the action to execute if the most recent Automated Underwriting results meet the specified configuration. |
Add a Comment | Conditions | Requires the user to add a comment. |
Create Calendar Event | Conditions | Requires the user to add a calendar event. |
Create Task | Conditions | Requires the user to create a task. |
Send Email | Conditions | Requires the user to send an email using an existing email template or draft a new one. |
Send SMS | Conditions | Requires the user to send a text message using an existing SMS template or draft a new one. |
Options | Category | Description (Tooltip) |
Assign to User | Post Functions | Assigns the app to the user executing the action, provided another user with the same App Role is not already assigned. |
Reset Automated U.W | Post Functions | Resets the most up-to-date Automated Underwriting results, including Manual Reviews. |
Trigger a Webhook | Post Functions | Triggers the specified webhook profile after executing the Action. You must specify a webhook already defined in Webhook Profile settings. |
FORTH Submission | Post Functions | Triggers the submission of enrolled and unenrolled creditors to FORTH via API. Requires pre-configured integration by the Logixx support team. |
Backend Submission | Post Functions | Triggers a full submission of all application data to another Logixx back-end organization. Requires pre-configured integration by the Logixx support team. |
Field Value | Validators | Allows the action to execute if the specified value of a field is set. |
Automated U.W | Validators | Allows the action to execute if the most recent Automated Underwriting results meet the specified configuration. |
Add a Comment | Conditions | Requires the user to add a comment. |
Create Calendar Event | Conditions | Requires the user to add a calendar event. |
Create Task | Conditions | Requires the user to create a task. |
Send Email | Conditions | Requires the user to send an email using an existing email template or draft a new one. |
Send SMS | Conditions | Requires the user to send a text message using an existing SMS template or draft a new one. |
Action Reporting
Contact Attempt
A switch to track whether a contact attempt has been made.
Contacted
A switch to track whether the user has successfully contacted the applicant.
Milestone
The Milestone field allows users to assign progress markers to actions and for reporting. Available options include:
None
Created
Contact Attempt
Contacted
Credit Report
Budget Analysis
Underwriting
Lead Pool
Submitted
Signed
Enrolled
First Payment
Canceled
Graduated
Progress
The Progress field tracks specific achievements within a workflow. Available options include:
None
Credit Pulled
Enrolled Client
UW Approved
Dispositions
Alongside Actions, Logixx CRM now includes Dispositions to improve call tracking and follow-up.
Dispositions represent call outcomes such as “Left Voicemail,” “Not Interested,” or “Follow-Up Needed.”
They appear in the Applicant Profile, next to Actions.
While Actions define what happens in the system (assign, send, submit, etc.), Dispositions capture the result of a conversation.
👉 For detailed guidance, see the full : Dispositions | logixx Help Center