Changelog · Oct 26 – Nov 1 · 12 changes
What shipped this week
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
If you start today, you get 14 days of Business with 1,000 credits and no card, and your first Intake Bot comes from your own form, with your brand and your site's voice. When a customer is left waiting for a reply, the assigned person gets an alert. And if your team writes code, it now reads cases, contacts and records from the API and gets a webhook when a case changes phase or owner. Installing a FlowApp from iozen.ai now takes one step: you land on its board with sample cases already scored and in their phases.
Jay
Billing · new workspacesample
Business trial
Days left14
Credits1,000
If you stay on Freenothing is deleted
Cardnot needed
Newest first
Change by change
- 6 NEW
- 6 BETTER
- 0 FIXED
- BETTER
An installed FlowApp starts with sample cases on its board
- The problem
- A FlowApp installed from iozen.ai opened on an empty board, so you could not see how cases move until a real one arrived.
- What we did
- When you sign up from a FlowApp on iozen.ai, its Process Board opens with the sample cases from that FlowApp's page, scored and placed in their phases. They are marked as samples, count toward nothing, and one click deletes them.
- How it helps
- You see scoring, priorities and phases at work from the first minute, then delete the samples when real cases start.
- BETTER
Installing a FlowApp from iozen.ai is one step
- The problem
- Signing up from a FlowApp page asked for your website and your problem first, answers the install then ignored.
- What we did
- "Install this FlowApp" opens a signup that shows the FlowApp you are installing, with its board and sample cases in miniature, and asks only for your account. Confirm your email and you land on that FlowApp with its sample cases.
- How it helps
- You see what you are installing and get to it with one form.
- NEW
Combine segments, filters and contacts in one campaign
- The problem
- A campaign audience came from one source, a segment, filters or a contact list.
- What we did
- Campaigns can combine saved segments, filters and specific contacts, and each contact is counted once. The wizard has a side menu showing what each step still needs.
- How it helps
- You mix segments, filters and specific contacts in one campaign, and nobody is counted twice.
- BETTER
WhatsApp campaigns send in batches
- The problem
- Campaigns didn't pause between batches to check quality. A reply like cancel or exit could unsubscribe a contact.
- What we did
- Campaigns go out in batches of 200 every 30 minutes. Before each batch, ioZen checks the quality of your number and of the message, and stops the campaign if either drops or Meta pauses the template. The campaign page shows which batch is next and when. Replies like cancel or exit no longer unsubscribe a contact, so they can answer an Intake Bot freely. Only the Stop promotions button in WhatsApp unsubscribes.
- How it helps
- Your campaign stops itself if the quality of your number or message drops, and contacts can answer an Intake Bot without unsubscribing by accident.
- NEW
Cases in the API include tags, contacts, and records
- The problem
- The case data in the API left out the description, the tags and the linked contacts and records.
- What we did
- Case pages and case webhooks now include the description, tags, comment count, and linked contacts and records. A key with read:cases sees the link ids. Contact details need read:contacts, and record values need read:records. Case webhooks always include both. updated_after also matches tag changes and edits to a linked record or contact. Contact phone is null when WhatsApp hides the number. Adding a tag does not send a webhook: tag the case before you move it, or read the tag from the API.
- How it helps
- One read of a case gives you its description, tags, and linked contacts and records, within the scopes your key has.
- NEW
Webhooks for case phase changes and assignments
- The problem
- Your other systems got no signed notice when a case moved to another phase or got a new owner.
- What we did
- Outbound webhooks now include card.phase_changed and card.assigned: one signed delivery each time a case moves to another phase or its owners change, manually or by an assignment rule, with the case, the actor and the exact time. Intake Bot filters apply through the case's origin bot. contact.created now fires for every new contact, including WhatsApp conversations, inbox, marketing opt-in, API sends and manual creation.
- How it helps
- Your other tools get a signed notice each time a case changes phase or owner, with who did it and when.
- NEW
Read Process Boards, contacts, and records from the API
- The problem
- The API didn't let you read your Process Boards, contacts or records.
- What we did
- API keys can list Process Boards and page their cases, read contacts, and read Record Types and records. Each resource stays behind its own scope: read:cases, read:contacts, or read:records.
- How it helps
- You read your boards, cases, contacts and records from your own code, and each key sees only what its scope allows.
- BETTER
Submission export includes contact and ad click IDs
- The problem
- A submission in your export didn't say which contact it came from or which ad click brought it.
- What we did
- Submission export can include test submissions. That option is off by default. New columns add contact ID, contact phone, ad click IDs (gclid, gbraid, wbraid, fbclid, ctwa_clid), Google campaign ID, and Google ad source. Click ID columns need a plan with marketing attribution. Termination reason is now Early end outcome. The API returns the contact and those click IDs on each submission.
- How it helps
- Your export and the API show which contact sent each submission and, with marketing attribution, the ad click behind it.
- NEW
Alerts when a customer waits for a reply
- The problem
- A customer could finish the bot and wait for a reply while nobody was told.
- What we did
- When a customer finishes the bot and nobody replies, the assigned person gets a bell and an email after the minutes you set. If they are away, or nobody is assigned, admins are alerted. A second alert can go to the owners and admins you pick. The clock runs only during the hours you set. Turn it on in Settings, Response time. It comes with Inbox, on Business and Enterprise, and stays off until an admin turns it on. The email goes out right away.
- How it helps
- The assigned person, or an admin, gets an alert when a customer is waiting, counted only during the hours you set.
- NEW
New workspaces start with 14 days of Business
- The problem
- A new workspace started on Free, without Agent Blocks, knowledge, landing pages or your own branding.
- What we did
- Every new workspace starts on a 14-day Business trial with 1,000 credits, no card needed: Agent Blocks, knowledge, landing pages and your own branding from day one. The WhatsApp line comes with Business itself. Billing shows the days left. Pay before it ends to keep Business, or stay on Free: nothing is deleted. What Free doesn't include is paused, and comes back when you upgrade.
- How it helps
- You try Business for 14 days with 1,000 credits and no card, and nothing is deleted if you stay on Free.
- BETTER
Your first Intake Bot starts from your own form
- The problem
- Your site already had a form with your questions, but your first Intake Bot didn't start from it.
- What we did
- When you sign up with your website, ioZen now reads the form on your site and builds your first Intake Bot from it: the same information, in the words your customers already know, with fewer questions and the right types for emails, phone numbers and dates. Your website, description and location also fill in your organization profile, without replacing anything you already entered. The problem you picked at signup now guides which pages of your site we read.
- How it helps
- You start with an Intake Bot built from your own form, in your customers' words and with fewer questions.
- BETTER
Your first Intake Bot looks and sounds like your business
- The problem
- Your first Intake Bot didn't carry your mark, your color or the way your site writes.
- What we did
- The first Intake Bot now wears your site's mark as its avatar and your theme color when your site has one, and speaks in the voice your site writes in. It asks what the customer needs first and leaves name and contact for the end. While it builds, you see what we read on your site. The sample run now plays the whole conversation, from the welcome to the farewell, and the case lands with a one-line summary: what they want, the amount and when.
- How it helps
- Your first Intake Bot already looks and sounds like your business, and each case arrives with a one-line summary.
All weeks
- Oct 26 – Nov 1 2026Combine segments, filters and contacts in one campaign12 changes
- Oct 19 – 25 2026Your first FlowApp in about a minute28 changes
- Oct 12 – 18 2026Serve Intake Bots from your own domain16 changes
- Oct 5 – 11 2026Create a contact from a case card16 changes
- Sep 28 – Oct 4 2026Calculation blocks12 changes
- Sep 21 – 27 2026Workspace ad network connections7 changes
- Sep 14 – 20 2026Action destination wizard for Intake Bot sends27 changes
- Sep 7 – 13 2026Brand Kit looks and website match7 changes
- Aug 31 – Sep 6 2026Process Board phases can record conversion outcomes13 changes
- Aug 24 – 30 2026GoHighLevel connects like any other CRM9 changes
- Aug 17 – 23 2026Conversion delivery failures and Google posting are now visible9 changes
- Aug 10 – 16 2026Hidden number fields can total a score group12 changes
- Aug 3 – 9 2026Team Inbox for WhatsApp conversations4 changes
- Jul 27 – Aug 2 2026AI-generated choice options keep their full labels2 changes
- Jul 20 – 26 2026Run Intake Bots on WhatsApp1 change
- Jul 6 – 12 2026Assign cases to team members2 changes
- Jun 29 – Jul 5 2026Submission analytics and AI insights5 changes
- Jun 22 – 28 2026End an intake early with a content block3 changes
- Jun 15 – 21 2026Copy FlowApp across workspaces3 changes
- Jun 8 – 14 2026Agent Block — Collect Mode1 change
- Jun 1 – 7 2026Bulk AI question generation6 changes
- May 25 – 31 2026Verify Meta conversions from ioZen's test view2 changes
- May 18 – 24 2026AI credits now scale with actual AI work1 change
- May 11 – 17 2026Intake Bot generation recovery and AI content fallbacks2 changes
- May 4 – 10 2026Ludicrous voice pack: all 9 Magic Moments, AI-chosen intensity5 changes
- Apr 27 – May 3 2026AI Document Extraction: Upload Once, Answer Never5 changes
- Apr 20 – 26 2026Customize your Intake Bot share URL20 changes
- Apr 13 – 19 2026Voice Input on Every Field Type1 change
- Apr 6 – 12 2026Resume Unfinished Intake Bot Submissions5 changes
- Mar 30 – Apr 5 2026AI Generation & Intelligence Prompt Improvements6 changes
- Mar 23 – 29 2026Geolocation Field Type & Growth-Framed Onboarding3 changes
- Mar 16 – 22 2026Smart IntakeBot Create4 changes
- Mar 9 – 15 2026AI-Generated Content Blocks6 changes
- Mar 2 – 8 2026Hidden Fields & Data Passing8 changes
- Feb 23 – Mar 1 2026Contact Import Wizard7 changes
- Feb 16 – 22 2026Stripe Promotion Codes2 changes
- Feb 9 – 15 2026Mobile Access Gate12 changes
- Feb 2 – 8 2026Real-Time Collaboration6 changes