Follow-Up Sequences allow AIUNIFY Call Center customers to automate continued communication with contacts after a call outcome or other qualifying event.
Instead of manually remembering when to call, text, or contact each lead again, a customer can create a sequence containing several timed steps.
A sequence may include:
Follow-Up Sequences are designed to help businesses maintain consistent outreach without requiring an agent to manually schedule every follow-up activity.
A Follow-Up Sequence is an automated workflow made up of one or more steps.
Each step defines:
For example, a No Answer sequence could be configured as follows:
Once an eligible contact is enrolled, AIUNIFY Call Center tracks the contact’s current step, completed steps, next scheduled action, and overall enrollment status.
Follow-Up Sequences can help a business:
Sequences are most effective when the timing, content, and number of follow-up attempts match the business’s actual customer-engagement strategy.
Before creating or activating a sequence, confirm that the account has:
Email actions require valid mail configuration.
Webhook actions require an accessible external destination and any necessary technical configuration.
To open the sequence area:
The sequence page is located at:
Customers see sequences belonging to their own account.
Agents may see sequence information belonging to their parent Customer account when their assigned access permits it.
The main Sequences page displays the workflows associated with the Customer account.
Each sequence may show:
The page may also display overall account statistics.
The summary area may include:
The number of sequences owned by the Customer account.
The total number of enrollment records across the Customer’s sequences.
The number of enrollments marked as Converted.
A calculated conversion measurement across the Customer’s sequence activity.
The current implementation calculates its primary conversion measurement using converted enrollments compared with completed enrollments.
Review the underlying enrollment counts when interpreting the percentage.
To locate a sequence:
The search checks both:
Clear the Search field to return to the full list.
Sequences may be filtered by their current activation status.
Shows sequences that can accept new matching enrollments.
Shows sequences that are not currently accepting new automatic enrollments.
To apply a status filter:
The page may also allow sequences to be filtered according to their trigger.
Available trigger filters include:
Trigger filtering is useful when the account contains several workflows designed for different contact outcomes.
To create a sequence:
After saving, the system returns to the sequence list or opens the new sequence.
The Sequence Name identifies the workflow.
Use a name that clearly explains:
Examples include:
The name is required and may contain up to 255 characters.
Short, descriptive names are easier to locate and understand.
The Description field explains the purpose of the sequence.
A useful description may identify:
Example:
The description is optional but recommended when the account contains several similar sequences.
The Trigger Type determines what event makes a contact eligible for the sequence.
Available trigger types are:
Select the trigger that best represents the reason for the follow-up workflow.
Use No Answer when the sequence should follow up after a contact does not answer a call.
A No Answer sequence may include:
Avoid calling too frequently.
Repeated calls within a short period may produce complaints or reduce the likelihood of a response.
Use Interested when the contact expresses positive interest during a call.
Interest may be identified through:
An Interested sequence may include:
Use this trigger for contacts who need continued assistance rather than immediate closure.
Use Callback Requested when a contact asks to be contacted again.
A callback sequence may include:
The sequence delay should reflect the time requested by the contact whenever that information is available.
Do not substitute a generic delay when the contact requested a specific callback time.
Use Not Interested carefully.
This trigger may be appropriate for:
Do not use a Not Interested sequence to continue aggressive promotional contact.
Respect opt-out requests and applicable consent requirements.
Use Manual when contacts should be enrolled deliberately by a user rather than automatically through a call outcome.
Manual sequences are useful for:
Manual enrollment gives the Customer greater control over who enters the workflow.
Use Completed when the follow-up should begin after a completed call or completed workflow.
A Completed sequence may be used for:
Confirm how the business defines a completed interaction before activating this trigger.
Smart Timing allows AIUNIFY Call Center to optimize follow-up scheduling using available contact and calling data.
When enabled, the system may consider previous successful connection patterns to determine more effective contact times.
Smart Timing can help:
Smart Timing works best after sufficient call history has been collected.
A new contact with no prior activity may not have enough information for a highly personalized schedule.
To enable Smart Timing:
The current builder enables Smart Timing by default when creating a new sequence.
Turn it off when the business requires exact fixed delays without timing optimization.
Priority controls which matching sequence should receive greater consideration when multiple active sequences may apply.
The available priority range is:
A higher number represents a higher priority.
For example:
The default priority is:
Use higher priorities for workflows such as:
Do not assign priority 10 to every sequence.
Priority is useful only when different workflows have meaningful differences.
The Create Sequence page includes an Active control.
The sequence may begin accepting eligible contacts immediately after it is saved.
The sequence is saved but does not accept new automatic enrollments.
Keeping a sequence inactive initially is recommended when:
Steps define what happens after a contact enters a sequence.
Each step contains:
A sequence must contain at least one step.
The default new sequence begins with one step named:
The default delay is:
The default action is:
Give each step a name that explains its purpose.
Examples include:
Clear step names make the sequence easier to review and troubleshoot.
The Delay Amount determines how long the system waits before the step becomes due.
The amount must be zero or greater.
Examples include:
The delay should provide enough time for the contact to respond without allowing the opportunity to become stale.
A delay of zero may cause a step to become due immediately after the preceding sequence event.
Use immediate steps carefully.
Available delay units are:
Use Minutes for short operational pauses or urgent follow-up.
Use Hours for same-day or next-day outreach.
Use Days for longer sales, support, or nurturing workflows.
The delay unit works together with the Delay Amount.
For example:
means that the system waits approximately 24 hours before the step is due.
The Call action is intended to initiate an automated telephone follow-up.
Before using it, confirm:
A failed call step may be recorded as unsuccessful and may require administrative review.
The SMS action is intended to send a text-message follow-up.
Before using it, confirm:
The underlying sequence structure supports SMS action configuration, including message information.
The standard builder may provide limited action-specific fields in the current release.
The Email action represents an email follow-up step.
Email delivery requires:
The sequence builder includes Email as an action type, but the standard customer interface may not expose a complete email-content editor in the current release.
Test email actions before using them with live contacts.
The Wait action creates a pause in the workflow without sending a communication.
Use Wait when the sequence should:
A Wait action can make the sequence easier to understand when a timing period represents a distinct stage.
The Webhook action is intended to send information to an external system.
A webhook may be used to:
Webhook actions require:
The current customer builder may not provide every advanced webhook field directly in the interface.
Developer or administrator configuration may be required.
To add a step:
There is no benefit to adding unnecessary steps.
Each extra call, message, or external action can increase cost and customer-contact frequency.
The sequence builder includes Up and Down controls.
To reorder a step:
Step order determines the order in which the actions are processed.
A correct delay with an incorrect position can still produce the wrong workflow.
To remove a step:
A sequence must retain at least one valid step.
Exercise caution when editing a sequence that already has active enrollments.
Before saving, verify:
Use an inactive test sequence before launching a complex workflow.
After reviewing the sequence:
The system validates:
To view sequence details:
The Sequence Details page may display:
To activate an inactive sequence:
After activation, new contacts matching the selected trigger may be enrolled automatically.
Activation does not retroactively guarantee that all older matching contacts will be enrolled.
To deactivate an active sequence:
Deactivation prevents new matching contacts from being automatically enrolled.
Important: Existing active enrollments continue through their remaining steps unless they are individually paused, stopped, completed, or converted.
Deactivation is not the same as stopping all enrolled contacts.
To edit:
Editing may allow changes to:
Use caution when changing a sequence that already contains active enrollments.
When the step list is submitted during an update, the current backend replaces the existing stored steps with the newly submitted step list.
This can affect contacts already progressing through the sequence.
Before major changes:
For major workflow changes, creating a new sequence may be safer than restructuring an active one.
To delete:
Deletion is treated as an action that cannot be undone through the normal interface.
The sequence uses soft deletion internally, but customers should still treat the action as permanent.
The system prevents deletion when the sequence has active enrollments.
An error may state:
To resolve it:
Deactivation alone does not remove the active-enrollment restriction.
An enrollment connects one contact to one Follow-Up Sequence.
The enrollment records:
Each enrolled contact progresses independently.
One contact may be at Step 1 while another contact in the same sequence is at Step 3.
Automatic enrollment occurs when:
Possible automatic triggers include:
Manual enrollment allows an authorized user to place a selected contact into a sequence.
The process requires:
To enroll manually:
The exact manual-enrollment button may depend on the current page and permissions.
A manual enrollment may fail when:
Review the contact’s existing enrollments before trying again.
The system uses several enrollment statuses.
The enrollment is currently progressing through its sequence.
Only Active enrollments are eligible to execute due steps.
The enrollment remains stored, but automatic step execution is temporarily suspended.
All required sequence steps have completed.
The contact achieved the desired conversion result.
The enrollment was deliberately ended before normal completion.
An Active enrollment may display:
The background sequence processor checks Active enrollments whose next action is due.
Pause an enrollment when the contact should temporarily stop receiving sequence activity.
Possible reasons include:
To pause:
The enrollment status changes to Paused.
To continue a paused workflow:
The enrollment returns to Active status.
Review the next scheduled step after resuming to make sure the timing remains appropriate.
Stopping permanently ends that enrollment’s workflow.
To stop:
The reason is stored with the enrollment.
Examples of stop reasons include:
A stopped enrollment is not the same as a paused enrollment.
Use Pause when the sequence may continue later.
Use Stop when the enrollment should not continue.
A stopped enrollment normally requires a new enrollment if the contact needs to begin the sequence again later.
These controls operate at different levels.
Prevents new automatic enrollments.
Existing active enrollments continue.
Stops one specific enrolled contact from progressing temporarily.
Ends one specific contact’s sequence permanently.
Choose the control based on whether the change should affect:
The current interface provides individual enrollment controls rather than one universal stop-all command.
The Current Step indicates the contact’s present position in the sequence.
A newly enrolled contact may initially show no completed current step while the first step is being scheduled.
After a step begins or completes, the current-step position updates according to the sequence engine.
Steps Completed indicates how many sequence actions have already been processed for the contact.
This value helps determine whether the contact is:
Compare it with the total number of sequence steps.
The Next Step At field identifies when the next sequence action is scheduled to become due.
A step does not execute before this time.
If the time has passed and the enrollment remains Active without progressing, the background sequence processor may require administrative review.
Enrollment records may contain:
When the contact entered the sequence.
When the most recent sequence action was processed.
When the next action becomes due.
When the sequence reached a completed, converted, or stopped result.
These dates help troubleshoot delays and verify workflow timing.
The Sequence Details page may display recent enrollments and enrollment statistics.
Enrollment information can include:
The detailed enrollment API supports status filtering and paginated results.
The visual Sequence Details page may show a limited set of the most recent enrollments.
The Sequence Details page may display:
Use these measurements to understand whether the workflow is progressing.
A high enrollment total with very few completions may indicate:
The current sequence reporting compares Converted enrollments with Completed enrollments when calculating its displayed conversion rate.
Because of this implementation, review all three numbers:
Do not evaluate performance using the percentage alone.
The sequence analytics may display performance for each step.
Step measurements can include:
How many times the step was processed.
How many executions completed successfully.
How many executions were recorded as failed.
The percentage of step executions that completed successfully.
A low success rate on one step may indicate a problem with:
Activating or deactivating a sequence does not remove its existing history.
The system retains:
This allows a customer to temporarily stop new enrollments without deleting historical results.
The backend supports an optional maximum-enrollment setting.
When a sequence reaches its configured capacity, additional contacts may not be enrolled.
The standard customer builder may not display this advanced field in the current release.
If a contact cannot be enrolled and no duplicate enrollment exists, an administrator or developer may need to review the sequence’s capacity setting.
The underlying sequence system supports structured trigger and stop-condition data.
These advanced conditions can be used to define more detailed workflow rules.
However, the current standard sequence builder primarily exposes:
Advanced condition editing may require additional interface development or technical configuration.
The system supports Call, SMS, Email, Wait, and Webhook action types.
The underlying step record can store action-specific configuration.
However, the standard builder may not currently display a complete configuration form for every action type.
For example, the customer interface may allow Email or Webhook to be selected without presenting every required delivery field.
Test each action type before relying on it in a live sequence.
Sequence actions are processed through background jobs.
The processor:
The system processes due enrollments in batches.
Individual step jobs may retry when an execution temporarily fails.
An overdue enrollment may occur when:
If several Active enrollments remain overdue, contact the platform administrator.
Agents work under a parent Customer account.
The sequence listing uses the parent Customer’s ownership when an Agent accesses it.
Depending on delegated permissions, Agents may be able to:
Customers should retain control over sequence creation, structural editing, activation, and deletion unless an Agent has specifically been authorized to manage automation.
Begin with a simple sequence.
Use clear names.
Use descriptions that explain the purpose.
Start with two or three steps rather than a long workflow.
Test every action.
Use realistic delays.
Avoid excessive call frequency.
Use Smart Timing when sufficient history exists.
Use priority values consistently.
Keep inactive until testing is complete.
Review active enrollments before editing.
Respect consent and opt-out requests.
Monitor failures and overdue steps.
Compare conversion results over time.
A basic sequence could be configured as:
No Answer
5
Enabled
Name: First Retry Call
Delay: 24 hours
Action: Call
Name: Follow-Up Message
Delay: 24 hours
Action: SMS
Name: Final Call Attempt
Delay: 2 days
Action: Call
This is only an example. The appropriate timing depends on the business, audience, and applicable communication rules.
Callback Requested
9
Disabled when the contact supplied an exact requested time
Name: Requested Callback
Delay: Based on the agreed callback period
Action: Call
Name: Missed Callback SMS
Delay: 30 minutes
Action: SMS
A contact’s requested time should take precedence over a generic Smart Timing recommendation.
Interested
8
Name: Confirmation Message
Delay: 10 minutes
Action: SMS
Name: Sales Follow-Up
Delay: 1 day
Action: Call
Name: CRM Notification
Delay: 0 minutes
Action: Webhook
Confirm that SMS and webhook details are fully configured before activation.
Confirm:
Possible causes include:
Review the contact’s current sequence activity before creating another enrollment.
This is expected behavior when existing Active enrollments remain.
Deactivation prevents new enrollments but does not stop current ones.
Pause or stop the individual enrollments that should no longer continue.
Confirm that no Active enrollments remain.
Deactivate the sequence first, then pause, stop, or allow active enrollments to complete.
Attempt deletion again after the active count reaches zero.
Review:
Existing enrollments may have been created under an earlier step structure.
Confirm the requirements for the selected action.
Check phone number, Voice capability, credits, provider configuration, and geographic permissions.
Check SMS capability, recipient format, message configuration, and credits.
Check contact email address and mail configuration.
Check destination URL, authentication, availability, and expected payload.
Smart Timing may have limited information when:
Allow additional call history to accumulate or use fixed timing.
Confirm:
New sequences naturally begin with zero statistics.
The current implementation compares Converted enrollments with Completed enrollments.
Review the actual counts rather than relying only on the percentage.
A small number of completed records can produce a large change in the displayed rate.
Confirm:
Customers should avoid granting structural sequence-management authority unless the Agent’s role requires it.
Before activating a sequence, confirm:
Follow-Up Sequences automate continued contact after call outcomes and other qualifying events.
Customers can create sequences triggered by No Answer, Interested, Callback Requested, Not Interested, Manual, or Completed outcomes.
Each sequence contains one or more ordered steps with delays measured in minutes, hours, or days. Supported action types include Call, SMS, Email, Wait, and Webhook.
Smart Timing can use available contact history to improve scheduling. Priority values from 1–10 help determine which workflow should receive greater consideration when several sequences match.
Activating a sequence allows new matching contacts to be enrolled. Deactivating it prevents new enrollments but does not stop existing active enrollments.
Individual enrollments can be Active, Paused, Completed, Converted, or Stopped. Customers can pause, resume, or stop individual enrollments as needed.
The Sequence Details page provides enrollment counts, conversion measurements, recent enrollment activity, and step-performance statistics.
Customers should test sequences before activation, use reasonable communication timing, monitor failures, respect consent requirements, and carefully review active enrollments before changing the sequence’s step structure.