Free
UChat Official
Introduction
In this detailed tutorial, we explore five methods to send delay messages across various platforms, primarily focusing on Facebook, WhatsApp, WeChat, SMS, Telegram, and voice flows.
The goal is to understand how to effectively utilize these methods, their limitations, and best practices to enhance user engagement through timely messaging. The tutorial is divided into three parts:
Part 1: Overview of five delay message methods
Part 2: Content types and platform-specific considerations
Part 3: Practical examples and pros & cons
This guide aims to provide a rich, structured summary with Markdown formatting, including bold, italics, tables, and lists to facilitate clarity and quick reference.
Part 1: The Five Methods to Send Delay Messages
1. Sequence Broadcasts
Description: Automated series of messages sent sequentially after user subscription.
Use case: Introducing users to your service gradually.
Setup: Predefine message order, timing, and content.
Limitations: Requires preset messages and timing; cannot be edited dynamically once set.
2. Broadcast
Description: One-time message sent immediately or scheduled.
Use case: Urgent announcements, event updates.
Flexibility: Can target users based on conditions like tags, shopping carts, or user fields.
Limitations: Manual setup each time; cannot be reused directly.
3. OTN (One-Time Notification)
Description: Send notifications that require user permission.
Platform-specific: Only for Facebook.
Features: No need to assign content types; send anything once permission is granted.
Limitations: User must click to allow; only one message per request.
4. OTN Plus
Description: Similar to OTN but with more flexibility.
Features: No need to specify content type; can send any message.
Use case: When you need to send multiple notifications over time, requesting permission once.
5. Smart Delay
Description: Dynamic delay based on duration, specific date/time, or user data.
Types:
Duration-based: Minutes, hours, seconds.
Specific date/time: Fixed points like holidays.
Dynamic date/time: Based on user actions (e.g., booking time).
Advantages: Highly flexible; can be integrated anywhere in the flow.
Limitations: Requires careful setup; editing involves locating the specific delay step.
Part 2: Content Types and Platform-Specific Considerations
Facebook Content Types (Mandatory after 24 hours)
Content Type | Description | Notes |
|---|---|---|
Default | General message | Allowed anytime |
Promotion | Promotional content | Allowed within 24 hours or with proper content type |
Update | Event or status updates | Must match message purpose |
Confirm Event | Confirmations | For specific interactions |
Post Purchase Update | Purchase-related info | For transactional updates |
Important:
After 24 hours of last user interaction, only specific content types can be used.
Sending incorrect content types results in failure and error logs.
Facebook rules are strict; content type selection is crucial to avoid bans.
Other Platforms (WhatsApp, WeChat, SMS, Telegram, Voice)
No content type restrictions.
Messages can be any content without specifying types.
No permission request needed for OTN-like messages.
Note: For WhatsApp and voice flows, content types are not required.
Platform-specific notes:
Platform | Content Type Requirement | Notes |
|---|---|---|
Yes | Critical after 24 hours | |
No | Flexible messaging | |
Voice/Telegram | No | No content type needed |
Part 3: Practical Demonstrations, Examples, and Best Practices
Setting Up Sequence Messages
Step 1: Choose Facebook flow.
Step 2: Navigate to Automation > Sequence.
Step 3: Create a new sequence, name it, and add messages.
Step 4: Assign content types (e.g., default, promotion).
Step 5: Define timing and order.
Additional: You can add extra messages before the last message is sent, enabling dynamic content flow.
Sending Broadcasts
Step 1: Select Broadcast from sidebar.
Step 2: Name, choose target audience, and set conditions.
Step 3: Write message content.
Step 4: Choose send now or schedule.
Note: Broadcasts are manual and not reusable without reconfiguration.
Sending OTN and OTN Plus
Step 1: Select OTN or OTN Plus.
Step 2: Pick topics (for OTN).
Step 3: Send permission request.
Step 4: Once user accepts, send the message.
Limitations: Multiple notifications require multiple user permissions.
Using Smart Delay
Step 1: Insert Smart Delay in flow.
Step 2: Choose delay type:
Duration: e.g., 30 minutes.
Specific date/time: e.g., Mother's Day at 12 PM.
Dynamic date/time: e.g., booking time + offset.
Step 3: Configure offsets for reminders or follow-ups.
Step 4: After delay, the subsequent message is sent.
Tip: Always set correct content types for delayed messages, especially after 24 hours.
Summary of Pros & Cons
Method | Pros | Cons |
|---|---|---|
Sequence | Automated, reusable, scalable | Predefined; less flexible for real-time changes |
Broadcast | Immediate, flexible, condition-based | Manual setup; not reusable |
OTN | No content type restrictions; flexible | User permission required; one message per request |
OTN Plus | No content type needed; multiple notifications | Multiple permissions needed for multiple messages |
Smart Delay | Highly flexible; dynamic timing | Setup complexity; editing can be cumbersome |
Final Thoughts
Choosing the appropriate delay message method depends on your platform, content needs, and user interaction goals:
Use Sequence for automated onboarding or educational flows.
Use Broadcast for urgent updates or announcements.
Use OTN/OTN Plus for permission-based notifications.
Use Smart Delay for timed reminders or dynamic follow-ups.
Key Takeaways:
Always match content types with platform rules.
Plan your flow to minimize manual reconfiguration.
Test thoroughly to avoid errors or bans.
Keep user experience in mind—avoid spamming or irrelevant messages.