Share your feedback, suggest features, and report bugs!

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

Share or Embed Conversations, Analytics, and Contacts Tabs for Clients

It would be incredibly useful to have the ability to securely share the Conversations, Analytics, and Contacts tabs with clients โ€” either via a secure, shareable link or through an embeddable version that can be integrated into client-facing portals or dashboards. This feature would allow clients to: Monitor conversations in real time or review chat history View analytics to understand chatbot performance and usage Access contact lists generated from user interactions To ensure flexibility and security, the ideal functionality would include: Read-only access options Password protection or token-based authentication Customizable embeds via iframe or script Option to restrict data by bot, project, or date range This feature would enhance client collaboration, improve transparency, and simplify reporting โ€” especially for agencies or teams managing multiple bots on behalf of clients.

Tuur Desmet 2 days ago

๐Ÿ’ก Feature Request

Company-Based Password Access & Tracking for Chatbot Users

Currently, Chatling does not support differentiated access control using passwords tied to specific companies. This limits the ability to segment users or identify their organization during admin review. Requested Enhancements: 1. Company-Specific Password Access Enable support for creating and assigning unique passwords for different companies. When a user accesses the chatbot, they must enter the password provided to their organization. This password determines access and associates the user with a specific company. 2. Company Tagging in Conversations for Admin View In the admin panel where conversations are reviewed, display the company name or code based on the password entered by the user. This helps admins quickly identify which user belongs to which company (e.g., users with abc123 are from Company A, xyz456 from Company B).

Anugrah Joshi 20 days ago

๐Ÿ’ก Feature Request

Smart Multilingual & Voice-Aware Chatbot for Pan-India Users

Currently, Chatling uses the Language Condition block to respond based on the browserโ€™s language setting (e.g., Spanish, French, English). While this works well for a few languages, manually building separate flows for each regional language in India is impractical and time-consuming. ๐Ÿงฉ Requested Enhancements: 1. Smart Multilingual Understanding & Response The chatbot should understand and respond in any Indian language, regardless of whether it is natively supported. Use language detection + translation models to: Detect user input (typed or spoken) Translate to internal language for processing Respond back in the same language as the input (even if itโ€™s unsupported like Marathi, Tamil, etc.) 2. Universal Voice Support Accept voice input in any Indian language. Generate text or voice replies in the same language for inclusive interaction, especially useful for rural or elderly users. 3. Eliminate Need for Manual Multi-language Flows Avoid creating separate decision branches (e.g., IF language == 'X') for every language. Instead, use a dynamic translation-based pipeline, saving time and ensuring scalability across Indiaโ€™s linguistic diversity. ๐ŸŽฏ Why This Matters: Increases accessibility and reach across Indiaโ€™s diverse regions. Supports non-English and non-Hindi speakers who prefer their native language. Saves significant development effort and time for bot creators. Aligns with Digital India and Bhashini initiatives promoting digital inclusivity.

Anugrah Joshi 21 days ago

๐Ÿ’ก Feature Request

Add Clear Documentation for Google Sheets Integration

Please provide in-app explanations or detailed documentation for the different blocks available in the Google Sheets integration โ€“ specifically: Add Row Update Row Clear Row Delete Row Currently, these blocks appear without any guidance on: How they differ from each other What each one actually does When and how to use them with variables or user inputs What setup is needed in the Google Sheet (e.g., headers, ID columns) Why this matters: As a chatbot developer using Chatling, I find the Google Sheets integration very useful but also confusing without proper documentation. It's hard to use these blocks correctly without knowing their purpose and behavior. Clear examples and tooltips would help users integrate Google Sheets confidently and avoid errors. Suggested Improvements: Add tooltips or info icons next to each block Provide sample use cases or templates Explain what "Clear Row" vs. "Delete Row" actually does (e.g., does "clear" empty cell values but keep the row? does "delete" shift rows up?) Looking forward to seeing this improvement for a smoother experience with Google Sheets integrations.

Anugrah Joshi 21 days ago

๐Ÿ’ก Feature Request

Better Explanation, Examples & UI Improvements for HTTP Request Block

As a chatbot developer using Chatling, Iโ€™ve found the HTTP Request block to be powerful but quite difficult to understand in depth โ€” especially when dealing with complex setups like headers, query parameters, dynamic path variables, or mapping JSON responses. Currently, the block includes options like: Request method (GET, POST, PUT, PATCH, DELETE) Endpoint URL Request options (headers, query parameters, body) Capture Response to a variable (JSON required) However, these features are not explained clearly within the platform, and there are no detailed examples or visual guidance, which makes it hard for new users to implement API integrations correctly. ๐Ÿ’ก Suggested Improvements: 1. Add Detailed In-UI Explanations for Each Field Tooltips or small info icons (โ„น๏ธ) next to each field with simple explanations. For example: Headers: โ€œUsed for passing authentication tokens or content-type info (e.g., Authorization: Bearer your_token)โ€ Request Body: โ€œOnly used in POST/PUT/PATCH. Must be valid JSON. You can include variables using {{variable_name}}โ€ 2. Provide Real-World API Examples Include sample configurations (preset templates) such as: โ€œGet product by IDโ€ โ€œSubmit a contact formโ€ โ€œAuthenticate with a tokenโ€ These examples should pre-fill the HTTP Request block to show how each part connects. 3. Add Preview/Test Functionality Let users test the API call directly from within the block. Show the raw request and raw response (status code, headers, response body) to help with debugging. 4. Better Response Mapping Interface After capturing a JSON response, show a visual tree viewer of the response with easy ways to bind values like {{response.product.name}}. Add a response validator or sample preview.

Anugrah Joshi 21 days ago

๐Ÿ’ก Feature Request

Add Support for Additional Indian Languages + Voice Interaction in Native Language

My chatbot is used across India where users speak diverse regional languages. Currently, Chatling supports only English, Hindi, and Bengali. However, this limits accessibility for users who prefer languages like Marathi, Tamil, Telugu, Malayalam, Kannada, Gujarati, etc. To better support a Pan-India audience, I request the following enhancements: Requested Features: Add More Indian Languages: Support languages like Marathi, Tamil, Telugu, Kannada, Malayalam, Gujarati, Punjabi, Assamese, and Urdu. Allow users to choose their preferred language at the start of the chat or detect it automatically. Voice Input + Native Language Reply: If a user speaks in Marathi (or any supported language), the bot should: Understand the voice in that language. Respond in the same language, either via text or synthesized voice. This would ensure inclusivity for non-English/Hindi speakers, especially for users who are not comfortable with typing. Why Itโ€™s Important: India is a multilingual country โ€” supporting more languages will increase accessibility, user satisfaction, and reach. Many rural and regional users prefer voice-based interaction in their native tongue. It aligns with government initiatives like Digital India and Bhashini.

Anugrah Joshi 21 days ago

๐Ÿ’ก Feature Request