Changelog
Follow up on the latest improvements and updates.
RSS
new
Email Builder
Export email marketing data 🚀
You can now export email performance data directly from the Email Stats section as a CSV file.
⭐
What’s New
- Users can generate exports for:
- All campaigns
- Email marketing campaigns only
- Workflows only – at an individual email action level
- Bulk actions only
2. The exported CSV is sent via email as a secure download link, valid for 30 days, making it easy to access and share.
3. All exports include key performance metrics such as deliveries, opens, and clicks.
4. Recent Downloads section under settings to easily track downloads made in last 30 days.
🚀
Impact
- Simplifies performance analysis across campaigns and workflows
- Makes it easier to download, share via email, and report on email marketing results
✅
How to Use It
- Ensure you have enabled it in Labs

- Navigate to Marketing → Email
- Click on the Statisticstab
- Click Export

- Add the email address(es) where you want to receive the file and proceed

- To access past exports, go to Settings → Recent Downloads

fixed
Automations
Fixed: 'Assign to User' Now Skips Inactive Users
Overview
In workflows using the Assign to User action with Split Traffic, deactivated or deleted users were not revalidated at runtime. This could cause contacts to be assigned to inactive users, leading to missed follow-ups.
What’s new
The Assign to User action now validates each user’s status when the step runs and skips any inactive or deleted users.
What’s changed
If a user in the configured Split Traffic list is no longer active, they are excluded from assignment at execution time.
Additional Notes
- The existing split distribution order does not reset. Traffic continues to distribute as if the deleted user never existed.
- If only one user was configured and that user is deleted, the step is skipped.
new
Automations
Standard Builder: Now with Sticky Notes 2.0
What’s new?
Sticky Notes 2.0 is now available in the Standard Builder. Previously available in the Advanced Builder, you can now add images/logos, color-code branches, and leave rich annotations directly inside your workflows workflows.
How it works
Use the Sticky Note tool on the Builder canvas to drop notes anywhere in your workflow. Customize with colors, formatted text, and embedded images or links. Resize and position them to label sections or branches.
How to use it
- Open a workflow in Standard Builder.
- Click Sticky Note from the left toolbar.
- Add text, choose a color, and optionally embed an image or logo.
Why we built it
Teams using workflows needed better collaboration and context-sharing. Now you can brand workflows, leave setup instructions, and document logic directly on the canvas - without switching tools.
Additional Note
- Sticky Notes are visual only and do not affect automation logic.
Preview:


new
improved
Automations
AI Builder: Post Generation To Do List
What's New
After AI Builder generates a workflow, a new To Do List now surfaces in every action and trigger that still needs human input - so nothing gets missed before your workflow goes live.
Built on top of the existing Workflow Highlights system, the checklist consolidates all incomplete items into one actionable view.

How It Works
- Generate a workflow using AI Builder.
- A To-Do List automatically appears, highlighting every action or trigger that requires your input.
- Click the pencil icon next to any item to jump directly to that step on the canvas.
- Complete the required fields and your workflow is ready to publish.
Why This Matters
Certain inputs require a human decision, connecting integration credentials, selecting an account, choosing a pipeline, or defining which step to wait for. The To-Do List makes these gaps visible upfront, reducing the risk of incomplete workflows going live and affecting contacts or system performance.
👀
What’s New?
- Added Conversion Locationselection at Ad Set level:
- Instant Forms (default)
- Website
- Website and Instant Forms

- Introduced Dataset (Pixel)selection (required for Website & Hybrid).
- Added Conversion Eventdropdown for both website and Hybrid(Instant form and Website).
- Added Destination URL fieldat Ad level (required for Website & Hybrid).
- Hybrid support now allows both Lead Form + Website URLin the same ad.
👷
How It Works:
- Select Objective: Lead Generation.
- At Ad Set level, choose Conversion Location:
- Instant Forms> Lead form only (existing behaviour).
- Website> Requires Dataset + Conversion Event.

- Website & Instant Forms> Requires Dataset + Conversion Event.

- At Ad level:
- Website > Destination URL required.

- Instant Forms > Lead Form required.
- Hybrid > Both required and then Meta optimises which one to show to users as per their optimisation engine rules.

- Publish is blocked if required fields are missing.
⭐
Why It Matters:
- Brings HL closer to Meta Ads Manager parity.
- Enables website-based lead optimizationusing Pixel events.
- Supports hybrid lead collection(Website + Instant Forms).
- Improves performance flexibility for advanced advertisers.
📝
Notes:
- Conversion Location cannot be changed after publish (Meta limitation).
- Instant Forms remains default for backward compatibility.
- Reporting adapts dynamically based on selected conversion location.
improved
SaaS Mode
Dashboard
Enhanced Usage Export from Agency Dashboard: Rebilling Status Included for Sub-Accounts
We’ve improved the Agency Dashboard Usage Export to give you clearer visibility into potential revenue leakage caused by rebilling being turned off at the sub-account level.
What’s New
The “Costs” sheet in the Usage Export file now includes a new column that shows the Rebilling Status (Enabled/Disabled) for each product per sub-account.
This enhancement applies at the product level, allowing you to see rebilling configuration alongside actual usage costs.
What Problem This Solves
Previously, agencies had no easy way to identify:
- Sub-accounts generating usage costs where rebilling was disabled
- Products consuming wallet credits or direct costs without being passed through
- Prior month usage that resulted in absorbed expenses
- Revenue leakage caused by configuration gaps
Because this visibility was not available in filters or dashboard views, agencies had to manually cross-reference settings across multiple screens — making the process time-consuming and error-prone.
How You Can Use It
With this update, you can now:
- Before exporting report, turn off toggle "Include only rebilled transactions" then Export the Usage Report from the Agency Dashboard
- Open the “Costs” sheet
- Filter by Rebilling Status = Disabled
- Identify high-usage sub-accounts where costs are being absorbed
- Use filters or pivot tables to:
- Calculate total absorbed costs
- Analyze by product
- Review by sub-account
- Quantify missed revenue opportunities
This makes it significantly easier to detect configuration issues and take corrective action quickly.
Why This Matters
- Prevents Revenue Leakage – Quickly identify costs not being rebilled
- Improves Profitability Tracking – Understand true margins per sub-account
- Reduces Manual Audits – No more cross-checking rebilling settings separately
- Supports Better Financial Decisions – Act on real usage data with clarity
This is a fast, actionable enhancement designed to give agencies immediate control over absorbed usage costs while more advanced dashboard-level reporting improvements are in development.
improved
new
Calendar
🔕 No External Update Emails for “Showed” & “No Show” Status Changes
🧭 Overview
We’ve improved how appointment status changes behave when marked as
Showed
or No
Show
.Previously, updating these statuses would upload the event to connected calendars (Google, Outlook, iCloud), which triggered external
event update emails
to attendees — even though nothing meaningful had changed from their perspective.With this update, marking an appointment as Showed or No Show will no longer push updates and emails to third-party calendars.
🚀 What’s Changed
✅ No Event Update Emails for “Showed” or "No Show"
Changing the status to "
Showed
" or "No Show
"will no longer trigger external update emails.✅ Internal Tracking Still Works as Expected
Status changes are still reflected inside the system for reporting, and automation logic — only external calendar updates has been adjusted.
🎯 Why This Matters
- Prevents unnecessary “Appointment Updated” emails
- Avoids confusion for customers
- Keeps external calendar behavior clean and intentional
- Ensures status tracking remains operational, not customer-facing
new
Phone System
Pre-Built A2P Campaign (Widget-First) Registration Flow
We’re launching a Pre-Built A2P Campaign (Widget-First) registration experience designed to reduce carrier rejections, eliminate manual compliance writing and effort, and ensure faster A2P submissions while also reducing rejection risk.
✅ What’s New
⭐ Pre-Built Campaign (Recommended Path)
Users can now select : Pre-built campaign (Chat Widget) during A2P registration right as they are about to start Campaign registration in the Standard A2P flow.
This flow:
- Enforces Chat Widget as the only opt-in method
- Automatically generates compliant consent language
- Locks required compliance elements
- Prevents financial/marketing misclassification
- Reduces rejection risk

🧭 Streamlined Messaging Use Case Selection
Step 1: Message Type
Choose one:
- Marketing / Promotional
- Informational / Non-Marketing

Step 2: Filtered Use Case Dropdown
If Marketing is selected only “Marketing” is available and if Informational is selected then,
Select from:
- 2FA
- Account Notification
- Customer Care
- Delivery Notification
- Fraud Alert
- Higher education
- Polling and Voting
- Public Service Announcement
- Security Alert
🔒 Financial + Marketing Conflict Protection
- If a user selects "Marketing / Promotional" AND Financial services / loan arrangement, The flow is blocked.
- Users must switch to Informational to proceed. This prevents high-risk carrier rejections.
🔞 Automatic Age Gating (Carrier-Compliant)
Age gating is now automatically enforced when “Age gated content” is selected OR “Financial services / loan arrangement” is selected
When triggered:
- A mandatory Date of Birth (DOB) field appears in the widget
- Cannot be removed
- Required before submission
- If neither condition applies then DOB field does not appear
🧩 Auto-Generated Compliance Widget
The system now automatically:
- Creates a compliant Chat Widget
- Injects business name into disclosure
- Applies locked disclosure language
- Adds STOP/HELP language
- Adds data rate + frequency disclosure
- Attaches widget to campaign
- Generates embed code

Users cannot:
- Edit disclosure text
- Remove required fields
- Add consent checkboxes
- Edit any compliance fields
- Select alternative opt-in methods
🧱 Final Widget Structure
Required (Locked) :
- Phone number (mandatory)
- Disclosure block
- STOP/HELP language
- Data rate disclosure
- Frequency disclosure
Conditional:
Date of Birth (mandatory when triggered)
Optional :
- Name
- Message
- UI styling (colors + header text only)
Removed:
- Email field
- Consent checkbox
- Custom compliance fields
- Editable disclosure text
- Opt-in method selector
👀 Read-Only Widget Preview
Users can preview:
- Full widget
- Disclosure placement
- DOB field (if triggered)
- Preview is not editable.

🔐 Locked Final Consent Review
Before submission:
- All fields auto-filled
- Non-editable
- Sample messages generated
- Opt-in method defined
- Website compliance checklist confirmation required

Who Is Impacted?
- Agencies or sub-accounts submitting new A2P campaigns
- Users launching marketing-only campaigns
- Users launching informational-only campaigns
- Campaigns involving financial or age-gated content
Benefits of This Update:
- Reduced A2P rejection rates
- Prevention of financial/marketing misclassification
- Automatic age-gating compliance
- Stronger carrier and CTIA alignment
IMPORTANT
: This Campaign registration flow is not available for "mixed use-case" and "Sole-prop" campaigns.new
improved
Automations
AI Powered Field Tooltips
What's New
Workflow action fields now include AI powered tooltips that provide contextual explanations directly within the builder. Building on the existing "Learn More" AI capability available on actions and triggers, this extends AI assisted guidance to the individual field level.
When hovering over the ℹ️ icon next to a field, users see a brief description of the field's purpose along with an "Explain" call-to-action. Clicking "Explain" opens the AI assistant with a detailed, conversational explanation of that field — including how it impacts the workflow. Users can ask follow-up questions and clarify doubts without leaving the builder.

Current Availability
This feature is currently in experiment mode, live on two fields within Advanced Settings for the
Manual Action to SMS
and Manual Action to Call
Actions. Results from this test will determine broader rollout.What's Next
Based on experiment outcomes, AI powered tooltips will expand to all fields across all actions and triggers — making the workflow builder more self explanatory and reducing the learning curve for new users.
Why This Matters
Users no longer need to leave the builder to search documentation or guess what a setting does. Combined with the existing "Learn More" capability on actions and triggers, field-level AI tooltips provide instant, contextual clarity right where it's needed.
What’s new?
IVR Connect Call now exposes new variables: 'Answered By User ID', 'Answered By Device', and 'Answered By Phone Number'.
You can use Answered By User ID inside the Assign User action to automatically assign the contact to the person who picked up the call. These variables are also available in the custom variable picker, so they can be referenced in other workflow actions like Notes, SMS, Email, and more.
How it works
When a call reaches your IVR and is routed through Connect Call, the system captures who answered. In workflows, you can reference these values dynamically - most commonly passing Answered By User ID into Assign User to set ownership, or inserting the other variables into messages and notes.
How to use it
- Add an Assign User action after your IVR → Connect Call step.
- In the Users field, switch to Dynamic and select Connect Call → Answered By User ID.
- Save and publish the workflow.
Why we built it
Previously, contact ownership had to be set manually or assigned to a fixed user. Now, ownership automatically matches the person who actually spoke to the lead - keeping follow-ups, tasks, and reporting accurate.
Use Case example
A lead calls your IVR and the call is routed through Connect Call. John answers the phone. The workflow uses Answered By User ID from the Connect Call step, and the contact is automatically assigned to John.
Additional Notes
- Works for both single or multiple users configured in Connect Call.
- Assignment happens only if the call is successfully answered.
- Uses the first connected user as the owner.
- Assign User will not work if the Connect Call routes to a Custom Phone Number (no associated user ID).
- To assign dynamically, you must use Answered By User ID (not device or phone number).
Preview

Load More
→