Changelog · Oct 12 – 18 2026 · 16 changes
What shipped the week of Oct 12
Every week we tell you what changed in ioZen, why we did it and what you get out of it. Each change says which plans get it.
What changes for you this week
Conversations are now billed per message processed with AI, from 0.5 credits, and messages without AI are free; each submission shows where its credits went. On Business and Enterprise you can serve your Intake Bots from your own domain. And Agent Blocks check every sentence against what they read before they reply.
Jay
Case 0412 · Laura M.sample
What this case cost to serve
Messages with AI · 147 credits
Messages without AI · 6free
Total7 credits · $0.07
Newest first
Change by change
- 3 NEW
- 4 BETTER
- 9 FIXED
- BETTER
Agent Blocks check facts before they reply
- The problem
- Agent Block replies weren't checked against what the bot had read.
- What we did
- Before an advisor or autonomous Agent Block sends a reply, each sentence is checked against the knowledge it read and what the respondent said. A store, product, location, time, price or contact detail that is not there, or that belongs to another place, is removed, and the bot says it can't find that information instead. When the first search misses the question, the bot searches once more by the kind of place that would have the answer before replying. Reference tables are queried for the question: ask for a category and the bot gets every matching row and how many there are. In a case and in the Agent Block test, a check mark under each reply shows whether it was verified, and Evidence lists each store or place the reply names with the source line behind it.
- How it helps
- Each sentence is checked against the knowledge and the respondent's words before the bot replies, and a check mark shows whether a reply was verified.
- NEW
Serve Intake Bots from your own domain
- The problem
- Your Intake Bots could only be served from ioZen's standard links.
- What we did
- Business and Enterprise workspaces can connect their own domains in Settings → Domains, a subdomain like forms.acme.com or a root domain like acme.com. A TXT record proves ownership, an A or CNAME record points the domain at ioZen, and HTTPS is set up automatically. Each Intake Bot can be served at the root or at a path such as /claims from its share panel, and its settings list every public link in one place. Business includes 5 domains; Enterprise is unlimited. If a plan loses the feature, the custom URLs redirect to the standard ioZen links.
- How it helps
- You connect your own domain and serve each Intake Bot at the root or at a path, with HTTPS set up automatically.
- NEW
Start a WhatsApp conversation from the API
- The problem
- The API couldn't open a WhatsApp conversation from a CRM.
- What we did
- A CRM can open a WhatsApp conversation with an approved UTILITY or AUTHENTICATION template. The call finds or creates the contact by phone, routes the reply to an Intake Bot, and returns the message id. MARKETING templates are rejected. A live chat is left alone. The key needs the send:whatsapp scope, and the workspace needs the inbox.
- How it helps
- Your CRM opens a WhatsApp conversation with an approved UTILITY or AUTHENTICATION template, and the reply goes to an Intake Bot.
- NEW
Pay for a sponsored plan by card
- The problem
- A workspace on a sponsored plan couldn't pay by card from Billing.
- What we did
- A workspace on a sponsored plan can now pay by card from Billing, monthly or annual. It can keep its plan or pick another paid plan. Once the payment goes through, the sponsorship ends: monthly credits come from the paid plan and this month's usage starts at 0. Bonus and purchased credits stay. On a lower plan, features it does not include turn off.
- How it helps
- You pay by card from Billing, monthly or annual, and keep your plan or pick another paid one.
- BETTER
Bill Intake Bot conversations per message processed with AI
- The problem
- Conversation charges followed the number of model calls behind each message.
- What we did
- Intake Bot conversations on the web and WhatsApp are billed per visitor message processed with AI: from 0.5 credits per message, whatever the number of model calls behind it. Messages handled without AI are free. Charges settle in batches and appear as AI conversation in Settings → Usage and in each submission's Credits tab. Test submissions keep per-call pricing.
- How it helps
- You pay from 0.5 credits per visitor message processed with AI, whatever the number of model calls, and messages handled without AI are free.
- BETTER
Simpler plan comparison
- The problem
- The plan comparison repeated what every plan includes in each row, and some rows showed integration action blocks as unavailable on some plans.
- What we did
- The plan comparison now groups features that work together into one row: Integrations (including action blocks with deterministic, assisted and agentic execution, available on every plan), Agent Block with Knowledge, WhatsApp, analytics, developer access, and field security. What every plan includes is listed once instead of repeated in each row. We also fixed rows that showed integration action blocks as unavailable on some plans.
- How it helps
- You compare plans in fewer rows, with what every plan includes listed once.
- BETTER
Match submission credits with Recent operations
- The problem
- A submission's credits didn't line up with what Recent operations showed.
- What we did
- A submission's Credits tab now lists its credits by line, using the same labels as Settings → Usage, and each line adds up to that submission's rows in Recent operations. Recent operations show which submission each charge belongs to, with test submissions marked, and a link from the Credits tab opens Usage filtered to that submission. AI content blocks are labeled as such. Pricing is unchanged.
- How it helps
- A submission's credits are listed by line, each line adds up to its rows in Recent operations, and a link opens Usage filtered to that submission.
FIXED
What you reported is fixed.
Fewer snags for you and your clients while they're being served.
the fixes count too. they're most of it
Calculations and conditions can use questions from branches
Cases stay where you drop them on the Process Board
Clearer credit breakdown and complete WhatsApp delivery records
See 6 more fixes
Include ordinary AI operations in case credits
Show case pricing only when it applies and refresh usage history live
Keep setup progress moving when live updates drop
Buttons open links filled with the respondent's answers
Large submission exports download from the submissions page