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.

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.

Choose one:

Step 2: Filtered Use Case Dropdown

If Marketing is selected only “Marketing” is available and if Informational is selected then,

Age gating is now automatically enforced when “Age gated content” is selected OR “Financial services / loan arrangement” is selected

Date of Birth (mandatory when triggered)

Users can preview:

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.

This feature is currently in experiment mode, live on two fields within Advanced Settings for the and Actions. Results from this test will determine broader rollout.

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.

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.

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.

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.

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.

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.

The Connect Call (IVR) action now supports an optional Call Whisper message. When a call is transferred to another number, you can play a private “heads-up” message to the person who answers before the caller is connected.

If Add Whisper Message is toggled on, the system plays your configured message to the call recipient first, then connects the caller. You can control the message text, voice, and how many times it repeats (loops).

Transferred calls often arrive with zero context. Call Whisper helps your team answer confidently by sharing key details up front - without the caller hearing it.

Users had reported inconsistent behavior - the custom value picker would fall back to the campaign variable when UTM Campaign (Last Attribution) was empty, but If/Else conditions would not. This caused workflows to branch unexpectedly.

If/Else conditions now correctly apply the same fallback logic as the custom value picker for UTM Campaign (Last Attribution).

If UTM Campaign (Last Attribution) is empty, If/Else conditions will now automatically use the campaign variable as a fallback, ensuring consistent behavior across both areas.

You can now use company-based variables inside contact based workflows. In addition to contact fields, you can reference company details like company name, phone, email, website, address, and other company fields. These are available in both the Custom Value picker and If/Else branches.

When building a workflow, company fields now appear alongside contact fields in the variable picker. If a contact is associated with a company, the workflow can dynamically pull that company’s details into messages, notes, and conditions, or use them to drive If/Else logic.

Many users manage contacts tied to businesses. This update removes the need for workarounds and manual mapping, making it easier to personalize communication and automate decisions based on company-level data.

Every workflow trigger now includes a built-in, human-readable description that explains what the trigger does and when it fires. Descriptions are visible directly within the Workflow Builder when browsing, selecting, or editing triggers.

Open the Workflow Builder and click to add or edit a trigger. Each available trigger now displays a clear description of its function, allowing you to select the right trigger with confidence without needing to reference external documentation.

Trigger descriptions reduce guesswork during workflow setup, making it easier for both new and experienced users to identify the correct trigger quickly and build automations faster.

Businesses can now define a Cost Price and Margin for every product price or variant — giving you a clear, built-in way to track profitability without relying on spreadsheets or external tools.

Once configured, cost data flows into your transaction exports, invoices, and calendars — so you always know what you're making on every sale.

3rd of March, 2026

Labs (opt-in beta)

Voice: Call Transcription

---

We've upgraded the transcription engine powering voice call transcriptions. This brings multi-lingual transcription and improved accuracy for English too, without any change to your existing pricing or rebilling setup.

---

Transcriptions now support 10 languages: English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian, and Dutch.

No language selection required. The spoken language is detected automatically.

If the conversation switches languages during a call, transcription continues to work correctly. No manual intervention needed.

Each transcription includes timestamps for easier reference and review.

---

---

This feature is available as a . To enable:

We’ve significantly improved how work in Rentals to make date and time behavior clearer, more intuitive, and easier to configure.

With this update, businesses can now , giving them full control over whether customers choose dates only or dates and times — without relying on hidden global settings.

Previously, booking behavior (such as time selection, duration calculation, and multi-day pricing) could depend on global setting configurations, leading to accidental multi-day charges and confusion around rental start/end times.

Booking logic is now explicit, visible, and self-contained within each listing — so businesses can clearly understand how bookings are calculated and charged.

You now see three clearly defined :

Each mode now has visible, predictable behavior — with no hidden dependencies.

This is perfect for vacation rentals, overnight stays, and date-based pricing models.

For listings with predefined booking durations:

To prevent unsupported configurations:

This ensures only valid combinations can be selected.

To ensure a smooth transition: