Sequences in Aloware are automated workflows that help admins manage follow-ups, lead nurturing, onboarding, and ongoing customer engagement. They allow teams to automate repetitive communication tasks while keeping contact handling consistent across campaigns.
Each sequence is built using a combination of actions such as messaging, updates to contact records, ownership changes, and enrollment into other workflows. These actions run automatically based on triggers or scheduled timing.
For example, a sequence can send a welcome SMS when a tag is applied, wait two days, and then assign the contact to a sales representative for follow-up.
Only admins can create and manage sequences in the Aloware admin panel.
If contacts are not enrolling as expected, the issue is usually related to inactive sequences, missing triggers, or incorrect enrollment conditions.
This guide explains how to manage sequences, configure workflow behavior, monitor enrollment, and review execution history.
Navigating the sequences page
The Sequences page gives admins a centralized view of all workflows in the account, making it easier to monitor automation health and identify issues quickly.
Each sequence row provides key signals to understand workflow activity:
Sequence Name & ID helps identify and locate specific workflows for review or troubleshooting.
Steps shows how many actions are included in the workflow and helps gauge complexity.
Contacts shows how many contacts are currently enrolled in the sequence at any given time.
Remaining tasks indicates how many actions are still pending for enrolled contacts.
Process on helps admins understand when the workflow runs, whether daily or on business days.
Line used shows which communication line is used for outbound messaging or calls.
Status indicates whether the sequence is currently active or inactive.
This view is typically used to confirm that workflows are running as expected and to quickly spot unusual drops in enrollment or activity.
Managing sequences
Each sequence includes tools that help admins manage workflow behavior, monitor automation activity, and troubleshoot enrollment issues.
Use Settings to control how the sequence processes contacts, including processing schedules, assigned communication lines, and throttling behavior. This is especially useful when managing outbound activity volume during peak hours.
The Steps section is where admins build the actual workflow logic. Sequences can combine messaging, dialer, tagging, ownership changes, and automation actions to support different customer journeys and follow-up processes.
Use Triggers to control how contacts enter the workflow automatically. Common examples include adding a tag, updating a contact field, or enrolling contacts from another automation.
The Contacts section helps admins review who is currently enrolled in the workflow, monitor progression through sequence steps, or manually manage enrollments during troubleshooting.
If contacts are not progressing as expected, the History tab provides a detailed activity log for reviewing completed actions, failed events, skipped steps, and enrollment activity.
Admins managing multiple campaigns can use Create copy to quickly reuse an existing workflow structure instead of rebuilding sequences manually.
Use Delete when a workflow is no longer needed or should be permanently removed from the account.
Adjust Throttle when controlling pacing of outbound activity is important, especially when sending messages or calls gradually during peak hours.
Setting up sequence actions
Each sequence is built using actions that define what happens to a contact at each step. These actions can be combined to create workflows that match different customer journeys, from simple follow-ups to multi-step automation flows.
Messaging actions
Messaging actions are used to automate communication across SMS, email, and voicemail channels to support lead engagement and follow-ups.
Send SMS message
Send picture/MMS message
Send SMS to inbox
Send email to contact
Send email to inbox
Send ringless voicemail
Dialer actions
Dialer actions help automate outbound calling workflows and manage how contacts are routed to calling campaigns.
Add to power dialer
Remove from power dialer
Progressive dialer
Preview dialer
Contact management actions
Contact management actions are used to keep CRM data accurate as contacts move through workflows.
Add tag to contact
Remove tag from contact
Change contact's owner
Round-robin change contact owner
Mark contact as DNC
Change lead source
Change contact disposition status
Add contact to list
Remove contact from list
Add line to contact
Workflow and automation actions
Workflow actions connect sequences with other automations and external systems, allowing more advanced automation flows.
Enroll to other sequence
Send webhook
Start AloAi conversation
Disenroll from AloAi Agents
Enroll in another sequence
Example: A lead can be automatically tagged after receiving a welcome message, then enrolled into a follow-up sequence for continued engagement.
Reviewing sequence activity
The History tab is used by admins to validate automation behavior and troubleshoot issues when workflows do not perform as expected.
To review activity, open a sequence and go to the History tab.
The log provides a full record of workflow execution, including which contacts were processed, what actions were triggered, and when each event occurred.
Admins typically use this to confirm whether contacts were enrolled correctly, whether actions executed successfully, or where a workflow may have stopped.
Filters allow deeper investigation by letting admins narrow results by contact, event type, or timeframe.
Answering Machine Detection (AMD) in sequences
Outbound calls placed through sequences use Answering Machine Detection (AMD) to identify whether a call was answered by a real person or by voicemail, answering machines, fax lines, or unclassified responses.
Only human-answered calls are counted as sequence responses, which helps ensure that engagement metrics reflect real conversations rather than voicemail pickups.
As a result, admins may notice lower but more accurate sequence response counts in reporting.
AMD runs automatically on all outbound sequence calls and does not require any setup or configuration.