Changelog · Oct 19 – 25 2026 · 28 changes
What shipped the week of Oct 19
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
Your first FlowApp is now ready in about a minute: ioZen reads your site, recommends one, and you watch a sample customer go through your Intake Bot. On Business and Enterprise, new cases reach the right person through rules you set, and a bell tells you about assignments and mentions. More of the app reads in Spanish, and your account emails arrive in your language.
Jay
0412 · car
Ready to quote · 86
Laura M. · 2022 Mazda 3, used for work. Her policy expires on Nov 15. She wants full coverage.
Assigned to Andrea
sample
Newest first
Change by change
- 8 NEW
- 10 BETTER
- 10 FIXED
- NEW
Your first FlowApp in about a minute
- The problem
- Your first FlowApp didn't start from your own website.
- What we did
- Signup now takes three short steps: your website, the problem that costs you time or customers, and your account. After you confirm your email, ioZen reads your site and recommends your first FlowApp: its Intake Bot, the phases of its Process Board and the outcome it is for. Pick it, or one of three alternatives, or describe your own. A sample customer then goes through your new Intake Bot while you watch, and the scored case lands on your board. Try the bot yourself from the link or the QR code. If you change your mind before you pick, what we built in the background is not charged.
- How it helps
- After signup, ioZen reads your site and recommends your first FlowApp, and a sample customer goes through your new Intake Bot while you watch.
- BETTER
Meet the people behind ioZen while you get started
- The problem
- Signup and your first FlowApp came without notes from the team.
- What we did
- Signup and your first FlowApp now come with a few notes from the team. Jay welcomes you on the first step and again on a new check-email screen, which shows the address we wrote to, opens Gmail or Outlook when that's where it went, and lets you resend the email or fix the address. Esteban shares a tip from our customer meetings while your Intake Bot is built and introduces himself on your FlowApp's Overview, and Mauricio is there when your plan runs out of room. The wait now shows what is done and about how long is left, the sample case is stamped as a sample, and when you reach your plan's FlowApp limit, New FlowApp says so up front with a Go Pro button instead of running the assistant first.
- How it helps
- Jay, Esteban and Mauricio show up along the way, and the wait shows what is done and about how long is left.
- BETTER
Account emails come from ioZen, in your language
- The problem
- Confirming your signup on your phone could fail if you signed up on your laptop.
- What we did
- The emails to confirm your signup, reset your password or change your email now come from ioZen (noreply@iozen.ai) in the language you signed up in, Spanish or English. Their links open in any browser, so confirming on your phone works even if you signed up on your laptop. Resetting your password lands on the screen to choose a new one.
- How it helps
- Account emails come from ioZen in the language you signed up in, and their links open in any browser.
- NEW
Filter contacts and campaigns by your own fields
- The problem
- Contacts and campaign audiences couldn't be filtered by your own contact fields.
- What we did
- Filter contacts and WhatsApp campaign audiences by any contact field: options, yes or no, numbers, dates and text. Imports keep each value's type, so imported lists filter right away. The import step lists what to include and offers a sample CSV built from your fields. The campaign form shows numbered steps and a summary with recipients and credits.
- How it helps
- You filter contacts and WhatsApp campaign audiences by any contact field, and imported lists filter right away.
- NEW
Every FlowApp opens on its home
- The problem
- A new Intake Bot in a FlowApp asked for your website again.
- What we did
- Open a FlowApp and you see its goal and how it works in four steps: where people start (your Intake Bots and their channels), how answers are saved (Record Types), the phases each case moves through on the Process Board, and what runs on its own, like scoring. Below, "Make it better" cards point to the next improvement, such as connecting WhatsApp or inviting your team, and count what you have done. A new Intake Bot in the FlowApp starts from its goal and context, so the wizard no longer asks for your website again.
- How it helps
- You open a FlowApp on its goal and four steps, with cards pointing to the next improvement.
- BETTER
Usage shows each credit wallet on its own
- The problem
- Plan credits and purchased credits weren't shown separately in Usage.
- What we did
- Settings → Usage now has one card for plan credits and one for purchased credits. Each card shows what's left, what it pays for, and where the credits went since the billing period started, with WhatsApp messages and Meta fees on separate lines. Purchased credits never expire, so that card also shows what was used before this period. The lines on each card add up to its total.
- How it helps
- You see what's left in each credit wallet, what it pays for and where the credits went this billing period.
- NEW
WhatsApp campaigns you can review
- The problem
- You couldn't see who was missing a value before creating a campaign.
- What we did
- Campaign fields render as labels and dates in the template language. Before you create a campaign, ioZen checks the audience and shows who is missing a value. The campaign page shows status changes live. You can edit or delete a draft.
- How it helps
- Before you create a campaign, ioZen shows who is missing a value, and you can edit or delete a draft.
- BETTER
WhatsApp intakes skip the country question
- The problem
- A WhatsApp conversation asked the country question even though the sender's country code already showed it.
- What we did
- Contact mapping has a new Country slot. Pick the Intake Bot question that asks for the country, and a WhatsApp conversation fills it from the sender's country code without asking. A choice question keeps the option that names that country; if none does, the country name is saved anyway. The web chat still asks it. Contacts now show their country, taken from that answer or from the phone number.
- How it helps
- A WhatsApp conversation fills the country from the sender's country code without asking, and contacts show their country.
- BETTER
The wizard builds early endings and conditional messages
- The problem
- The wizard didn't add early endings or conditions on messages.
- What we did
- When your description names a hard knockout, like a property outside your service area, the wizard adds a closing message that ends the conversation kindly for those people and records the reason. The plan shows these under "Ends early when" before you generate. Messages that only apply to some people get a "Show this when..." condition, so everyone else skips them.
- How it helps
- The wizard closes the conversation kindly for people your description rules out and records the reason, and conditional messages skip everyone else.
- NEW
Case distribution and private cases
- The problem
- New cases had to be sorted to the right person by hand.
- What we did
- New cases can now reach the right person without anyone sorting them by hand. In Settings, Distribution, build ordered rules on country, channel, Intake Bot, board or score, and give each rule a pool of team members. Cases go to the pool in rotation or to whoever has the fewest open cases. A fallback covers everything else, or leaves the case unassigned for admins. Members on pause are skipped, a tester shows who would get a case without moving the rotation, and each case shows which rule assigned it. Case distribution is available on Business and Enterprise. Separately, the new Members only see their cases setting in Settings, Team limits members to the cases they work on. Owners and admins still see every case. It works on every plan and is off by default.
- How it helps
- New cases reach the right person through ordered rules, and you can limit members to the cases they work on.
- BETTER
Faster Home, navigation and Intake Bots
- The problem
- The app showed a blank screen while it started up.
- What we did
- The app now shows the sidebar and page layout as soon as it loads, instead of a blank screen while it starts up. Moving between sections shows the page outline right away. Home loads its numbers in fewer steps, and public Intake Bots download much less code before the first question appears.
- How it helps
- You see the sidebar and page layout as soon as the app loads, and public Intake Bots download much less code before the first question.
- NEW
Notifications: one bell, mentions, and fewer emails
- The problem
- You had no bell for what teammates needed from you.
- What we did
- A bell next to the workspace logo shows what teammates need from you: cases assigned to you, mentions in case comments, new cases on boards you follow, and comments and phase changes on cases you follow. Type @ in a case comment to mention a teammate. You follow a case when you create, comment on, get assigned or get mentioned on it, and you can follow or unfollow any case, board or conversation. In Settings, Notifications, choose in-app or email for each category. Email is now on by default only for assignments and mentions, and each email waits 5 minutes and is skipped if you already read it in ioZen. New-case and escalation emails are off by default and show up in the bell; turn email back on for those categories if you want it.
- How it helps
- A bell shows your assignments, mentions and activity on cases you follow, and you pick in-app or email for each category.
- BETTER
Agent Blocks focus on advising and objectives
- The problem
- Agent Blocks had a Collector type that gathered answers, with typed outputs, decision-table enforcement, derived columns and option chips.
- What we did
- Agent Blocks now come in two types: Advisor, which answers questions from your sources, and Autonomous, which pursues an objective. The Collector type is gone, along with its typed outputs, decision-table enforcement, derived columns and option chips. Questions do that job with less cost and more predictable answers: place them after the Agent Block and route on its outcome. Reference tables stay, and every question queries them for matching rows. Existing Collector blocks no longer appear in the editor or run in live flows; answers they already collected stay in the submission data.
- How it helps
- Agent Blocks are Advisor or Autonomous, and questions after the block do the collecting, with less cost and more predictable answers.
- BETTER
Evidence shows the source line for every Agent Block reply
- The problem
- Only replies that named a store or place got the line-by-line Evidence view, and the rest showed whole passages.
- What we did
- Evidence under an Agent Block reply now lists what the reply states, each with the line from your knowledge or the table row behind it, for every kind of reply. Codes, emails and links are shown on their own, other sentences in full, and each line says which document and section it comes from. Before, only replies that named a store or place got this view, and the rest showed whole passages. A store named in a table row is no longer flagged as missing from the sources.
- How it helps
- You see the source line behind every Agent Block reply, with the document and section it comes from.
- NEW
Autonomous Agent Blocks on Business
- The problem
- Autonomous Agent Blocks weren't available on Business.
- What we did
- Autonomous Agent Blocks are now available on Business and Enterprise. Give the block an objective and it holds the conversation until it reaches an outcome, asking short Discovery questions along the way. Later steps route on that outcome, just like with an Advisor.
- How it helps
- You give an Autonomous Agent Block an objective, and it holds the conversation until it reaches an outcome that later steps route on.
- NEW
Cascading dropdowns from one Record Type
- The problem
- A Dropdown that searches your records couldn't filter its options by earlier answers.
- What we did
- A Dropdown that searches your records can now filter by earlier answers. Load one Record Type with a row per valid combination, add one Dropdown per level, and set each level's filter to "Answer to…" the questions above it: province, then city, then neighborhood, or university, then program, then format and term. Turn on Distinct values for every level above the last so each option shows once. Changing an earlier answer clears the levels below it, and a submission with a combination that is not in the table is rejected. Works on the web and on WhatsApp, including inside branches.
- How it helps
- You build chained Dropdowns from one Record Type, like province, then city, then neighborhood, and each one filters by the answers above it.
- BETTER
Rename an Intake Bot from its menu, and more of ioZen in Spanish
- The problem
- Several screens didn't read in Spanish when your workspace or bot was in Spanish.
- What we did
- Rename an Intake Bot from its actions menu; the header updates right away. A new question added with nothing selected goes at the end of the list. Process Boards, the Branching editor, submission details, Record Type imports and file uploads now read in Spanish when your workspace or bot is in Spanish, including card titles and card history. Switches for the default route and Branching now have names for screen readers.
- How it helps
- You rename an Intake Bot from its actions menu, and Process Boards, Branching and submission details read in Spanish.
- BETTER
Spanish submission exports, and AI copy without loose ends
- The problem
- Submission exports didn't use your language for column headers, and AI copy could leave a label like "Número de cédula:" with no answer.
- What we did
- Submission exports use your language for column headers, and duplicates are named "Copia" in Spanish. Share link errors and the public bot's not-found page read in Spanish too. AI content blocks drop a line like "Número de cédula:" when that answer is missing. Names an agent reads from a table row no longer show as unsourced. Searching variables only matches what you type, and the bot name now sits first in Settings › General. The credits notice no longer blocks the buttons under it.
- How it helps
- Exports use your language for column headers, and AI copy drops a line when its answer is missing.
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
Private answers stay private after the bot finishes, and assignment rules sign their notifications
Private answers stay private in every branch, and more of the app in Spanish
Rewording a live question no longer hides its earlier answers
See 7 more fixes
Build visibility conditions at your own pace
Action Blocks can map questions inside branches
AI summaries leave out what wasn't answered, and cleaner retries
AI copy in your Intake Bots says only what really happened
Yes / No questions show their choices in Stepper and Immersive
Record dropdowns and private answers work inside branches
New Intake Bots send cases to your board, and AI never sees private answers