Workflows

Aegis One workflows are the central focus of Aegis One, allowing the creation and customization of a unique vetting pipeline for outgoing interactions. This feature works as a drag-and-drop flowchart builder, where different nodes can be selected from a list to perform different functions on an outgoing interaction. For more information, see the Executing an Aegis Workflow article.

Workflow

Displayed information includes workflow name, ID, published date, and status. Clicking the copy icon in any row will copy the workflow ID to the clipboard.

To open the workflow modification page click on an existing workflow in the list or choose to create a new workflow.

Workflow Edit

Newly created workflows begin with a Start node. Set the name and status of the workflow or adjust the zoom level to begin. Several different nodes may be dragged onto the main canvas. Connecting these nodes creates a path of execution. Node selections include:

Accept

• Allow interaction to proceed to network. Used at the end of the workflow after successfully meeting all requirements.

Reject

• Reject interaction attempt. Connects to the end of any node in the workflow that determines a requirement failed to be met.

Notes

• Place notes in the workflow to document processes.

Return

• Return control from an embedded workflow. Used in conjunction with the Workflow handoff node to pass control back to a parent workflow once functionality is complete in the child workflow.

Workflow handoff

• Handoff control to a different Aegis workflow. May be used in conjunction with the Return node to return control to the originating workflow.

DataBoost

• Perform DataBoost lookup query. Often used in conjunction with a Decision node, where the Decision node will create a conditional using the data retrieved from the DataBoost node.

Core Pool

• Integrate workflow with a core pool campaign.

Record set query

• The Record Set Query node connects to an Aegis Record Set, allowing queries to be performed when the workflow passes through this node. This node serves two primary functions:
  • Retrieving Recipient Data
    • If a record matching the recipient is found in the record set, recipient-specific tokens are populated.
    • These tokens can be used in subsequent decision nodes to drive workflow logic.
  • Updating ZIP Code Information
    • The node can update the ZIP code in the record set with the ZIP code collected during the interaction, ensuring data remains current.
    • To enable this functionality, the attribute containing the ZIP code must be explicitly configured.
• ZIP code update behavior is controlled by the override setting. Override Options for ZIP Code Updates:
  • Always – The ZIP code from the current interaction replaces the ZIP code in the record set if they are different.
  • When Not Set – The ZIP code from the interaction is added to the record set only if the record does not already contain a ZIP code.
  • Never – The ZIP code in the record set remains unchanged, regardless of the ZIP code from the interaction.

Decision

• Provides customizable conditional branching based on interaction data. Multiple conditions may be included in the decision by selecting Add condition.
  
  • Scope - The scope of the data that to be accessed for the conditional.
  • Property - The exact field to be accessed for the conditional
  • Operation - The operation to be performed on the data.
  • Value - The exact value to compare the gathered data to.
• Conditions may be added or deleted, with the Decision node always returning true if no conditions exist. If multiple conditions exist the decision will be determined by selecting All conditions must be met or Any of the conditions can be met.

FTC Do-Not-Call

• Runs a check to see if destination is on the Federal Do-Not-Call List.

State Do-Not-Call

• Runs a check to see if the destination is on the State Do-Not-Call List.
  
  • All states - Check each state's Do-Not-Call list.
  • Individual states can also be selected, and only the states that are selected will have their Do-Not-Call list checked.

RND Query

• Runs a check to see if a number is on the reassigned number database using the configured RND connection, Contact date scope, and Contact date property. The query will check records from the range included in the Default look back days. If a contact date does not exist the query will look back this number of days from the time of the interaction.

Natural disaster

• Runs a check to see if the interaction is attempting to reach someone who is currently in an active natural disaster situation.

Known litigator

• Runs a check to see if the interaction is attempting to reach someone who is on the known litigator list.

State dialing rules

• Runs a check to see if the interaction attempt is violating any contact rules in the state where the recipient resides. Residence is determined by the associated Property and Property type defined in the node. Pure CallerID updates state dialing rules frequently, ensuring this check is correct with the most up-to-date requirements and rules.

Time of day

• Create a schedule permitting outgoing interactions.
  
  • Time ranges may be added or removed for each day of the week. Each day can have different schedules. Days without a scheduled range will not permit interactions, while days with one or more schedules will allow interactions during those times.

Velocity

• Set a limit on how many interactions can be sent to a particular number in a set amount of time. If velocity constraints are exceeded the attempt will be rejected, automatically denying all interactions to that number until the suppression period has elapsed.
  • Channels - Select to check for velocity in Voice, SMS, or both.
  • Max interactions - The maximum number of interactions allowed during the time period.
  • In - The time period to check interactions. Unit for this time frame is set in the Period section.
  • Period - The unit for the time frame. Ranges from Minutes to Months.

Webhook

• Trigger a selected webhook when this node is passed through.

Active prospect

• If integrated with Active Prospect, connect Active Prospect to the workflow to verify consent.

Verisk

• If integrated with Verisk, connect Verisk to the workflow to verify consent.