Changelog · Aug 31 – Sep 6 2026 · 13 changes
What shipped the week of Aug 31
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
WhatsApp now lives in one place: each contact has one thread, and you read and reply from the Inbox, the case or the contact's profile. You can write first with an approved template and send campaigns to a segment of your contacts. And cases that come from a Click-to-WhatsApp ad now keep which ad they came from.
Jay
Process Board · phasesample
Meeting scheduled
Outcome it recordsmeeting scheduled
Whenthe first time
If the case enters againnot again
Newest first
Change by change
- 9 NEW
- 2 BETTER
- 2 FIXED
- NEW
Process Board phases can record conversion outcomes
- The problem
- A Process Board phase couldn't record a conversion outcome when a case entered it.
- What we did
- A Process Board phase can record one outcome the first time a case enters it: purchase, meeting scheduled, or a named custom event, with optional value and currency. ioZen writes one first-party lifecycle event. Moving the same case into that phase again does not write another. Network sends follow configured platform credentials and do not depend on Intake Bot On Payment or On Meeting Booked flags. If no submission is found, only the first-party event is recorded. Test cards send to Meta Test Events only when a test sink is ready.
- How it helps
- A phase records a purchase, a scheduled meeting or a custom event the first time a case enters it, and never writes it twice for the same case.
- NEW
Import a contact list into a WhatsApp campaign
- The problem
- You couldn't import a contact list from a new WhatsApp campaign.
- What we did
- New campaign can open the Contact Center import wizard. The imported rows are tagged and saved as a phone-ready segment, then selected as the campaign audience. Campaigns target contacts only: saved segment, filters, or a simple search.
- How it helps
- You import a contact list from New campaign, and it is tagged, saved as a phone-ready segment and selected as the audience.
- NEW
Google Data Manager conversion delivery
- The problem
- Google Ads conversions weren't delivered through Data Manager.
- What we did
- Google Ads conversion delivery now uses Data Manager for configured connections. ioZen sends one click ID plus available hashed customer data, validates setup without ingesting a test conversion, and keeps eligible legacy Ads connections available without duplicate Google delivery.
- How it helps
- Your configured connections send Google Ads conversions through Data Manager, and setup is validated without ingesting a test conversion.
- NEW
Click-to-WhatsApp ads now attribute in ioZen
- The problem
- Cases from Click-to-WhatsApp ads didn't keep the referral and click ID, so source analytics couldn't group them.
- What we did
- WhatsApp conversations that start from a Meta Click-to-WhatsApp ad now keep the referral and click ID. The Intake Bot submission is stamped so source analytics can group those cases. Organic WhatsApp stays unattributed. Optionally, each number can send server-side Meta business-messaging conversions (LeadSubmitted, Purchase) to the WABA-linked dataset using the raw click ID and an optional Test Events code. Meta attributes those events for 7 days from the click. This is beta until a live Test Events check is completed.
- How it helps
- Click-to-WhatsApp conversations keep the referral and click ID, source analytics can group those cases, and each number can optionally send Meta conversions (beta).
- NEW
Tracked links for non-Meta WhatsApp ads
- The problem
- Ads that don't come from Meta had no tracked link into WhatsApp.
- What we did
- Each WhatsApp number can now publish first-party /l/[slug] links. A click stores UTMs and click IDs, then opens WhatsApp with a short reference marker that is removed before the conversation is stored. A surviving token is a deterministic match and can reach ad networks. A 10-minute unique fallback is a first-party estimate only. Click-to-WhatsApp referrals still take precedence. Phone is not a LinkedIn match key; capture email in the Intake Bot or keep li_fat_id.
- How it helps
- Each WhatsApp number can publish its own links that store UTMs and click IDs, then open WhatsApp with the reference marker removed before the conversation is saved.
- NEW
WhatsApp campaigns from contact segments and filters
- The problem
- Outreach campaigns couldn't target a saved contact segment or contact filters.
- What we did
- Outreach campaigns can target a saved contact segment or contact filters. Template variables resolve per contact from contact or custom fields, with a fallback. Create reviews the eligible audience before send.
- How it helps
- You aim a campaign at a saved segment or filters, fill template variables per contact with a fallback, and review the eligible audience before sending.
- NEW
Start WhatsApp conversations with approved templates
- The problem
- You couldn't start a WhatsApp thread from the inbox or a contact card with a number that had never written.
- What we did
- Inbox and contact cards can now open a WhatsApp thread with a number that has never written, using an approved template. Marketing sends require a recorded opt-in. Business plans also get Outreach campaigns on Kapso Broadcasts, with a watchman that stops the send if number health drops.
- How it helps
- You open a WhatsApp thread with a new number using an approved template, and marketing sends require a recorded opt-in.
- BETTER
One WhatsApp thread per contact
- The problem
- WhatsApp history split into a new thread each day.
- What we did
- WhatsApp inbox, case, and contact threads stay on one conversation after the 24-hour window closes or a template is sent. History no longer splits into a new thread each day.
- How it helps
- Your WhatsApp threads in the inbox, case and contact stay on one conversation, even after the 24-hour window closes or a template is sent.
- BETTER
Payment failure warnings and billing history
- The problem
- You only heard about a failed subscription payment after the plan was canceled.
- What we did
- Workspace owners now get an email as soon as a subscription payment fails, with the retry date and a link to update the card, instead of only hearing about it after the plan is canceled. Billing settings shows a notice explaining an automatic downgrade and a history of payment issues and plan changes. Data and purchased credits are unaffected by a downgrade.
- How it helps
- You get an email as soon as a payment fails, with the retry date and a link to update the card, and Billing shows the history.
- NEW
WhatsApp threads on case cards
- The problem
- A case card didn't list the WhatsApp and Intake Bot conversations linked to it.
- What we did
- A case card now lists WhatsApp and Intake Bot conversations linked to its contacts or submissions. Open a thread from the Messages tab to read history and reply with the same composer, session window, and credit rules as the Team Inbox.
- How it helps
- You read a case's WhatsApp and Intake Bot conversations and reply from its Messages tab, with the same session window and credit rules as the Team Inbox.
- NEW
WhatsApp threads on contact profiles
- The problem
- A contact profile didn't open the WhatsApp threads linked to that contact.
- What we did
- A contact profile now opens linked WhatsApp threads in a Messages tab next to Activity. One thread opens inline; several show a list first. Reply, return to bot, and session rules match the Team Inbox.
- How it helps
- You open a contact's WhatsApp threads from its profile and reply with the same rules as the Team Inbox.
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
Intake Bot limit now counts drafts
Safer plan upgrades and downgrades