Changelog · Aug 24 – 30 2026 · 9 changes
What shipped the week of Aug 24
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 a customer stops replying on WhatsApp, your Intake Bot can write to them with an approved template, and you can too from the Inbox after the 24 hours. GoHighLevel connects like any other CRM. And if a webhook fails, you see every attempt and resend it with one click.
Jay
Integrations · GoHighLevelsample
What your Intake Bot sends
Contactsyes
Opportunitiesyes
Tags and notesyes
Location idnot needed
Newest first
Change by change
- 4 NEW
- 2 BETTER
- 3 FIXED
- BETTER
Admins can brand and scope any Composio integration
- The problem
- Adding a Composio toolkit needed a code change, even when Composio already covered it.
- What we did
- Admin Integrations now stores display name, logo, bilingual descriptions, auth scheme, and scoping keys on the toolkit setting. A new toolkit no longer needs a code change when Composio already covers it.
- How it helps
- Admins set a toolkit's display name, logo, descriptions, auth scheme and scoping keys in its setting, with no code change.
- NEW
GoHighLevel connects like any other CRM
- The problem
- You couldn't connect GoHighLevel from Integrations.
- What we did
- Workspaces can connect GoHighLevel from Integrations and push contacts, opportunities, tags, and notes from Intake Bot action blocks. The connected sub-account is stored on connect so builders do not paste a location id.
- How it helps
- You connect GoHighLevel from Integrations and push contacts, opportunities, tags and notes from an Intake Bot, with no location id to paste.
- NEW
WhatsApp intakes skip the mapped phone question
- The problem
- A WhatsApp conversation asked for the phone number even though the sender's number was already known.
- What we did
- When an Intake Bot maps a phone field to the contact, a WhatsApp conversation fills that field from the sender's number and does not ask it. The same published bot still asks for the number on the web chat. The number lands on the contact, the record, and the Process Board card through the existing submission pipeline.
- How it helps
- WhatsApp conversations fill the mapped phone field from the sender's number without asking, and the web chat still asks for it.
- BETTER
Stripe Checkout for custom plans
- The problem
- Custom plans couldn't collect a negotiated monthly USD price through Stripe Checkout.
- What we did
- Custom plans can now collect a negotiated monthly USD price through Stripe Checkout. Workspace owners complete payment setup themselves and can update their card or view invoices without changing or canceling the negotiated plan. Manual invoice and bank-transfer billing remain available.
- How it helps
- Workspace owners set up payment themselves and can update their card or view invoices without touching the negotiated plan.
- NEW
Webhook delivery logs, redelivery, and per-bot filters
- The problem
- Webhooks kept no log of delivery attempts, and an endpoint couldn't follow only specific Intake Bots.
- What we did
- Webhooks now keep a per-attempt delivery log (status, HTTP code, duration) visible in the dashboard and the API, and failed deliveries can be redelivered with one click. Endpoints can subscribe to specific Intake Bots instead of the whole workspace. When an endpoint fails 10 times in a row it is paused automatically and workspace admins get an email with a resume link. The v1 API adds PATCH and test endpoints for webhooks, date filters when listing submissions, a Retry-After header on rate limits, and every event now carries an api_version field.
- How it helps
- You see every delivery attempt, redeliver failed ones with one click, and choose which Intake Bots an endpoint follows.
- NEW
WhatsApp templates, inbox send, and abandoned-intake follow-up
- The problem
- You couldn't send a template from Team Inbox after the 24-hour window closed, and a WhatsApp intake that went quiet got no follow-up.
- What we did
- Business and Enterprise workspaces can install curated utility templates or write their own, wait for Meta approval, then send them from Team Inbox after the 24-hour window closes. Intake Bots can optionally fire one of those templates when a WhatsApp intake goes quiet. Meta starts billing service (free-form) messages on 2026-10-01 at each market's utility rate, so a utility template outside the window will cost the same as a reply inside it. Marketing templates stay about 3x that rate.
- How it helps
- You send approved WhatsApp templates from Team Inbox after the 24-hour window, and an Intake Bot can send one when a WhatsApp intake goes quiet.
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
Browser auto-translation no longer breaks the app with an error screen
Google Calendar appointment links embed in CTA modals
Location questions answered on WhatsApp now save the coordinates