Updates from our Chatwoot fazer.ai editions

Includes changes from Chatwoot fazer.ai v4.18.0-fazer-ai.128.

✨ What's new

• Receive email through Resend. If your installation already sends email through Resend, your administrator can now enable customer replies to reach conversations in email inboxes without their own IMAP connection, another email provider, or your own mail server. Resend retries do not create duplicate conversations.

🐛 Fixes

• Consistent update times. Webhooks and real-time events now report update times that exactly match the saved values. Integrations comparing these times no longer see false differences caused by extra precision that could lead them to discard or reprocess events.

Includes changes from Chatwoot fazer.ai v4.18.0-fazer-ai.127.

✨ What's new

• Article sorting in the Help Center. In the Articles tab, you can sort by last update (the default), creation date, title or views in either direction, with your choice saved for you; within a category, the menu stays hidden to preserve its manual order.
• New webhook address for Z-API. If the current address is exposed, administrators can generate a replacement in the Configuration tab, and the old address keeps working until Z-API confirms the new one so a failed registration does not interrupt incoming messages.

⚡ Improvements

• Pairing after switching WhatsApp providers. Switching an inbox to Baileys, Z-API, WhatsApp (native) or uazapi opens QR code pairing immediately, and disconnected inboxes show a notice in their configuration tabs.
• Reopened conversations return to the team. A new option per inbox sends resolved or snoozed conversations to “Unassigned” when the customer reopens them and the assignee no longer belongs to the conversation’s team.
• Push notifications for internal chat. Mentions and direct messages now have push notifications enabled by default, including for existing accounts, so you can notice them beyond the notification bell.
• Update dates in webhooks. Bot and account webhooks include contact and inbox update dates so integrations that keep copies of these records can put events in order.

🐛 Fixes

• Voice messages play on Android. Voice messages recorded in the panel for WhatsApp (native) inboxes now play on Android without an audio file error.
• Conversation lists stay consistent while scrolling. Conversations with the same activity timestamp no longer appear twice or disappear between pages.
• Failed bot replies reach the team. When a bot exhausts its reply attempts, the conversation moves to “Unassigned” and becomes eligible for automatic assignment so the team can take over.
• Webhook tokens stay hidden in logs. Z-API and uazapi webhook address tokens no longer appear in plain text in application logs or error reports.
• Contacts are created immediately in disconnected WhatsApp inboxes. In disconnected WhatsApp (native) inboxes, contacts are now created immediately with the number exactly as entered, without the error that previously appeared after about 15 seconds.

Includes changes from Chatwoot fazer.ai v4.18.0-fazer-ai.126.

🔒 Security

• WhatsApp verifies incoming messages. Each incoming call is now checked to come from the inbox’s provider before it becomes a message, with a temporary exception for manually configured WhatsApp Cloud inboxes described below. Updating is recommended; this version’s security advisory provides the details.
  • Baileys, WhatsApp (native) and Uazapi. No action is needed, messages keep arriving.
  • Z-API. In most cases, no action is needed: about 10 minutes after the update, each inbox automatically switches to its own receiving address without losing messages during the change. If your Z-API instance’s webhooks point somewhere other than Chatwoot for a custom integration, the inbox stays as it is; reconnect it to migrate.
  • WhatsApp Cloud connected through Meta’s guided setup. No action is needed for inboxes connected using Facebook login.
  • Manually configured WhatsApp Cloud. New inboxes require the Meta App Secret, and Chatwoot checks that it belongs to the same app as the token you paste. Existing inboxes show a notice and a field to add the secret in the Configuration tab.
  • Transition for existing manual inboxes. Events continue to be accepted without a signature until you add the secret during this transition period, but a future version will stop accepting them. Add the secret now to avoid interruptions; find it in your app’s dashboard at developers.facebook.com, under App settings, Basic, “App secret”.
  • End the transition early on your own installation. Set WHATSAPP_ACCEPT_UNSIGNED_WEBHOOKS=false only after adding the secret to every manually configured inbox. Otherwise, inboxes without the secret stop receiving events.

✨ What's new

• Open the conversation in fazer.ai agents from the contact panel. Agents and administrators see a robot button beside the call and edit buttons when the inbox uses fazer.ai agents as its bot. It opens the same conversation in a new tab, so you can check executions, logs and settings without searching for it.

🐛 Fixes

• Agent reports load over long periods. In accounts with many messages, the “Handled” metric introduced in the previous version could be slow or fail to load for ranges of a few months, and now loads quickly. On self-hosted installations with millions of messages, the update creates a database index, so the first startup after updating may take longer.

Includes changes from Chatwoot fazer.ai v4.18.0-fazer-ai.125.

✨ What's new

• Reports show who actually handles conversations. The new “Handled” metric in agent, inbox and team reports counts conversations where an agent sends at least one public message to the customer during the selected period, crediting the sender regardless of assignment and excluding private notes, reactions, bots, automations and campaigns. To distinguish assignments from replies, “Conversations” becomes “Assigned” in agent and team reports and “Opened” in inbox reports, while each agent’s page shows a daily chart of handled conversations with clickable bars to view them.

🐛 Fixes

• Conversation lists load even after an agent is deleted. Conversations assigned to a deleted user appear without an assignee, instead of leaving the entire list blank.
• Blocked WhatsApp contacts stay blocked across more interactions. Their messages no longer open conversations or reach the bot in Baileys and Z-API inboxes, history imports exclude their messages in Baileys and WhatsApp (native), and their reactions no longer appear in WhatsApp (native) and Uazapi inboxes. Replies agents send from the connected phone continue to appear in the conversation.
• Changing your profile email keeps you signed in. When the new address requires confirmation, the screen explains that a confirmation link has been sent there and that your current email remains active until you click it. The email field continues to show your active address.
• The website widget stops showing “typing…” indefinitely. If the bot finishes without replying, the indicator disappears 30 seconds after the visitor’s last message and stays cleared when the page reloads. The bot continues to respond to the visitor’s next message.

Includes changes from Chatwoot fazer.ai v4.18.0-fazer-ai.124.

✨ What's new

• WhatsApp (native) available to everyone. The channel is now available in every installation and account without extra setup, still in beta, with pairing by QR code or a code on your phone. It runs within your installation, with no third-party service or extra service to deploy.
• Important for self-hosted installations. If you already run a separate connector, set WHATSAPP_CONNECTOR_EMBEDDED=false before updating to prevent two connectors from competing for the same sessions. To disable the channel across the installation, set WHATSAPP_CONNECTOR_ENABLED=false.

⚡ Improvements

• Guidance for Baileys and Z-API inboxes. Both providers now carry a “Legacy” label, with a notice in provider selection and existing inbox settings explaining that they still work and recommending WhatsApp (native). Existing inboxes also offer conversion to native, with confirmation and conversation history preserved.
• WhatsApp providers organized by connection type. The list starts with the official API and then shows QR code connections, in this order: WhatsApp Cloud, WhatsApp (native), Twilio, Uazapi, Z-API and Baileys.
• Proxy under advanced options. When creating or converting a WhatsApp (native) inbox, the proxy field now sits alongside preferences under “Advanced options”. The section opens automatically if the inbox already has a proxy.
• More currencies in Kanban. When creating or editing a funnel, you can choose any official currency, with names in your screen language. Value fields and totals use each currency’s decimal places, including no decimals for the Colombian peso, Hungarian forint, Indonesian rupiah and Icelandic króna, while existing funnels remain valid.

🐛 Fixes

• Messages preserved during longer server outages. WhatsApp (native) now disconnects immediately when the installation's server becomes unavailable, so WhatsApp holds incoming messages until the connection returns. Previously, outages longer than about 30 seconds could lose messages even though the sender saw them as delivered.
• Messages arrive promptly after brief server disruptions. If a temporary problem with the installation's server prevents delivery to a WhatsApp (native) inbox, the message now arrives within seconds of recovery, with a brief inbox reconnection. Previously, it could wait for hours until the next disconnection.