Changelog

Follow up on the latest improvements and updates.

RSS

We are thrilled to announce our new web templates, designed to elevate your marketing efforts. Whether building a website, creating a sales funnel, or sending email campaigns, our versatile and user-friendly templates have you covered. Fully customizable and professional, they streamline your workflow, saving you time and letting you focus on engaging your audience and driving results.
List of New Templates
------------------------------------------------------
🚀
1 New Website Templates Published
🚀
------------------------------------------------------
Real Estate - 1
-----------------------------------------------------
🚀
4 New Social Templates Published
🚀
-----------------------------------------------------
Other - 2
Medical - 2
-----------------------------------------------------
🚀
2 New Facebook Ad Templates Published
🚀
-----------------------------------------------------
Other - 1
Insurance - 1
-----------------------------------------------------
🚀
5 New Google Ad Templates Published
🚀
-----------------------------------------------------
Home Services - Bathroom Remodel Contractor
Health & Wellness - Health Club
Finance - Accounting Bookkeeper
Creative - Mobile DJ
Business Coaching & Consulting - Personal Development Coach
-----------------------------------------------------
🚀
2 New LinkedIn Templates Published
🚀
-----------------------------------------------------
Creative - 1
Real Estate - 1
-----------------------------------------------------
🚀
3 New LinkedIn Templates Published
🚀
-----------------------------------------------------
Lead Generation & Nurturing - Facebook Lead Ad Auto-Responder
Industry-Specific - Property Inquiry Follow-Up
Industry-Specific - Home Valuation Funnel
------------------------------------------------------
📣
1 New Snapshot
📣
------------------------------------------------------
Restaurant & Bar - Donut Shop
Dollar Store - Facebook Ad
Graphic Designer - LinkedIn Ad
Home Staging - Website
Home Valuation Funnel - Workflow
Pet Grooming - Social Planner
Pharmacy - Social Planner
Property Inquiry Follow Up - Workflow
Property Inspector - LinkedIn Ad
Accounting Bookkeeper - Google Ads
Bathroom Remodel Contractor - Google Ads
Donut Shop - Snapshot
Health Club - Google Ads
Mobile DJ - Google Ads
Personal Development Coach - Google Ads

new

improved

Automations

Targeted Edits in AI Builder

Overview
AI Builder now follows targeted-edit instructions with far greater precision. Name the actions or triggers you want changed and it updates exactly those, leaving everything else untouched. It can also apply the same change across many actions in a single instruction, so bulk edits that once meant opening each action by hand now happen in one pass.
What's New
  1. Sharper scoped-edit instruction following — Name the actions or triggers you want changed (all of them, a set number, or only specific ones) and AI Builder applies the change to exactly that set.
Screenshot 2026-07-11 at 12
  1. Bulk copy edits — Update email, SMS, or any-channel copy across multiple actions in a single pass.
Screenshot 2026-07-11 at 12
  1. Bulk pipeline stage swaps — Change pipeline stages across all or specific actions and triggers at once.
Screenshot 2026-07-11 at 12
  1. Bulk sender identity — Set From Name and From Email across all or selected email actions in one instruction.
Screenshot 2026-07-11 at 12
  1. Precise targeting — Provide exact copy for 20 of your 50 emails and AI Builder edits only those 20, leaving the rest unchanged.
How to Use
  1. Open the AI assistant in the sidebar within the workflow builder.
  2. Describe the change and its scope (e.g., "Set the From Name to Aviv in all email actions" or "Update the SMS copy in only the first two actions").
  3. Review the preview and save.
Why This Matters
Editing effort no longer scales with workflow size. On long, complex workflows, the bottleneck has always been the manual, action-by-action grind—and that's exactly what a single scoped instruction removes, so the largest automations see the biggest gains. Just as important, reliable scoping is what makes AI-driven bulk editing safe to trust at scale: changes apply only to the set you name, with no spillover into actions you didn't touch.
New Channel Management Experience
Channel Management changes how AI bots are assigned to your conversation channels. Instead
of relying on a single "Primary Bot," any bot can now be assigned directly to specific
channels and respond independently.
What's new
  • No more "Primary Bot" requirement.
    Bots are assigned directly to channels (SMS,
Email, Facebook, Instagram, WhatsApp, Live Chat, Web Chat).
  • Granular routing.
    Route by channel, by specific account/number, and by contact tags —
for example, send VIP-tagged contacts to one bot and everyone else to another.
  • Specificity wins.
    A more targeted assignment takes priority over a broader one (e.g.
"Facebook + VIP tag" overrides a general "Facebook" assignment).
  • No duplicate assignments.
    Two bots can't share the exact same channel + identifier +
tag configuration.
How to turn it on
  1. Open
    Labs
    at the sub-account level.
  2. Enable the flag named
    "Conversations AI Channel Management"
    .
  3. Wait about 5 minutes
    for your existing setup to migrate before testing.
Migration runs automatically once the flag is on — you don't need to recreate your bots.
What happens to your existing bots (migration)
  • Your current Primary Bot is preserved.
    During migration it's automatically assigned
to the channels it already supports, so it keeps responding exactly as before.
  • Bots that were
    not
    the Primary Bot keep their settings, but you assign them to
channels using the new channel assignment controls.
  • Bot assigned directly to a contact still takes top priority
    — regardless of channel.
Previously, if a bot was assigned to a contact but had that channel disabled, it wouldn't
reply. Now that per-bot supported channels are deprecated, an assigned bot will reply as
long as it's in autopilot mode, while still honoring all other settings (such as sleep
time).
The "first bot is primary" concept is gone
Previously, the first bot you created for a sub-account was automatically made the
location's
Primary Bot
. That concept is deprecated — there's no automatic primary
anymore. To get a bot to reply, you simply
enable the channels
you want it to handle.
Facebook & Instagram with multiple accounts
  • Each connected Facebook Page or Instagram account is treated as a separate channel
identifier.
  • After migration, your existing bot responds across
    all
    connected Facebook/Instagram
accounts by default.
  • To route them separately, assign a specific bot to a specific Page/account — each
connected account can be handled by a different bot.
Snapshots
What happens to a loaded snapshot depends on when the original bots were set up:
  • Snapshot from an older setup (before Channel Management):
    the bot that was the Primary
Bot keeps responding automatically — it's assigned its supported channels for you on the
first incoming message, no manual setup needed.
  • Snapshot from a Channel Management setup:
    loaded bots come in without channel
assignments.
Assign each bot to the channels you want it to handle
before it will
respond.
  • Either way, review each loaded bot's channel assignments before going live to confirm
they match how you want conversations routed.
Tags and segmentation
  • Assignments can include
    include
    and
    exclude
    tag filters.
  • Two bots can share the same channel as long as their tag filters differ — this is how you
split traffic (for example, VIPs to one bot, everyone else to another).
Workflows and transfers
  • The
    "Update Conversation AI Bot and Status"
    workflow action is still supported and is
now
channel-agnostic
— the workflow-assigned bot responds for that contact across any
channel, without a separate channel assignment.
  • Transfer Bot
    continues to work. A transferred bot can respond to the contact even
without a pre-set channel assignment for that conversation.
  • Sleep / pause behavior is preserved — a manual reply pauses the assigned bot for its
configured duration (when enabled), no matter which bot is handling the contact.
IMPORTANT: When this feature is enabled, any agent assigned using Update Conversation AI Bot and Status, that agent will respond on all channels. The previous Supported Channels configuration has been deprecated and is no longer used to determine where an agent responds.
Not supported yet
  • Public API
    is not supported for managing channel assignments — please use the in-app
Channel Management controls.
Need help
If a bot isn't responding as expected after enabling the flag, confirm the bot is assigned
to the correct channel (and account, for Facebook/Instagram) and that its tag filters match
the contact.
We've redesigned the Prospect AI experience to give you better visibility into what your AI sales agents are doing, what they've found, and what's happening behind the scenes.
Managing multiple AI agents is now easier than ever.
🔍 What's New
Redesigned AI agent cards
Screenshot 2026-07-10 at 3
Your AI agents now provide more useful information at a glance. Each agent card now shows:
  1. Total prospects discovered
  2. Last successful run
  3. Next scheduled run
  4. Agent description and specialization
  5. Quick access to view all prospects found by that agent
  6. No more opening each agent just to understand its status.
New agent home
Clicking an AI agent no longer takes you straight into edit mode. Instead, you'll now land on the agent's own workspace with two dedicated views:
Summary
  1. Agent configuration
  2. Prospect statistics
  3. Prospect finding criteria
  4. Next scheduled run
  5. Quick access to all discovered prospects
Screenshot 2026-07-10 at 3
Activity
  1. Complete execution history
  2. Previous runs
  3. Upcoming schedules
  4. Success and failure logs
From here, you can review your agent's performance before making changes.
Introducing the agent activity center
Screenshot 2026-07-10 at 3
For the first time, Prospect AI now explains what your AI agent has been doing. Now review:
  • When the agent last ran
  • When it's scheduled to run next
  • How many prospects were found
  • Which business categories were discovered
  • Historical execution logs
If no prospects are found, Prospect AI now tells you why and suggests improvements such as:
  • Increase search radius
  • Relax conversion score filters
  • Lower GBP rating requirements
  • Upgrade to high monthly limit or change limit allocation across agents
Screenshot 2026-07-10 at 3
Instead of wondering why nothing happened, you'll now receive actionable recommendations.
Dashboard metrics & faster navigation
The Prospect AI dashboard now includes quick insights across all your agents. See at a glance:
  1. Total AI agents
  2. Active agents
  3. Total prospects discovered
  4. Monthly lead usage
We've also added a search bar so you can quickly find and manage specific agents as your AI team grows.
Native CRM pipeline integration
Screenshot 2026-07-10 at 3
Prospect AI now integrates directly with your CRM pipelines. When configuring an agent, you can choose:
  • Which pipeline new prospects should enter
  • Which stage they should be placed in
Every newly discovered prospect can now be automatically added to your CRM pipeline, making it immediately ready for review, automation, and outreach.
This eliminates manual movement between Prospecting and your sales pipeline.
Why this matters
Prospect AI is becoming much more than an automated lead finder. With better visibility, execution history, smarter recommendations, and native CRM integration, your AI agents now behave more like members of your sales team.
You can now:
  • Understand what every agent is doing
  • Diagnose why an agent isn't finding prospects
  • Review every prospect an agent has discovered
  • Automatically move new prospects into your sales pipeline
  • Manage your growing AI sales team from a single dashboard
Prospect AI continues to evolve from a simple prospect discovery tool into a
complete AI SDR
and sales engine—helping you discover, qualify, organize, and prepare prospects for outreach with minimal manual work.
Have more ideas or feedback how Prospect AI can further make your outbound prospecting easier and efficient - do drop them here
Overview
Todoist is a task-management platform used by teams and individuals to organize work into projects, sections, and tasks, with support for labels, priorities, due dates, deadlines, comments, and collaboration. The Todoist integration brings these primitives into the Workflow Builder so task-lifecycle activity fires customer-facing automations, and any workflow can manage Todoist tasks and projects without leaving the builder.
About the Integration
The integration ships with two halves:
  • Triggers (Todoist → Workflows): Three polling triggers — New incomplete task, New completed task, New project — all polling every 5 minutes.
  • Actions (Workflows → Todoist): Twelve actions covering task lifecycle (create, update, mark complete), task and project comments, project creation and section moves, discovery (find tasks, find projects, find user), and collaborator management (get collaborators, invite user).
All triggers and actions are flagged as premium workflow components — premium action credits apply at the standard automation rate. Todoist plan usage (projects, tasks, collaborators, integrations) is billed by Todoist directly on your Todoist account.
How to Set Up Todoist
Before any Todoist trigger or action can run, the integration has to be connected via OAuth.
  • Connect via the Workflow Builder (recommended)
  • Open Automation → Workflows and pick (or create) a workflow.
  • Add a Todoist trigger or action — search for Todoist in the Apps tab.
  • Select any Todoist trigger or action.
  • On the panel, click Connect your account.
  • You will be redirected to Todoist’s OAuth authorization screen. Approve the requested scopes.
  • You will be returned to the Workflow Builder; the panel will update to show Connected.
Connect via Settings (alternative path)
  • Go to Settings → Integrations.
  • Locate Todoist and click Connect.
  • Complete the OAuth flow.
image
image
Example: Setting Up a Trigger (New incomplete task)
This walkthrough wires up a workflow that fires every time a new task is created in a specific Todoist project. The same configuration shape applies to New completed task and New project — only the trigger selection and applicable filters change.
Step 1: Add the trigger
  • Open the workflow and click Add trigger.
  • Switch to the Apps tab and search for Todoist.
  • Select New incomplete task.
Step 2: Configure the trigger
  • Connected Account — pick the Todoist account this trigger should watch.
  • Workflow Trigger Name — a meaningful label, e.g. ‘New Support Task’.
  • Filters → Project — pick a project to scope to (helper text reads ‘Only trigger for tasks in this project’). Leave empty to fire on tasks in any project.
  • Add filters (optional) — layer on additional conditions (label, priority, due-date range).
Step 3: Test the trigger
  • Click Find new records inside the Test your trigger panel.
  • If no matching records appear, add a task to the target Todoist project and wait one polling cycle (5 minutes), then re-fetch.
  • Select the returned record as the mapping reference.
  • Click Save trigger.
image
Example: Setting Up an Action (Create task)
This walkthrough creates a Todoist task from a workflow event — the most common outbound-to-Todoist pattern.
Step 1: Add the action
  • Inside the workflow, click Add to insert a new step.
  • Open the Apps tab and select Todoist.
  • Choose Create task from the action list.
Step 2: Configure the action
  • Connected Account — pick the Todoist account where the task should be created.
  • Action Name — e.g. ‘Create Task from Form Submission’.
  • Project — pick from the dropdown. Defaults to Inbox if not specified. Use Find projects upstream to resolve the project ID from a project name if it isn’t known at build time.
  • Title (required) — the task title. Keep it concise for clean rendering in Todoist’s task lists.
  • Note — a detailed description for the task, if the title alone doesn’t carry enough context.
  • Due Date (Human Formatted) OR Due Date (Raw Formatted) — pick one, not both. See ‘Working with Due Dates and Deadlines’ above.
  • Deadline Date (optional) — hard deadline in YYYY-MM-DD. Todoist deadlines don’t support a time component.
Step 3: Test the action
  • Click Test action.
  • Confirm — this creates a real task in Todoist. Use a clearly-marked title (‘TEST — DELETE’) if testing against a production project.
  • Save the action and run a full Test workflow before publishing.
image
image
How to Test Triggers and Actions
Always test before publishing. Testing locks the payload schema and gives downstream steps a real record to map against.
Test a trigger
  • Inside the trigger panel, click Find new records.
  • If no matching records appear, create or complete a task in Todoist (or create a project) and wait one polling cycle (5 minutes), then re-fetch.
  • Select the returned record as the mapping reference.
Test an action
  • Inside the action panel, click Test action.
  • The action runs against the live Todoist account — real tasks, comments, or projects are created.
  • Verify in Todoist and clean up test records afterwards.
Common Use Cases
Use Case 1: Form submission → Todoist task in the right project
Goal: Route inbound requests into Todoist as tasks with the right project, labels, and priority.
Workflow Setup:
  • Trigger: Form submission
  • Optional: Branch on form input to determine the right project or priority
  • Action: Find projects (resolve the target project ID by name)
  • Action: Create task (title from form, note with the full submission body, priority based on urgency signal, labels for team routing)
Example: A customer submits a support request marked ‘urgent’. The workflow finds the ‘Support Backlog’ project and creates a P1 task with the full request as the note, labeled ‘external-report’ — the support lead sees it in Todoist within seconds without leaving their task list.
Use Case 2: Task completed → close the loop in the platform
Goal: Take action when a Todoist task is marked complete.
Workflow Setup:
  • Trigger: New completed task (filter by project)
  • Action: Match the task back to the originating CRM contact (via a stored task ID or a label carrying the contact reference)
  • Action: Update contact / send notification / advance a stage
Example: A ‘Follow up with Acme’ task is marked complete in the AE’s Todoist. Within 5 minutes, the CRM contact’s custom field is updated (‘last touched: today’) and the deal stage is bumped — Todoist stays the AE’s working list, and the CRM records get updated for free.
Use Case 3: Team task with due date and label
Goal: Create a task on a shared project with proper metadata for routing and reporting.
Workflow Setup:
  • Trigger: Any operational event needing follow-up
  • Action: Create task (Project = shared team project, Priority = P2, Labels = ‘needs-review’)
  • Action: Add comment to task (context / links / instructions)
Example: A signup-abandonment automation creates a task in the CS team’s Todoist project with a note linking to the abandoned session, priority P2, and label ‘needs-review’ — a CS agent picks it up within their normal workflow.
We have introduced Jira as a native integration in Workflows. Customer-facing automations can now react when new issues are created or existing issues are updated in Jira — and drive Jira back the other way with a broad set of issue-lifecycle actions: create, update, link, comment, watch, attach files, log work, and move to sprint.
The integration ships with two triggers and eleven actions. Authentication is OAuth, preceded by a friendly Name and Email label. Actions and triggers include a Cloud Site selector so a single connected Atlassian account can target the correct Jira Cloud site even when the user has access to more than one.
Triggers (Jira → Workflows)
  • New issue
  • Updated issue
image
Actions (Workflows → Jira)
  • Discovery
  • Find users
  • Find projects
  • Find issues
  • Issue creation and updates
  • Create issue
  • Update issue
  • Issue enrichment
  • Add comment to issue
  • Add watcher to issue
  • Add attachment to issue
  • Add work log to issue
  • Issue relationships
  • Link issue
  • Move issue to sprint
image
Integration Setup
Connect Jira once via OAuth to begin using the triggers and actions across all workflows.
Steps:
  • Open the Workflow Builder and add any Jira trigger or action.
  • On the panel, click Connect your account.
  • The External Authentication Configuration modal opens. Enter a friendly Name (e.g. ‘Engineering Jira’, ‘Support Jira’) and the Email associated with this Jira account. Click Continue.
  • You will be redirected to Atlassian’s authorization screen. Approve the requested Jira scopes.
  • You will be returned to the Workflow Builder; the panel will update to show Connected.
  • On any Jira trigger or action, pick the target Cloud Site that this step should read from or write to. Required on Create issue; a filter on the triggers.
Use Cases
  1. Issue resolved → notify the customer
  • Updated issue (status = Done) → Find contact → Send resolution message with the fix summary
  • An engineer flips an issue to Done in Jira
  • Within 5 minutes, the workflow matches the issue back to the customer who reported it and sends a resolution notification with the fix summary
  1. Cross-issue linking on shared reports
  • New issue → Find issues (by shared reference) → Link issue (‘relates to’ or ‘duplicates’)
  • When a new issue is created with a shared external reference (support ticket ID, feature request ID), the workflow looks for existing Jira issues with the same reference and links them
  • Reduces duplicate work and keeps related issues discoverable inside Jira
Sample screenshots
image
image
Managing service bookings just got a whole lot easier! You can now fully edit
both paid and unpaid service appointments
without needing to cancel and recreate the booking. Whether your customer wants to add another service, change the assigned staff member, update add-ons, or apply a coupon after booking, you can make those changes seamlessly while keeping the booking, order, and payment information in sync.
This has been one of our most requested Services enhancements, and we're excited to finally bring it to you!
✨ What's New
Complete Booking Editing
  • Edit
    both paid and unpaid
    service bookings.
  • Add or remove services from an existing appointment.
  • Add, update, or remove add-ons.
  • Change the assigned staff member.
  • Apply, update, or remove coupons.
  • Update appointment details without recreating the booking.
Automatic Payment Reconciliation
  • Every edit automatically recalculates the booking total.
  • The appointment always reflects the latest payment status, including:
    Additional payment required
    ,
    Fully paid
    and
    Refund due
    .
  • If a refund is due, you can now
    process the refund directly from the appointment modal
    , making it quick and easy to settle payment differences without leaving the booking.
  • If a refund has been initiated but is still being processed,
    editing will be temporarily disabled
    until the refund is completed. During this time, you can still
    reschedule the appointment
    if needed.
  • This ensures payment records remain accurate while preventing conflicts during refund processing.
Smarter Order Management
  • Every service booking continues to be linked to its associated order.
  • When a booking is edited, the
    existing order is updated
    instead of creating a brand-new order.
  • This keeps your order history clean while ensuring payments, services, and booking details always stay in sync.
📱 Mobile App Support
  • Support for editing service bookings on the mobile app is complete and is scheduled to roll out during the
    week of July 20th
    .
⚙️ How to Use
  1. Open an existing
    Service Booking
    .
  2. Click
    Edit
    .
  3. Make any required changes, including:
  • Add or remove services
  • Modify add-ons
  • Change the assigned staff member
  • Apply or remove coupons
  • Update other booking details
  1. Save your changes.
  2. Review the updated payment status to see whether additional payment is required, the booking is fully paid, or a refund is due. If applicable, process the refund directly from the appointment modal.
💡 Why This Matters
  • Edit bookings without canceling and recreating appointments.
  • Easily accommodate customer requests after a booking has been made.
  • Keep payments, orders, and appointment details synchronized automatically.
  • Maintain a single order throughout the booking lifecycle for cleaner records and easier reconciliation.
  • Save staff time while providing a more flexible experience for your customers.
image
image
image
Summary
We've successfully migrated the Submission Page for Forms, Surveys, and Quizzes to HighRise! 🎉 This enhancement modernizes the underlying architecture, improving maintainability and preparing the platform for future innovations—all while preserving the familiar user experience.
What's New
  1. Migrated the Forms, Surveys, and Quizzes Submission Page to the HighRise framework.
  2. Retained the existing user experience to ensure a seamless transition.
  3. Improved the underlying architecture for better scalability and easier future enhancements.
🔑
Key Highlights
  1. Enhanced platform stability and performance through HighRise migration.
  2. Modernized codebase for simplified maintenance and faster development.
  3. No changes to submission workflows—users can continue submitting Forms, Surveys, and Quizzes as usual.
  4. Establishes a strong foundation for upcoming improvements and feature delivery.
⚙️
How It Works
The submission experience remains unchanged from an end-user perspective. Behind the scenes, the submission page is now powered by the HighRise framework, providing a more robust, scalable, and maintainable implementation.
📝
Notes
  1. No action is required from customers or end users.
  2. Existing functionality and submission flows continue to work as expected.
  3. This enhancement is focused on infrastructure modernization to support future platform growth.
What's new?
The
Goal
action now supports
User Replied
as a goal event. Workflows can now jump contacts directly to a goal when a team member replies to a conversation, making it easy to stop or redirect automations once human engagement has started.
How it works
Configure a
Goal
action and select
User Replied
as the goal event. When a user sends a reply through a supported conversation channel, the contact immediately skips ahead to the Goal step, bypassing any intermediate workflow actions. This allows your workflow to react instantly to team activity instead of continuing scheduled automation.
How to use it
  1. Add a
    Goal
    action to your workflow.
  2. Select
    User Replied
    as the goal event.
  3. Configure the actions that should run after the Goal is reached.
Why we built it
Automated workflows should adapt when your team steps in. By supporting
User Replied
as a Goal event, you can prevent contacts from receiving unnecessary automated messages, reduce duplicate communication, and seamlessly transition from automation to human-led conversations.
Simple examples
  • A lead is enrolled in a 7-day email nurture sequence. On Day 2, a sales representative replies to the lead's SMS. The workflow immediately reaches the
    User Replied
    goal, skips the remaining nurture emails, and moves the contact to the end of the sequence.
  • A support workflow sends reminder messages while waiting for an agent to respond. As soon as a support agent replies, the contact reaches the
    User Replied
    goal, preventing any additional reminder messages from being sent.
Additional Notes
  • The Goal is achieved only when a
    user
    sends a reply to the contact.
  • Contacts immediately jump to the Goal step, skipping intermediate workflow actions.
  • Ideal for ending nurture sequences, preventing duplicate messaging, and transitioning from automated to human conversations.
Preview
Kapture 2026-07-08 at 22
image
What's new?
The Wait action now supports User Replied as a wait condition. In addition to waiting for a contact to reply, you can now keep the contact waiting until a team member responds to the conversation before continuing to the next step. Combined with the timeout option, you can now build powerful SLA workflows that automatically escalate if no user reply is sent within your target response time.
How it works
When configuring a Wait action, select User Replied as the wait condition and optionally define a timeout. The workflow pauses until a user replies or the timeout is reached - whichever happens first. If a reply is detected, the workflow continues immediately. If the timeout expires first, you can route the contact through escalation steps such as notifications, reassignments, or reminders.
How to use it
  • Add a Wait action to your workflow.
  • Select User Replied and configure an optional timeout.
  • Define what should happen after a user replies or when the timeout is reached.
Why we built it
Response-time SLAs are critical for sales and support teams. This enhancement lets you automate first-response tracking, reduce manual monitoring, and ensure conversations are escalated when response targets are missed - all without building complex workflow logic.
Simple examples
  • A support workflow waits up to 30 minutes for User Replied. If an agent responds within the SLA, the workflow continues normally. If the timeout is reached first, it alerts a supervisor and reassigns the conversation.
  • A sales workflow waits 15 minutes for a representative to reply to a new lead. If no reply is sent before the timeout, the workflow creates an urgent task and notifies the sales manager to help prevent missed opportunities.
Additional Notes
  • The contact resumes as soon as a user sends a reply or when the configured timeout is reached.
  • If no timeout is configured, the workflow waits until a user reply is received.
  • Ideal for first-response SLAs, escalation workflows, and internal response-time automations.
Preview
Wu6q92VyhaeGimnHmw5C-W4ObBpAtbIOTw
Load More