Create Message Sequences and Delays

Create ordered messages and actions with timing, business-hour and stop conditions.

What this guide helps you do

Create ordered messages and actions with timing, business-hour and stop conditions.

Who should use it

Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.

Before you begin

  • Use the correct workspace and minimum required role.
  • Use a business-controlled provider account where applicable.
  • Understand provider billing, usage and data settings.
  • Use fictional Pakistan test data.
  • Define human handover before enabling automatic replies or calls.

Main concepts and fields

Concept / FieldMeaning or Use
SequenceOrdered steps.
DelayMinutes, hours or days.
Business HoursPermitted send time.
Stop ConditionPrevents further messages.
Next ActionFollow-up after the step.

Step-by-step instructions

  1. Create a sequence.
  2. Add the first content source.
  3. Add delay.
  4. Add later steps.
  5. Set PKT sending hours.
  6. Set stop conditions for reply, opt-out or status.
  7. Test timing with a shortened test sequence.
  8. Activate and monitor.

Test and verification

  1. Run one complete successful path.
  2. Run an invalid or failure path.
  3. Confirm fields, assignment and logs.
  4. Confirm human handover.

Common issues and solutions

IssueWhat to Check
Flow does not startActive status, channel, trigger and entry condition.
Wrong branchField type, stored value and condition order.
Repeated messagesLoop, retries, duplicate event and overlapping flows.
Action failsCredential, endpoint, schema and timeout.
Handover failsTeam, agent and permission.

Security, privacy, consent, cost and provider notes

  • AI-provider charges and Wemblo AI-action usage are separate controls.
  • Do not expose provider keys or customer data in screenshots, tickets or client-side code.
  • Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
  • Do not promise perfect accuracy or guaranteed business outcomes.

Last reviewed: