What shipped the week of Nov 9

Your FlowApp's Overview when you come back, and a polished first experience

When you come back to a FlowApp, its Overview shows the whole FlowApp first, nothing dimmed and no tour. Zen, ioZen's AI, now lives in a panel on the right that you open with the Zen button in the top bar; on a wide screen it opens by itself only when it has something new for you, and it remembers whether you like it open. The guided show still plays once, when you sign up or install a FlowApp. Trying your Intake Bot keeps the reply box in view however long the conversation gets. Sample cases open with their conversation, the bot's questions and the case's answers. A follow-up question in the middle of a conversation no longer says hello again.

A new Intake Bot arrives with its own board, and you see your board without leaving Zen

The problem

A bot added later landed on your first board and you had to build its board and route by hand.

What we did

When you add a second Intake Bot to a FlowApp, it now arrives with the board its cases move through, with phases written for them, and it routes there on its own. If its cases follow the same steps as a board you already have, it uses that one. It also speaks in the same tone as the bot you already have, and asks real questions. In the Overview, the button Zen gives you to open your board now opens it right beside the conversation, with each phase, its cases, and the full board one click away.

How it helps

Each bot's cases land where they belong from the first one, and you check your board without losing the conversation.

Formulas read the ad campaign without hidden fields

The problem

Sending the campaign to a CRM took one hidden field per ad parameter, which crowded the question list and the table.

What we did

A Calculation block can use {{utm_campaign}}, {{utm_source}}, {{gclid}} or {{fbclid}} straight from the ad that brought the person, so you can tell ad cases from web cases and send the campaign to your CRM without adding hidden fields to the Intake Bot, also from an action that runs mid-conversation.

How it helps

The Intake Bot keeps only its real questions, and the CRM still gets the source and campaign.

The ioZen badge leads to the FlowApp behind the bot

The problem

The badge always opened the iozen.ai home, so someone who liked the bot had to search for the FlowApp behind it.

What we did

When someone answers an Intake Bot installed from a FlowApp on iozen.ai, the «Powered by ioZen» badge and the «Create your own Intake Bot like this» card now open that FlowApp's page, in the bot's language, where they can install the same FlowApp. A bot that did not come from a published FlowApp keeps leading to the iozen.ai home.

How it helps

Whoever likes a bot lands on the FlowApp that makes it and installs it in one step.

Boards: one Filters button, steadier drag and drop, and «View as operator»

The problem

The board had five filters and many buttons in a row, dragging a case slowly made its landing spot blink, and owners couldn't see the app the way their team does.

What we did

Every board now opens with «All · Mine · Unassigned» first, then the search and a single «Filters» button that groups status, priority, assignee and tags (plus «Unattended» on plans with the Inbox) and shows how many are on. Active filters sit under the toolbar as chips you remove with one click. The bell fills in when you follow the board. Dragging a case is steadier: the spot it will land in follows the center of the card, without jumping back and forth, and the case lands exactly there. Owners and admins can also check what their team sees: «View as operator» in the user menu shows the member's menu and «My cases» with your own data, under a banner with «Exit». It is a view only: your role and permissions don't change.

How it helps

Find your cases in one tap, move them where you mean, and set up your team knowing what they will see.

A case and its chat go to the same person

The problem

A case and its chat were assigned separately, so one person could hold the case while someone else answered the chat.

What we did

Assigning a case now assigns its conversation too, and assigning a conversation assigns its open cases. It works the same when you assign by hand, when a distribution rule assigns and when Zen assigns, so whoever takes a case also answers that person's chat. Nothing someone else already holds moves, closed cases stay as they are, and every change shows in the case activity. It works on plans with the Inbox and it's on by default; owners and admins can turn it off in Settings › “Case distribution”.

How it helps

Each customer talks to one person on your team, from the case to the chat.

A FlowApp's page on iozen.ai shows the whole FlowApp before you install it

The problem

A FlowApp's page described it, but you couldn't see what each piece does until you installed it.

What we did

Each FlowApp page on iozen.ai now shows what you get before you install it: a row for each Intake Bot with its questions, its calculation and its advisor, and a row for each Process Board with the bot that feeds it, its phases and its rules. A sample case shows the estimate the FlowApp's own calculation gives for its answers. The page also tells you which plan installs it and what each plan adds. Every FlowApp page has a short address in its language, like iozen.ai/flowapps/auto-insurance-quote, and the old addresses take you there.

How it helps

You know what you get, and which plan you need, before you install.

Your CRM gets the ad campaign of each case

The problem

The campaign stayed in Attribution, where no action could read it, and a bot in a site's own iframe recorded no campaign at all.

What we did

A hidden field named utm_campaign, utm_source, gclid or fbclid fills itself from the ad link that brought the person, so an action can send the campaign to your CRM. A site that opens the bot in its own iframe also records that campaign in Attribution, once it passes the ad params on the iframe link.

How it helps

Sales sees in the CRM which ad each case came from.

Install a FlowApp when you already have an account

The problem

Someone with an account who clicked "Install this FlowApp" landed on their workspace and the FlowApp was never installed.

What we did

"Install this FlowApp" on iozen.ai now works when you are already signed in: it installs in your workspace and opens it, and Zen tells you what it installed. If your plan has no room, nothing is installed and Zen tells you which plan does. An advisor your plan does not include arrives asleep: the conversation goes on without it, the map and the editor mark it, and it wakes up on its own with Business. Trying your Intake Bot from Zen now counts as a test, never as a real case.

How it helps

Any FlowApp on iozen.ai is one click away, for new and existing accounts.

The ioZen manual, at iozen.ai/docs

The problem

There was no single place on iozen.ai to learn ioZen step by step, in your language.

What we did

ioZen now has a manual on iozen.ai/docs, in Spanish and English: 26 guides that take you step by step, from what ioZen is and creating your first FlowApp to questions, agent blocks and estimates, cases and your team, tables and contacts, WhatsApp, where each case comes from (in beta), webhooks and the API, plans and credits, and security. A search box finds any guide, and every page is also available as Markdown, ready to paste into your AI assistant. Eight of the Spanish guides come with a video.

How it helps

You find how to do something in ioZen in seconds, in your language, with the screens you'll see.

My cases: your team works its cases from the phone

The problem

Team members who answer cases saw the builder's app: menus they don't use, and no list of their own cases, least of all on a phone.

What we did

Members of your team who don't build FlowApps now open ioZen on «My cases»: the cases newly assigned to them first, then each board they work on, phase by phase, across every FlowApp. A case moves to the next phase from its header, and on plans with the Inbox it opens on its chat on a phone, so they answer without hunting for it on a board. Members who can see every case also get «Unassigned», and «Take» makes a case theirs. A «Reports» tab shows their active cases, the ones waiting for a reply and the overdue ones, per board. Their menu is short: their cases, the boards they work on and Contacts, plus the Inbox where the plan has it. Owners and admins keep the full app, and nobody loses access to anything.

How it helps

Each person sees what is theirs first and works it in two taps from the phone.

Bots the AI writes in Spanish use «tú» by default

The problem

Bots the AI wrote in Spanish could sound stiff, with «usted» and phrases nobody says in a chat.

What we did

When ioZen's AI writes an Intake Bot in Spanish, it now addresses people as «tú» by default, in a warm, natural tone, with real questions that open with ¿. If the bot's tone is formal, it uses «usted», naturally. Either way it avoids stiff phrases like «Sírvase» or «Favor de».

How it helps

Your customers chat with a bot that sounds like your business, not like a form.

Zen shows you your first FlowApp as it builds it

The problem

Your first FlowApp was built behind a wait screen, and you met it all at once afterwards.

What we did

When you pick what to solve in onboarding, you go straight into your FlowApp and Zen, ioZen's AI, tells you what it read on your site while it writes the questions and builds the Process Board. Then, one tap per step, you see a sample customer write to your Intake Bot, their case land on the board with its score and why, the contact it created, and how the case would move through the phases, as a preview that changes nothing. If Zen sees a table that fits, it offers it and nothing is built until you tap Build. You can skip to your FlowApp at any step. At the end, Zen shows you examples of changes you can ask for, and three things your FlowApp can already do, each one a tap from the screen where you set it up.

How it helps

You see each piece of your FlowApp as it appears, at your own pace, and know what to do next.

Ask Zen for a change in your own words

The problem

Growing a FlowApp meant knowing which screen does what, and what people needed but ioZen didn't do never reached the team.

What we did

Below the conversation with Zen, ioZen's AI, there is now a box to ask for changes to your FlowApp in your own words, with examples made from your own FlowApp to start from. Zen shows what it would do and why before touching anything, and nothing changes until you tap Build. It can add an Intake Bot, if your plan has room, with its own Process Board and the route that sends each case there, add a question to a bot, rename a phase, or apply one of its suggestions. Adding a bot uses about 60 credits, shown before you build. When Zen can't do something yet, it tells you where in ioZen you can do it yourself, step by step, or that ioZen doesn't do it yet, and offers to tell the ioZen team. Your words reach the team only if you say yes.

How it helps

You say what you want and confirm it; what ioZen can't do yet goes to the roadmap when you want it to.

Zen suggests improvements, and you can share your FlowApp as a template

The problem

Ideas to improve a FlowApp were easy to miss, and a FlowApp that worked well had no way to help other businesses.

What we did

Zen, ioZen's AI, now suggests changes to your FlowApp right in the conversation, one at a time: what to change, why, and the piece it touches lit up. Tap Build to apply it, or say "Not now" and it waits in Suggestions, below your FlowApp, for your whole team. Once your FlowApp has a published Intake Bot and its board, Zen also offers to share it as a template: the ioZen team reviews it, removes your data and that of the people who wrote to you, and publishes it if it fits.

How it helps

You improve your FlowApp one tap at a time, and what works for you can work for others.