Changelog

Closed chats now get AI-powered summaries and Tags in the Details section. These provide key insights and suggestions for improving your knowledge base or adding FAQs—helping your Quidget bot respond even smarter.

• Web Chat Redesign: Updated Web Chat styling and preview options in settings. 
• Slack Auto-Start: Bots in Slack now auto-start for improved workflow automation.
• Billing Updates: Welcome message and feedback questions are no longer considered in Billing.
• Web Chat Behavior on Share Page: Adjusted logic for opening Web Chat when using Show channels view. Now user don’t need to click in webchat icon twice, the can is opening in one click.
• Button Tag Update: Changed button tags from <a> to <button> for better accessibility and structure.

You abe able to Adjust the Web Chat icon size and add Chat Popup Messages to customize the experience.
System messages now notify when an agent joins or leaves Web Chat.

• No More Duplicate Messages – Say goodbye to cluttered chat history.
• Empty Chats Won’t Affect Your Stats – Keep your analytics accurate.
• Clean Chat Start – Old messages won’t appear when starting a new chat.
• Appearance Settings Stability – Changes no longer reset AI & automation settings.
• Onboarding Fix – New bots now correctly transition to step 2.
• Search Fixes – Finding nodes and training items is now smoother.
• Flow Navigation Fix – No more “Not Found” errors when switching to the Flow page.

This month, we’re rolling out Conversations—a central hub for all your chats, making real-time customer interactions smoother than ever. Plus, we’ve made key fixes and improvements to keep Quidget running seamlessly.

What’s Inside?

•  All chats in one place — Manage every conversation from a single dashboard.
•  Real-time customer responses – Respond in real time to keep customers engaged.
•  Organized inbox — Sort conversations by type for better visibility.
•  Close or Delete Chats – Keep your inbox clean and structured.
•  Chat Details & Customer Info – Get quick insights for better support.

If your bot doesn’t yet support agent replies, follow these steps:

You may not have support for Agent responses if your bot wasn’t created from an AI Agent (Powered by OpenAI) template.

• Go to the Flow Page
• Choose at which step you want to redirect the user to the agent
• Integrate the Agent Action
  – Add a node with the Agent action.
  – Connect it to the previous nodes in the failed flow.
• Customize notifications for agent handoff
• Test your setup to ensure a smooth AI-to-human transition

Why This Matters

With Conversations, you gain more control over customer interactions, ensuring that conversations are efficiently managed, properly categorized, and escalated when necessary.