Share your feedback, suggest features, and report bugs!

Tell us what we can do to make Chatling the best product for you.

AI Chatbot Cannot Retrieve Product Information from Variant Codes Listed in Product Page Tables

We are experiencing an issue with our AI chatbot. The chatbot's knowledge base contains approximately 1,500 website URLs, most of which are product catalog pages. Each product page includes several related product codes (up to 10 variants per product). These variant codes and their descriptions are displayed in an HTML table on the product page. The problem is that when users search the chatbot using one of these product codes, the AI agent is unable to retrieve the corresponding information and does not provide a link to the related product page. For example, on the following product page: https://www.cappellottosrl.com/prodotti/trattamento-aria/sistemi-di-ventilazione-residenziale/air-fresh-i-s/product/D01203-AIR%2BFRESH%2BI-S/ the variant codes are listed within a table. However, when one of these codes is entered into the chatbot, the chatbot cannot identify the product, retrieve its information, or direct the user to the correct product page. Could you please advise how this can be resolved? Specifically: Does the crawler/indexing process extract data contained within HTML tables? Are product variant codes being indexed correctly? Is there a recommended way to structure or expose these codes so that the chatbot can retrieve them reliably? Would it be better to provide this information through a separate data source, such as structured data, a CSV feed, or dedicated product URLs for each variant? Any guidance on improving the indexing and retrieval of product variant codes would be greatly appreciated.

Alberto about 4 hours ago

πŸ’‘ Feature Request

Completed

Model updates take too long

I don’t understand why it often takes several weeks or even months until new models become available here. For instance, Gemini 3.5 Flash would offer a fantastic balance between speed, intelligence and cost. GPT 5.5 has been released 5 weeks ago. For Opus your supported version is 4 months behind the curve. And since quite some time the frontier models come with a set of controls such as β€œeffort” or β€œfast mode” that could change things for customer support intelligence. I’m not saying we need every single update instantly. But I can’t see a clear strategy behind the model selection and how and when updates come to the platform.

Fabian MΓΆsli 9 days ago

1

πŸ“₯ Feedback

Blocked Users β€” View, Manage, and Unblock

Currently, there's no way to view or manage blocked users after blocking them. Once a user is blocked, there's no interface to: See a list of all blocked users View their metadata (location, device, date blocked) Search or filter blocked users Unblock a specific user Use case: I accidentally blocked a legitimate user while blocking a bad actor. I had no way to discover this until the user reported the issue through an alternative method. Suggested solution options: A "Blocked Users" section (under Conversations or Settings) that lists all blocked sessions with their metadata and an unblock option. In β€œConversations” add a filter for β€œBLOCKED”

Zohra 15 days ago

2

πŸ’‘ Feature Request

Allow configuring Chatling widget launcher z-index

Could you please add a configuration option to set the z-index of the Chatling web widget launcher/bubble button? At the moment the launcher uses z-index: 2147483647 (the maximum 32-bit integer / effectively the highest possible z-index). This causes the launcher to sit on top of our cookie consent banner and it blocks the banner’s buttons, so users can’t click them properly. Because this is already the maximum z-index, we can’t fix it by raising our cookie banner above the widget. We need a way to lower the widget’s z-index via configuration (e.g. in window.chtlConfig), or an officially supported override. Ideally, it would be great to support separate z-index settings for: the launcher/bubble button the expanded chat window

Salata 23 days ago

πŸ’‘ Feature Request

Conversations & Conversations Export

When exporting conversations, it provides the following data: Conversation ID Message ID Type Message Date It would be helpful to also have the following data associated with the conversation: Status (Open, Closed, Important) Notes (The notes that you can make in a Chat that are only for internal viewing) Visitor Location Assigned Agent I assume that someone out there would have need for all of the data you can view on an individual conversation so if it’s easier to implement, just give us all the data. We can always hide columns we don’t want. From the Conversations Screen, it would be helpful if you could filter on a conversation ID (the one that matches the Export. That way if you wanted to find a specific conversation you reviewed in an export and fine tune an answer you can easily find the conversation.

Zohra about 1 month ago

πŸ’‘ Feature Request

URGENT: Need a way to MUTE Chatling on WhatsApp (Coexistence) - System messages sent to live customers!

Hi Ali and the Chatling Team, Thanks again for helping us connect the WhatsApp Coexistence flow successfully today. However, we are now facing an urgent issue. The connected number is actively being used by our sales rep on her mobile app, but Chatling keeps sending automated system messages to our real customers. Since we are still building the bot in the background, we need Chatling to be completely silent. Currently, there seems to be no way to pause the bot without disconnecting it entirely: If the bot is unpublished, customers receive: "Error starting chat... (CODE: 1944)" If we publish an empty flow or route it directly to 'Human Handoff', customers receive: "The chat has ended" How can we completely MUTE Chatling right now? We need to stop the platform from sending ANY automated system messages on WhatsApp while we finish configuring the AI. Is there a "Pause" toggle for the WhatsApp integration, or a way you can disable these default system messages on your end immediately? A "Mute" or "Test Mode" feature is absolutely crucial for anyone using the Coexistence model so we don't spam live customers while building the flows. Please let me know ASAP. Thanks, Koby

koby about 2 months ago

πŸ’‘ Feature Request

Completed

Connect a WhatsApp Business app" option missing in Coexistence flow

Hi Chatling Team, Following your April 3rd Changelog about WhatsApp Coexistence, we tried setting it up but hit a blocker. We followed the exact steps: Deleted the number from Meta's WhatsApp Manager. Set up the number on the native WhatsApp Business app. Initiated the reconnection via Chatling. The Issue: During the Meta embedded signup, the option "Connect a WhatsApp Business app" does NOT appear for our +972 (Israel) number. We only see the old "Add a new number" option, which forces SMS verification and fails with a "Number already in use" error. Questions: Is this a known Meta limitation specifically for the +972 region? Is there a workaround to enable this feature for our account? Thanks, Koby

koby about 2 months ago

3

πŸ› Bug Reports

API Support for Importing Zoho Articles

Currently, the only way to manage Zoho article imports is manually through the UI: Deleting and re-adding entries. This honestly feels quite inefficient. While it’s great that there is an option to import Zoho articles at all, it doesn’t really scale for a knowledge base in a ticket system. Content changes frequently: new articles are created daily, others get removed, and existing ones are updated. Yes, the auto-sync handles updates for already imported articles, which is helpful. However, there is no way to automatically handle newly created or deleted articles. This can neither be managed natively nor via API, as there is no available endpoint for it. I’m wondering if there is any kind of workaround for this. Given that we’re working in an environment that heavily promotes automation and AI-driven efficiency, it feels a bit ironic that such a basic process still relies on manual handling.

Sven 2 months ago

πŸ’¬ General