What's new

What's new?

Agency Settings has a new Workflow Settings page. It is the home for agency-level workflow configuration, and the first option on it is the default builder for workflows. Pick Standard or Advanced once at the agency, turn on Apply to all sub-accounts, and every owned sub-account opens new workflows in that builder. Sub-accounts you create later inherit the agency default at creation.

How it works

Workflow Settings sits in the Agency Settings sidebar. The default builder section holds the Standard and Advanced choice plus the bulk-apply toggle. Turning the toggle on pushes the selection down to every sub-account you own, so nobody has to set it account by account. The setting decides which builder a new workflow opens in. Workflows that already exist keep the builder they were built on.

How to use it

• Go to Agency Settings and open Workflow Settings.
• Pick Standard or Advanced under default builder.
• Turn on Apply to all sub-accounts and save.

Why we built it

The default builder only had a single place inside Global Workflow Settings. An agency running 200 sub-accounts had to set the builder in each one.

Now there is one page for it. Set the builder once, apply it across the estate, and know that a sub-account spun up next month starts on the same one. As more workflow components ship, they land on this page instead of somewhere else.

Additional Notes

• The bulk-apply toggle covers sub-accounts the agency owns.
• The page is built to take more options over time which will come up in the future

Preview

Overview

We've refreshed the user management experience with a new interface across both Agency and Sub-account. The same actions and the same data you rely on today - now cleaner, better organized, and easier to navigate.

My Profile has been reorganized into tabs, the user listing and Create/Edit User flows have been redesigned, and the "Team" and "My Staff" labels are now unified under a single, consistent name: Users.

This update is now available and can be turned on from Labs.

What's new?

My Profile, reorganized into tabs - Your profile settings are now split into clearly labeled tabs instead of one long page.

Agency: two tabs - General tab carrying personal details and Security tab carrying details like password, sign out everywhere and two-factor authentication

Sub-account: five tabs - General, Security, Calendars, Conversations, and Notifications - all with a refreshed UI.

A streamlined Notifications tab (Sub-account) - The Notifications tab now gives you clear, channel-wise visibility into your notifications, replacing the earlier cluttered layout.

"Team" and "My Staff" are now "Users" - We've standardized the naming across the platform. "Team" (Agency) and "My Staff" (Sub-account) are now both called Users, for a consistent experience everywhere. Only the label changes - the screen works exactly as before.

Refreshed Users listing - An updated look and feel for the screen where you view and manage users.

Redesigned Create and Edit User flows - The flows for adding and editing users have been refreshed, including how permissions are managed.

Clearer Roles & Permissions - The Roles and permissions tab in the Edit User flow has been reworked for clarity:

Navigate permission modules from a left-hand panel instead of scrolling through the entire page.

Scopes within each module are shown in an accordion, collapsed by default, to keep the view clean.

Search for a module to jump straight to it - results open in an expandable format.

Refreshed Sub-account user settings tabs - In the Sub-account Edit User flow, the additional tabs also have a revamped UI: Call and voicemail settings, User availability, Calendar configuration, and Notification settings.

My profile - Agency view: General tab

My profile - Agency view: Security tab

My profile - Sub-account view: Personal details tab

My profile - Sub-account view: Notifications tab

Users listing page

Edit user - Sub-account view: Roles and permissions

Additional notes

• This is a UI and navigation refresh. The underlying capabilities and permissions stay the same.
• Your existing profile settings, user data, and permission configurations carry over unchanged.
• The rename to "Users" is a label change only - no impact on functionality.
• The tabbed My Profile layout gives us room to add more configurations in the future without cluttering the page.

How to enable

1. Navigate: Go to Labs in your Agency settings.
2. Enable: Turn on ‘User Management - UI Refresh’
3. Explore: Head to My Profile and Users to see the new experience.

Roll-out & availability

• Release date: Sep 07, 2026
• Status: Live via Labs

What's New

If your plan is priced in Hungarian Forint (HUF), the price shown in your client portal Billing view now matches exactly what your agency configured. Previously, this view could show an amount 100 times higher than your actual plan price (for example, a 9,700 HUF plan appeared as 970,000 HUF).

Why It Matters

You'll now see the correct, accurate price for your HUF plan every time you check your billing details — no more confusing or alarming numbers that don't match what you're actually being charged.

Notes

• This fix applies to plans configured in Hungarian Forint (HUF).
• No action is needed on your part — the correct price now displays automatically.

AI Studio just leveled up from “generate a pretty frontend” to build a real full-stack web app. New projects run on TanStack Start: server-rendered pages, real backend (server functions and REST APIs), and a proper secrets vault. Prompt it. Ship it. Watch search engines, social cards, and users all see the same live site.

New AI Studio projects are born full-stack. Not a static SPA pretending to be a website: a React app with a server, routes, APIs, and a published runtime.

Every page is rendered on the server, on every request. Google, LinkedIn, Slack unfurls: they get real HTML (titles, descriptions, headings, the actual copy). No empty #root. No “enable prerender and hope.” Disable JavaScript and the page is still there. That’s not a tweak. That’s how the web is supposed to work.

Need to load data, talk to an API, or keep logic off the client? AI Studio can write server functions that run on the server and stay there. The browser calls them. It never sees the implementation. Your secret sauce stays secret.

Need a public API? You can ship REST endpoints too (/api/...): JSON in, JSON out, GET/POST, webhooks, curl. Server functions power the app from the inside. Server routes are the HTTP API the rest of the world can call.

Drop API keys and tokens into Secrets. They never land in the client bundle, never get pasted into chat, never show up in View Source. Preview and production both get them. Your app can finally call real services without you shipping credentials to every visitor.

SSR + server functions + REST APIs + secrets is the combo: multi-page sites with unique URLs, server-backed data, public APIs, private integrations, and a publish path that’s a live app, not a static zip. Describe the product. AI Studio builds the stack.

They keep running the same way. Nothing changes for existing Vite/React apps. A migration guide to move them onto the new framework is coming soon.

You can now transfer calls from the mobile app to staff members who don't have a personal phone number.

How to use this?

1. Make a regular call from the mobile app (outbound or inbound)
2. In the active call, tap the transfer call icon at the top right corner
3. Go to the Staff Members tab and choose the staff member you want to transfer the call to. Device types they can receive the transferred call on are shown next to their name

1. Tap Call and Hold for a warm transfer, or Transfer and End for a blind transfer
2. The staff member receiving the transferred call can see that it's a transferred call, along with who transferred it. On iOS, the incoming call banner shows the contact name followed by "via" and the name of the staff member who transferred it — for example, John Doe via Michael Scott.

On Android, the incoming call screen shows Transferred call from Michael Scott

1. They tap Answer
2. The warm transfer can be executed as usual

Key points

1. Works for both warm and blind transfers
2. Works for both outbound and inbound calls
3. The mobile app now works as both transfer source and destination
4. Re-transferring a call (transferring a call that was already transferred to you) isn't supported yet
5. Transfers ring every device the staff member has set under "Forward calls to" at the same time: Web App, Mobile App, Phone, and SIP desk phone
6. Staff members with no device configured appear as disabled in the transfer list

Overview

We're introducing Working Hours for Conversation AI, giving business more control over when their AI agents respond to customers.

You can now set specific working days and hours for each agent, choose which channels should follow those hours, and configure what happens when a customer reaches out after business hours.

This helps business keep their AI aligned with their actual operating hours while still making sure after-hours customers are acknowledged and followed up with.

What's New?

1. Set flexible Working Hours for each agent - Choose the days and times when an AI agent should actively respond. You can set different hours for each day and add multiple time slots for breaks or split shifts.
2. Choose which channels follow Working Hours - Apply the schedule only to selected channels such as SMS, Email, WhatsApp, Instagram, Facebook, Chat Widget, Live Chat, and TikTok. Channels that are not selected can continue responding 24/7.
3. Use Contact or Business Timezone - Run the schedule based on each contact's local timezone or your business timezone.
4. Continue ongoing conversations after hours - If a conversation started during working hours, the agent can continue replying after closing time until the conversation becomes inactive.
5. Send an Off-Hours Auto-Reply - Automatically acknowledge customers who message outside working hours. You can add your own custom message and personalize it using supported custom values.
6. Notify your team about after-hours messages - Send email notifications to admins, users, assigned users, selected team members, or custom email addresses.
7. Automatically tag after-hours contacts - Add selected tags to contacts who message outside business hours, making it easier to identify, filter, and follow up with them.
8. Follow up when business hours resume - Automatically send a follow-up when the business reopens if the customer has not already received a response from the agent or a team member.

Additional Notes:

• Working Hours is optional. If it is not enabled, the agent continues responding at any time as it does today.
• Working Hours applies only to the channels you select. Other channels continue working normally.
• The Off-Hours Auto-Reply, notifications, and contact tags are triggered once per closed period, so customers will not receive the same acknowledgement for every message they send after hours.
• The business-hours follow-up is skipped if the customer has already received a response from either the AI agent or a team member.
• In Suggestive Mode, suggestions can still be generated after working hours for your team.
• If Followup Hours is also configured for Advanced Follow-Up, the agent's Working Hours takes priority for the channels included in the agent's schedule.
• Agents can still be manually activated outside their Working Hours when needed via conversation panel.
• Working Hours is configured per agent, so different agents can have completely different schedules.

You can now generate an image inside a workflow. The AI Image Generation action is available under AI Actions. Give it a prompt. An AI model creates the image, stores it at a public URL, and returns that URL as text.

This is a premium action. Each execution has an additional charge.

What's New

• Four models: Select GPT Image 2, Gemini 3 Pro Image (Nano Banana Pro), Gemini 3.1 Flash Image (Nano Banana 2), or Gemini 2.5 Flash Image (Nano Banana).
• Flexible prompts: Type the prompt yourself or insert a custom value. The prompt can come from a contact field, a webhook payload, or an earlier action.
• Enhance Prompt: One click expands a short prompt into a detailed one.
• Templates: Start from Product Mockups, Social Post, Promo Flyer, or Lifestyle.
• Quality: Set Auto, High, Medium, or Low. The default is Auto.
• Brand control: Apply your Design Kit and Brand Voice.
• Output control: Set the size, the background, and the file format.
• Automatic storage: Each image goes to Media Storage and returns an Image URL variable for the actions that follow.

Pricing

Image generation is billed per execution. The figures below show what a typical image costs. Most generations land in this range.

Note: Treat these figures as a planning estimate, not a fixed rate.

Your actual cost per image depends on how you configure the action. The main factors are:

• Model: The model you select.
• Quality: The level you set.
• Size: The size you generate at.
• Additional context: A Design Kit or Brand Voice passes extra context to the model, which can shift the cost.

How to Use

1. Go to Automation > Workflows.
2. Open a workflow, then add the AI Image Generation action.
3. Select the model and set the quality. The default is Auto.
4. Write the prompt. Type it in, or insert a custom value so the prompt comes from your data at run time.
5. Click Enhance Prompt or start from a template. Both steps are optional.
6. Open Additional Settings for the size, the background, the output format, the Design Kit, and the Brand Voice. This step is optional.
7. Save the action.

Important: The generated image is stored at a public URL. Anyone with the link can open it without a login. Keep this in mind when a prompt pulls in customer data.

Why This Matters

A workflow can now create a visual, not only move one you uploaded in advance. Use the Image URL in the actions that come after. You can attach it to an email or SMS, publish it to a social post, save it to a custom field, or pass it to a webhook. Because the prompt can come from your data, one workflow can produce a different image for every contact, or fill in an image URL for every row in a Google Sheet.

You can now analyze an image inside a workflow. The AI Analyze Image action is available under AI Actions. Give it an image URL and a prompt. An AI vision model examines the image and returns the answer as text.

This is a premium action. Each execution has an additional charge.

What's New

• Text extraction: Read the text from receipts, invoices, screenshots, and documents.
• Image descriptions: Receive a written description of the contents of an image.
• Flexible prompts: Tell the model what to look for and how to answer. The prompt field accepts custom values.
• Detail level: Set Auto, High, or Low. High is more accurate for small text. Low is faster.
• Two models: Select GPT-5.6 Luna or GPT-5.6 Tera.

How to Use

1. Go to Automation > Workflows.
2. Open a workflow, then add the AI Analyze Image action.
3. Select the model.
4. Enter the image URL. Use the output of an earlier step or a custom value.
5. Write the analysis prompt.
6. Set the detail level. The default is Auto.
7. Save the action.

Important: The image URL must be public. Anyone must be able to open it without a login. Do not use a link to a page that contains the image. Use the direct link to the image file. Files in Media Storage are already public.

Why This Matters

A workflow can now read the contents of an image, not only move the image from step to step. Use the output text in the actions that come after. You can save it to a custom field, send it in an email or SMS, pass it to a webhook, or send it to another AI action.

What's new?

Dynamic value chips have three states now instead of two. A dynamic value chip used to be valid or invalid, so anything the builder couldn't resolve came back red with "value not recognized". The new middle state is a yellow chip, and it covers values that are real on the platform but have no source in the workflow you have open. Giving a clear distinction between values that could render blank and values that won't render at all.

How it works

Every chip lands in one of three states:

• Blue, value available in this workflow. The workflow can fill it, whether that comes from the contact record, a system value like the current date, or an earlier step.
• Yellow, value not available in this workflow. The value is real on the platform, but nothing in this workflow supplies it, for example {{sheet.10.rowNumber}} in a workflow with no Google Sheets step. It renders blank unless another workflow passes it in through Add to Workflow with pass input trigger parameters.
• Red, value doesn't exist on the platform. Nothing on the platform matches it, for example {{applesheet.10.rowNumber}}, so no workflow will render it.

Spacing inside the handlebars stopped mattering too. The platform stores Attribution Url as {{ attribution.first.url }} with the spaces, so typing {{attribution.first.url}} used to come back red. Both forms match now.

Why we built it

Earlier all fields which wouldn't render would show an error state with a red chip. However you might drop {{invoice.url}} into an Add Notes action on a workflow that no invoice trigger starts, or hand a value from one workflow to another through Add to Workflow.

The red chip earlier called those values unrecognized and pointed you at the picker, so a configuration you built on purpose read like a mistake you had made. Splitting the states puts red back on the cases worth acting on. Red now means the value is wrong. Yellow means check whether something else supplies it.

Additional Notes

• Yellow is a warning, not a block. Save and publish the workflow as usual.
• Red still catches typos, for example {{contact.frist_name}}.
• This changes the UI only. Values resolve at execution time the way they did before, so anything that ran before still runs.

Preview

A missed call can be a missed opportunity, and your follow up text should not fail simply because the number your customer called cannot send SMS.

Previously, Missed Call Text Back always tried to send the follow up SMS from the same number your customer called. But some numbers are designed primarily to receive calls or may not currently be eligible to send SMS. In those cases, your text back could fail even when another messaging ready number was available in your account.

We’ve improved this experience. Secure Automation will now automatically choose an eligible sending number, helping more of your missed call follow ups reach your customers while staying aligned with messaging requirements.

The result is simple: more missed callers receive your follow up message, while your texts stay aligned with messaging requirements.

✅ Your Missed Call Text Back Has a Better Chance of Reaching the Customer

When a customer calls and you miss them, we’ll still try to text them back from the number they called first, as long as that number can send SMS.

If it can’t, system will automatically look for the next best option:

1. A number you’ve successfully messaged this contact from before
2. Your default outbound number
3. Another eligible messaging number available in the location

This is especially helpful when calls come through number pools, call tracking numbers, unverified toll free numbers, or other numbers that aren’t eligible to send SMS. Instead of attempting the text from a number that can’t send, we’ll use an eligible number when one is available.

Most of the time, nothing changes. The missed caller simply receives your follow up as expected.

In some cases, the SMS may come from a different number than the one they originally called. That’s intentional. We’re choosing a number that can actually send the message rather than letting an important follow up fail.

When someone calls your business and you cannot answer, that first follow up can be important for keeping the conversation going.

With smarter number selection, you can:

• 📩 Reach more missed callers instead of losing the follow up because one number cannot send SMS
• ⚡ Keep follow ups automatic without manually managing which number should be used
• 🛡️ Stay aligned with messaging requirements such as A2P and toll free verification
• 🤝 Respond to potential leads sooner and keep conversations moving even when you miss the initial call

In short, if you have an eligible number available, we’ll automatically use it to give your missed call text a better chance of reaching the customer.

• Answered calls will continue to work as before and will not trigger a text back.
• If Missed Call Text Back is disabled in your Phone System settings, no message will be sent.
• Your contacts’ communication preferences and DND settings will continue to be respected.
• If there is no eligible number available, you’ll see the failed attempt in the conversation along with the reason, giving you clear visibility into what happened.

The User login workflow trigger now fires for logins from the new Client Portal experience — not just legacy membership logins. We've also added a dedicated Client Portal category in the workflow trigger picker, so all Client Portal triggers live in one place.

🔑 New Client Portal logins now fire the "User login" trigger Successful logins from the new Client Portal experience now emit the same workflow trigger event as legacy membership logins. Any workflow already using the User login trigger will start running on these logins automatically — no reconfiguration required.

🗂️ New "Client Portal" category in the trigger picker A dedicated Client Portal category now groups all Client Portal triggers together:

User login — moved from Courses

Client portal file uploaded — moved from Membership

💬 Clearer helper text The User login trigger now spells out that it covers both legacy membership logins and logins from the new Client Portal experience — removing the confusion caused by its old placement under Courses.

Automate on Client Portal member login

• Open the Workflow Builder.
• Click Add trigger and search for User login.
• Select it under the new Client Portal category (previously found under Courses).
• Save your workflow — it will now fire on both legacy membership logins and logins from the new Client Portal experience.

Already using this trigger? No action needed. Existing workflows continue to run as-is and will automatically pick up login events from the new Client Portal experience.

Agencies on the new Client Portal experience previously had no way to automate off a member login, because the trigger only covered legacy memberships. Trigger placement was inconsistent too — login sat under Courses while file upload sat under Membership — making it unclear what each trigger actually covered. This update closes the gap and puts both triggers where you'd expect to find them.

🗓️ Effective Date

• October 1, 2026 → Verizon and 'Other' Category Carrier Fee Updates

To keep our pricing aligned with current carrier costs and maintain optimal deliverability across global telecom networks, we are updating carrier fees for messaging traffic sent to U.S. numbers via Verizon and select providers in the 'Other' category.

Key changes for outbound messaging via the Verizon network:

• Outbound SMS (Long Code, Short Code, Toll-Free, Authy & Verify): $0.0045 → $0.0050 per message
• Outbound RCS Rich: $0.0045 → $0.0050 per message

Key changes for outbound messaging via 'Other' Category Carrier network:

• Outbound SMS (Long Code, Short Code Group B, Toll-Free, Authy & Verify): $0.0040 → $0.0042 per message
• Short Code Group A SMS: $0.0025 per message (No change)

These updates stem directly from our downstream carriers in response to changing delivery and infrastructure costs across telecom networks.

Updating our rates ensures:

• Continued high-quality service and performance

• Reliable and optimised message delivery

• Direct alignment with global carrier pricing structures

🙏 Thank You

We understand how important clear and transparent communication is regarding billing updates. We are committed to keeping you informed well in advance to ensure these adjustments are as seamless as possible. No action is required on your end. The updated rates will apply automatically from the effective date.