Changelog · Sep 21 – 27 2026 · 7 changes
What shipped the week of Sep 21
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
An assistant suggests where each case should go from its answers, and you accept it or change it. On the Process Board you see a dot on cases with an unread message, and you can filter to the ones still waiting. Intake Bot answers are saved on your contact's fields, and you use them in your WhatsApp templates.

Jay
Ad networks
Newest first
Change by change
- 5 NEW
- 1 BETTER
- 1 FIXED
- NEW
Workspace ad network connections
- The problem
- You couldn't save ad network credentials once for the whole workspace.
- What we did
- Save Meta, Google, TikTok, LinkedIn, and webhook credentials once per workspace. Intake Bots and Process Boards can opt in. Secrets are encrypted. Bots that do not link keep sending from their own credentials.
- How it helps
- You save Meta, Google, TikTok, LinkedIn and webhook credentials once, encrypted, and choose which Intake Bots and Process Boards use them.
- NEW
Assistant routing for Intake Bots
- The problem
- Routing an Intake Bot started with manual rules.
- What we did
- Routing an Intake Bot now starts with an assistant. It suggests where each case should go from the answers, you accept or edit that suggestion, and you can ask for a change. Manual rules stay available. Suggestions, changes, and live routing use credits.
- How it helps
- An assistant suggests where each case should go from the answers, and you accept it, edit it or ask for a change.
- BETTER
Field conversions are not a second lead
- The problem
- Meta website and TikTok received a field conversion as another lead.
- What we did
- Meta website and TikTok no longer receive a field conversion as another lead. Meta business messaging sends QualifiedLead for that field. Completion leads are unchanged.
- How it helps
- Meta website and TikTok no longer count a field conversion as a second lead, and Meta business messaging gets QualifiedLead for it.
- NEW
Unattended cases on Process Boards
- The problem
- A Process Board card didn't show when its inbox conversation had an unread message.
- What we did
- Process Board cards show a dot when a linked inbox conversation has an unread inbound message. A board filter lists only unattended cases.
- How it helps
- You see a dot on cards with an unread inbound message and can filter the board to only unattended cases.
- NEW
Map intake bot answers to contact custom fields
- The problem
- Custom fields from an Intake Bot couldn't be mapped to your workspace contact fields.
- What we did
- When contact creation is enabled on an intake bot, custom bot fields can be mapped to workspace contact fields (and created from the bot if they do not exist yet). Values are saved on the contact and available in WhatsApp templates as {{custom_key}}.
- How it helps
- Answers are saved on the contact's custom fields, and you can use them in WhatsApp templates as {{custom_key}}.
- NEW
Execute an Intake Bot from Inbox
- The problem
- You couldn't start an Intake Bot from an Inbox thread.
- What we did
- The Inbox thread control can start a published Intake Bot on an open WhatsApp session. Retry or return still resume the in-flight intake. Starting a different bot abandons the current one.
- How it helps
- You start a published Intake Bot from the Inbox thread on an open WhatsApp session.
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
Older Intake Bot looks save again