Updates from our Chatwoot fazer.ai editions

Includes changes from Chatwoot fazer.ai v4.17.0-fazer-ai.101.

🐛 Fixes

• A conversation that already has an owner no longer sits in Unassigned. If the browser missed the notice, usually a blink of network during an assignment, the conversation stayed listed as unassigned while the number beside the tab showed the truth. The leftovers piled up through the day until someone reloaded. The dashboard now notices the contradiction and asks the server how those conversations really are, and it also checks the whole list once whenever the connection comes back, which is exactly when notices get lost.
• The Individual/Group filter now applies to the tab counter too. The filter only ever shaped the list; the number beside the tab counted both kinds. It is also remembered between sessions inside the sort menu, so it was possible to sit on it without noticing. The bulk action bar also kept a conversation selected after it left the list, so the next bulk action was still sent to it.
• A lead that crosses from WhatsApp into the website chat stays one person. Sometimes it came out as two: the WhatsApp contact it keeps writing on, plus a widget contact holding the identifier that belonged to the first one, carrying a slice of history connected to nothing. A redirect link now records which contact it was minted for, and the visitor is merged onto that contact.
• SAML sign-in stops dressing a setup error as an authentication failure. An assertion carrying an address the database will not accept used to end on a 500 instead of the login page. And a role mapping pointing at a custom role that does not exist reported a failed sign-in while the user it claimed not to have authenticated already existed. Only a rejected assertion is reported as a failed sign-in now.
• An automation rule that emails a team keeps its name on the actions that follow. Sending the email cleared the rule from the account context and never put it back, so every action after it in the same rule produced activity messages with no author.

Includes changes from Chatwoot fazer.ai v4.17.0-fazer-ai.100.

🐛 Fixes

• WhatsApp contacts no longer come in with a phone number nobody can dial. When history was imported from a number whose WhatsApp account uses the newer internal identifier, contacts were created with that identifier sitting in the phone field. It is a long string of digits that looks like a number but reaches no one, and it left the contact impossible to recognise. Those contacts now arrive with the phone field empty until the real number is known, and the first message the contact sends fills it in.

Includes changes from Chatwoot fazer.ai v4.17.0-fazer-ai.99.

🐛 Fixes

• The Unassigned tab now matches its own counter. A conversation a bot is handling is not waiting for a human, so it stays out of Unassigned and shows up under All, exactly as the number beside the tab already said. Before, switching to All and back made those conversations appear in the list while the counter stayed put, and agents could not tell which queue was the real one.

Includes changes from Chatwoot fazer.ai v4.17.0-fazer-ai.98.

✨ What's new

• Conversation history on WhatsApp - Baileys inboxes. Connecting a number now brings in the conversations that already exist on the phone, filed as reference. Inside a conversation you can ask the phone for older messages as many times as you need, and Chatwoot tells you when there is nothing older left.
• Nothing is lost when the WhatsApp connection drops. Messages that arrived while the inbox was disconnected come in open in the queue when it reconnects, instead of disappearing.
• Reports that cross agent and inbox. You can now see one agent's performance in a single inbox, or one inbox broken down by agent. The filter lives in the link, so a report you check every day can be saved, and the CSV follows it.

🐛 Fixes

• A delivered message no longer shows as failed. A reply WhatsApp had already delivered could be marked as an error because of an internal delay, which led agents to send it a second time.
• Conversations the bot stopped answering. A momentary slowdown handed a conversation off from the bot, and it stayed silent no matter how much the customer wrote. It now leaves the bot only after delivery really fails.

Includes changes from Chatwoot fazer.ai v4.17.0-fazer-ai.97.

✨ What's new

• A new WhatsApp provider: uazapi (beta). Connect a number by scanning a QR code or typing a code on the phone, without going through Meta's official API.

⚡ Improvements

• More reliable WhatsApp. Sends, edits, reactions, attachments and group actions are more consistent, and a message that can't go out now shows as failed instead of looking delivered.
• Conversation history loads in full. Scrolling up no longer skips messages.