Changelog · Nov 16 – 22 2026 · 28 changes
What shipped the week of Nov 16
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
This week we went past the form. Picture Mariana asking for a car insurance quote on a Tuesday night. Before she closes the chat, the Intake Bot has handed her the PDF with her estimated premium, she has signed it with her finger and chosen to pay by link, by bank transfer or later. If she replies to your email, the reply lands in the Inbox, which now comes with every plan. And a year later, 30 days before the policy ends, the renewal case opens on its own. Documents and signatures are in beta.

Jay
Car insurance quote
Newest first
Change by change
- 16 NEW
- 8 BETTER
- 4 FIXED
- BETTER
Every Intake Bot block named the same way
- The problem
- Some blocks were «Bloque de Contenido» with a capital, others just «Cálculo», «Cobro» or «Handoff», and some Spanish messages said «Agent Block» in English.
- What we did
- The + menu in the Intake Bot editor now names every block the same way: content block, action block, agent block, calculation block, payment block, handoff block and conversion block. In Spanish the handoff is now «Bloque de traspaso», and messages that said «Agent Block» in English now say «bloque de agente».
- How it helps
- You find each block by the same kind of name in the menu, the side panel, the messages and the manual.
- NEW
Cases that come in by a date
- The problem
- Renewals and anniversaries lived in a spreadsheet or someone's memory, and the case started late or never.
- What we did
- A phase can now open a case when a date in a table comes up: a policy expiry, a contract, a birthday. Pick the date, how many days before or after, or every year, and the case arrives with its record and contact, with an email to the contact ready to send.
- How it helps
- Each case comes in once per date, with the date as its due date and the contact linked. «Write to the contact» fills an email with the record's data, sent from your workspace's name by one click or on its own; replies reach whoever has the case.
- NEW
Every email to your contacts has a way out
- The problem
- An email that bounced looked sent, and the only way for a person to stop your emails was to mark them as spam.
- What we did
- Each email your business sends a contact now ends with a link to stop receiving them, and Gmail may show its own unsubscribe button. The contact page says why someone doesn't get emails, and an owner can turn them back on when the person asks. If an email bounces, the case shows “Didn't arrive” on the document, logs “Email not delivered” and rings the bell for whoever has it. If too many bounce, ioZen pauses emails to contacts and emails the owners, and the Inbox shows why if your plan includes it.
- How it helps
- Your emails keep reaching inboxes, and you know right away when one didn't, so you can send it on WhatsApp.
- NEW
Contacts sorted by last message
- The problem
- A contact's date only moved when the contact was created or edited, so the person who just wrote could be anywhere in the list.
- What we did
- The contacts list can now be sorted by last message, name (A-Z) or date created. Last message is the default: when someone writes on WhatsApp or in the web chat, they move to the top. Your choice stays after a reload.
- How it helps
- The team answers the person who wrote last first, from Contactos, while the Inbox stays one row per conversation.
- BETTER
Deleting a contact also deletes their conversations
- The problem
- When someone asked to have their data erased, their conversations stayed behind after the contact was gone.
- What we did
- Deleting a contact now also deletes their WhatsApp and email conversations, with the messages and files, next to their documents. The dialog says how many before anything happens, for one contact or many, and the space their files took goes back to your workspace.
- How it helps
- One delete erases the person's profile, documents and conversations, and you see what goes before you confirm.
- NEW
Documents: quotes designed by AI, filled from each case
- The problem
- After the intake, quotes and contracts were written by hand in a word processor, so the case left ioZen at its most valuable moment.
- What we did
- Each FlowApp now has Documents. Describe the document you need, for example a quote with the customer's details, what they asked for and the estimated price, and the AI designs it with your brand kit. You can ask for changes in your own words, and see where each piece of data goes or fill it with an example case. From any case, Generate makes the PDF with that case's data: names and numbers come from the case and your calculations, never from the AI. Every document waits in the new Outbox, next to the Inbox, where you review it, edit it, download it and mark it as sent. A document never changes once it's made: editing it makes a new version, and each PDF keeps its fingerprint. Document designs travel with your FlowApp when you copy it or share it as a template. A phase can also generate its documents when a case enters it; whoever moves the card can send the document right then by WhatsApp, inside the 24-hour window, or by email as a link from «Your business via ioZen» (replies reach your team), or leave it in the Outbox. Nobody receives a document without that click. «Send for signature» sends a one-person link (by WhatsApp, email, or to copy) that works for 7 days and one signature: the contact sees the document, ticks «I accept» and signs with their finger or mouse, with no account; the case keeps a signed copy with its record (who, when, what they accepted, the document's fingerprint). It is a simple electronic signature, and a completed signature uses 50 credits. Designing a document uses credits; generating one uses 10 credits and an email to the contact 0.4 (test and example cases are free). A document or a signature starts only when the full price is there: with less, the case shows one notice with both prices and the action stays closed, saying why.
- How it helps
- The document a case needs is one click away, with your brand and the right numbers, and waits for you to send it.
- NEW
The Intake Bot hands over the quote
- The problem
- The person finished the conversation and then waited for someone on the team to send the quote by hand.
- What we did
- A new document block sends the person a PDF made from one of your templates as soon as the conversation ends: in the web chat, in «Paso a paso» and on WhatsApp. Put it inside a branch and it only goes out when the conversation took that branch, so each path can get its own document, up to 5 per conversation. Turn on «Ask for a signature» and a «Sign» button shows under the PDF. The document is logged as sent in the case and the Outbox. Each PDF uses 10 credits. If the workspace doesn't have them, the person sees nothing, your owners and admins get a notification and the case says why.
- How it helps
- Your customer leaves the conversation with the quote in hand, and can sign it right there.
- NEW
Your contacts' email replies land in the Inbox
- The problem
- Replies to your emails went to a mailbox outside ioZen, away from the case.
- What we did
- When a contact replies to an email your business sent, the reply lands in the Inbox, next to their case, and you answer from there by email.
- How it helps
- WhatsApp and email conversations live in one shared inbox, next to the case.
- BETTER
Exports bring every question, branches included
- The problem
- Branch questions came unchecked, so an export looked like the bot had lost answers it had saved.
- What we did
- In Submissions › Export, the questions inside branches and repeating groups now come checked, like the rest. Checking or unchecking a branch does the same for every question in it.
- How it helps
- Click Export and the file has everything the bot asked.
- NEW
Attach files to case comments
- The problem
- A quote, a photo or a signed page had no place in the case: it lived in someone's email or chat.
- What we did
- A case comment can carry files now: up to 5 per comment, each up to your plan's file size limit. Your team downloads them from the case's activity through a private link that expires in minutes.
- How it helps
- The file stays with the case, where the whole team finds it.
- NEW
Attach files to a contact's notes
- The problem
- A document about a person, like an ID or a signed contract, had no place on their profile.
- What we did
- A note on a contact can carry files now, as a case comment does: up to 5 per note, each up to your plan's file size limit, downloaded through a private link that expires in minutes. A note can be just a file. Deleting the note or the contact deletes its files.
- How it helps
- What you keep about a person stays on their profile, with their notes.
- BETTER
Your first email takes one card, and “Messages” updates on its own
- The problem
- The first email asked for the same thing in three places, an empty subject failed with a generic error, and a reply only showed on the contact after a reload.
- What we did
- Your first email to a contact now shows one card: who signs, the rule in one line and one box, instead of a dialog and two separate steps. “Send” tells you what's missing (the subject, the message or the box) and takes you there. A contact's and a case's “Messages” show a new reply right away, marked “New”, with no reload.
- How it helps
- Writing to a contact is one step, and the conversation on the contact and the case stays current while you work.
- BETTER
An installed FlowApp's charge waits for your payment details, and English templates open the English sign-up
- The problem
- An installed charge could offer a way to pay that led nowhere, because the author's payment link never travels, and nothing said what was missing.
- What we did
- When you install a FlowApp that charges in the chat, its charge arrives with only the payment methods your workspace can already take: the link stays off until you paste your own in the block, and transfer until your bank details are in Settings › Payments. Zen tells you which charges still need setting up, with a link to Settings › Payments, and stops once they take payments. The install link of an English template now opens the sign-up in English.
- How it helps
- Your customers only see ways to pay that reach your account, and you know right away what to set up before the first charge.
- BETTER
«Pay later» sends the link, and amounts read the way your customer reads them
- The problem
- A customer who couldn't pay right away had no way back to the payment, and amounts looked foreign in some currencies.
- What we did
- When a customer chooses «Pay later», they get the link to a payment page with the same options, once: by email from your workspace's name, with replies reaching your team, or in the WhatsApp reply. With no email, the web chat shows the link with «Copy link». Amounts now follow the conversation's language and the currency's region: $1,500.00 MXN in Spanish, MX$1,500.00 in English, 1.500,00 € for euros.
- How it helps
- The customer keeps a link to pay when they can, and every amount reads naturally in the chat, the email, the case and the board. The email uses 0.4 credits; nothing is charged if it doesn't go out.
- NEW
Charge inside the Intake Bot
- The problem
- Payments happened outside ioZen, so the case never knew whether the customer paid.
- What we did
- A new «Cobro» block charges inside the conversation, on the web and on WhatsApp, with your payment link or a bank transfer. The case shows when the payer reports it, and your team marks it paid.
- How it helps
- Quote and take the deposit in the same conversation, and see who paid on each case.
- NEW
Ask for a signature in your Intake Bot
- The problem
- Authorizing a quote or accepting a consent happened outside the conversation, on paper or by email, and the case waited for it.
- What we did
- A new “Signature” question closes the conversation with your customer's OK. They sign with a finger or the mouse, or type their name, and you see the signature and its record in the case.
- How it helps
- The OK arrives with the answers, as a simple electronic signature: the image, who signed, when, what they accepted and a fingerprint of their answers. On WhatsApp the bot sends a link to sign on the web.
- NEW
Show your Intake Bot step by step
- The problem
- Some customers expect a form, not a conversation, and a business that wanted one had only the chat.
- What we did
- A new way to present an Intake Bot: one question per screen, like a form, with a progress bar and Back. Same questions and the same brand; pick it in the Design tab or ask Zen.
- How it helps
- Branching, AI follow-ups and saved progress keep working, one screen at a time, on the link and your site; WhatsApp stays a chat. The question counter, chat too, now counts only the person's path: a branch they skip stops counting.
- BETTER
WhatsApp replies show the message they answer
- The problem
- A reply to a specific message showed up alone, with no hint of what it answered.
- What we did
- When a contact replies on WhatsApp to a specific message, the Inbox shows that message above the reply, as WhatsApp does. Tap it to go to the original.
- How it helps
- Your team reads every reply in context.
- NEW
Write an email to a contact, with files
- The problem
- You could only answer an email a contact sent. To write first, or to send a quote, you left ioZen.
- What we did
- Start a new email to a contact from their case or their profile, not only reply. New emails and replies carry files (PDF, images, Office or text), up to 7 MB per email. Each email uses 0.4 credits, files included.
- How it helps
- The email and its files stay in the contact's thread, next to the case, and the reply comes back to the Inbox.
- BETTER
Zen is always on the right, with its button
- The problem
- Zen showed up on the left on a first visit and on the right after that.
- What we did
- Zen, ioZen's AI, now has one place on every visit: the panel on the right of your FlowApp. The first time it opens by itself because it has something to tell you; after that, the “Zen” button at the top opens and closes it.
- How it helps
- You always know where Zen is and how to open or close it.
- NEW
Zen builds phases, rules and tables, and checks they connect
- The problem
- Growing a FlowApp piece by piece meant visiting a different screen for each piece, and nothing told you when a rule pointed nowhere.
- What we did
- Ask Zen, ioZen's AI, for a new phase, a board, a rule that sends some cases to another phase, or a table, and it proposes all the pieces in one plan, connected to each other. Before proposing, it tells you which parts of your FlowApp it looked at. After you tap Build, it checks that everything is connected: which question each rule reads, where those cases land and what fills each table. If it finds something already broken, like a rule that sends cases to a phase you deleted, it tells you once and writes the fix in the box for you to send. These changes use no extra credits beyond the request.
- How it helps
- You say what you want, confirm one plan, and see that every piece is connected.
- NEW
Zen offers one next step when you come back
- The problem
- Coming back to a FlowApp, it was not clear what to do next.
- What we did
- When you come back to your FlowApp, Zen, ioZen's AI, looks at where it is and offers the one step that moves it most: publish your Intake Bot, get your first case, work the cases that are waiting, or add a rule. A short bar shows how far along you are. Never more than one thing per visit, and Not now keeps it quiet for a week. It uses no credits.
- How it helps
- One clear next step each visit, at your pace.
- NEW
Zen reads what it needs before it proposes, and points out what's broken
- The problem
- Zen planned from a summary of your FlowApp and could guess on long bots, and something broken stayed hidden until you built again.
- What we did
- Zen, ioZen's AI, now reads the parts of your FlowApp it needs before it proposes a change, like every question of a long Intake Bot, and tells you what it looked at. It never changes anything without your tap on Build, and if a step can't be done, the card shows what got done and what didn't. When you come back and something is broken, a dot on the Zen button tells you; tap Not now and it stays quiet for a week, twice and it stops. After you add a question, Shall we try it? opens the bot the way your customers see it.
- How it helps
- Plans built on what your FlowApp really has, and broken pieces you hear about once, on your terms.
- NEW
Undo what Zen built, and one clear step each visit
- The problem
- A change from Zen could only be reverted by hand, and its panel offered so many buttons that the next step got lost.
- What we did
- Tap Undo under what Zen, ioZen's AI, just built and your FlowApp goes back to how it was before that change, all at once. Zen never deletes your customers' data: if what it built already holds cases or records, or someone edited it afterwards, it tells you why and changes nothing. Zen's panel is simpler too: one highlighted step per visit, and the writing box shows an example built from your FlowApp. When your FlowApp is all caught up, the step is to send it to ioZen as a template: our team reviews it, removes your data and, if it fits, publishes it for other businesses.
- How it helps
- You try changes without fear and always know what to do next.
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
Right after an estimate, an agent block could open with a cheerful welcome, as if the conversation had just started.Agent blocks open with one short question, never a greeting
A quote could print the estimated premium twice under the same label, and the insured value without its currency.Documents the AI designs print each figure once, with its currency
A reply stayed on “Sending…” until you reloaded, and the conversation kept saying “Waiting” after you had answered.Email replies show “Delivered” on their own, and clear “Waiting”
See 1 more fix
After a large upload, some files ended as failed because the AI was busy for a moment.Large Knowledge uploads finish instead of failing