Khoros Care, Marketing, Flow Release notes - May 15th 2026
Here is a list of the released features and bugfixes from this release period: Marketing (Spredfast) Faster Post Lists for High-Volume Accounts: Fixed a performance issue that caused post lists to time out for accounts with tens of thousands of posts. They now load in seconds Reliable Auto-Labeling: Fixed an issue where auto-labeling failed when label libraries were large, and improved diagnostics for duplicate native LinkedIn posts Threads Token Debugger Restored: Fixed an issue where the Threads token debugger returned 500 errors instead of results Flow RBM Message Delivery Retry: Rich Business Messaging deliveries now automatically retry on transient failures, so brief carrier hiccups no longer lose customer messages or strand conversations in bot mode Reliable Dropdown Menus on Sources Page: Fixed an issue where the Import CSV, Import Sheet, and Add Segment dropdowns intermittently failed on first click Web Channel & Gateway Reliability: Addressed stability issues in the web client channel and gateway services for more reliable real-time messaging Care Faster Tag Sync from Community to Care: Fixed an issue where community board renames and thread title edits required manual intervention to reach Care conversations. They now sync automatically, so agents see the latest titles and tags as they appear in Community TikTok / LinkedIn: Restored Visibility for Hidden Social Replies: Fixed an issue where TikTok and LinkedIn brand replies didn't reflect their hidden/visible state in Care, and where image-only Facebook Messenger messages were dropped during ingestion Facebook / LinkedIn: Brand Mention Ingestion for Personal Account Posts: Fixed an issue preventing Facebook brand mentions from personal accounts from reaching Care, and resolved a defect that made top-level LinkedIn brand mention posts unclickable in Posts columns Real-Time Reply Delivery for Agents: Fixed an issue that occasionally forced agents to refresh the page to see their replies. Replies now appear in conversations immediately Push Next Routing Reliability: Fixed an issue where conversations could get stuck unrouted after a transient indexing failure. Push Next now picks them up automatically once indexing recovers Reliable Bot-to-Agent Handoff: Fixed an issue where new conversations started seconds after an agent closed the prior case inherited stale ownership data. The bot now resumes cleanly and hands off to an agent as expected Accurate Bot-Handoff Queue Priority: Fixed an issue where queue position after a bot handoff didn't reflect the customer's actual wait time. It is now based on the earliest unanswered customer post, restoring expected SLA position Apple Messages for Business: URL Reliability: Fixed an issue where URLs were silently dropped when rich link previews failed. The URL is now sent as plain text fallback, so customers always receive what the agent intended, including in mixed text-and-URL messages Yelp Integra…183ViewsSign in to react to this post0CommentsKhoros K1, Care, Marketing, Flow Release notes - December 1st 2025
Khoros Care Customer Experience Improvements TikTok Response Labeling Enhancement: Agent responses to TikTok conversations are now correctly identified in the conversation timeline, eliminating incorrect "External response" labels that caused confusion for agents Trustpilot Data Recovery: Backfilled missing Trustpilot reviews that failed to process during authentication issues, restoring complete customer review data Community User Avatar Handling: Fixed issue where Community users without profile pictures caused processing failures, ensuring all Community posts are properly delivered to Care Brand Messenger Chat Reliability: Resolved bot response delivery issues in Brand Messenger widget, ensuring consistent message arrival and improved error logging for customer interactions Social Media Authentication & Message Processing: Resolved authentication issues and improved message processing reliability for social media channels, ensuring consistent delivery of customer messages Message Processing Reliability: Improved retry mechanism for failed message processing, reducing message delivery failures Performance & Scalability European Region Performance: Increased capacity in EU region to handle higher load during business hours, improving response times and system stability Proactive System Monitoring: Deployed comprehensive monitoring across US, EU, and APAC regions to validate core platform functionality including agent conversation handling, queue management, agent assist widgets, and dashboard access Admin Console Change Log Navigation: Change Log has been released from Beta and is generally available. User Management Enhancements: Improved batch user processing and cache synchronization to prevent data loss during user management operations Security & Platform Updates Security Enhancements: Deployed security fixes across multiple Care components: Analytics Dashboard: Critical security vulnerability patches Case Management Interface AI/ML Processing System Brand Messenger Chat Backend Publishing Interface: Latest security patches Messaging Authentication Khoros Marketing Platform Improvements Instance Management: Fixed server error that was preventing Marketing instance deprovisioning, improving platform lifecycle management User Moderation: Resolved issue preventing users from being banned in Marketing Inbox, restoring full moderation capabilities Stream Collections: Fixed deletion functionality for stream collections Infrastructure & Performance Social Gateway Updates: Deployed infrastructure improvements for enhanced reliability and performance Advertising Metrics Processing: Improved reliability of advertising metrics data collection by introducing safeguards to prevent processing failures Notification System: Improved stability of the notification system Enhanced Security Protocols: Strengthened database security protocols as part of ong…ViewsSign in to react to this postCommentsKhoros K1, Care, Marketing, Flow Release notes - December 15th 2025
Here is a list of the released features and bugfixes over the last two weeks: Marketing (Spredfast) Enhanced Analytics Data Processing: Fixed critical data processing workflows to ensure analytics reports display accurate metrics and insights without delays Improved Platform Reliability: Addressed stability issues that affected content publishing and analytics workflows during peak usage periods Flow Configurable Search Precision: You can now customize how many documents are analyzed when using AI search reranking, allowing you to balance between search speed and result accuracy based on your needs Faster AI Training Completion: Training jobs now complete significantly faster by running at higher priority, reducing wait times when setting up new AI capabilities Multi-Language Agent Handover: Fixed chatbot prompts that were always in English - the "connect with an agent" suggestion now appears in the same language as the customer's conversation Improved System Responsiveness: Optimized background processes to reduce latency and improve overall platform performance during high-traffic periods Care Instagram: Accurate Ad Content Attribution: Fixed an issue where Instagram ads from other accounts were incorrectly appearing under your brand - ads now correctly filter to show only content owned by your configured Instagram account Instagram:Better Multi-Brand Response Handling: When managing multiple Instagram brand accounts mentioned in a single conversation, the system now correctly identifies and uses all relevant brand tokens for responses, preventing missed reply opportunities TikTok: Correct Response Attribution: TikTok replies are now properly labeled as your brand responses instead of being marked as "External Response" - improving conversation tracking and reporting accuracy LinkedIn: Reliable Comment Deletion: LinkedIn comment deletion now includes verification and automatic retry logic to ensure comments are successfully removed, with clear logging of success or failure status Facebook Messenger: Clean Secure Chat Invitations: Secure chat invitation links sent via Facebook Messenger now display cleanly without showing raw URLs or incorrect "Post edited" labels in the agent timeline Fixed Moderation Column Updates: Posts now automatically disappear from Community Moderation columns after being moderated, instead of remaining visible with a spinning indicator indefinitely Support for Authors Without Profile Pictures: Fixed a critical issue preventing Community posts from authors without profile pictures from appearing in Care - these posts now process correctly and reach your agents Prevent Duplicate Cases: Eliminated race condition that created multiple cases when customers sent rapid messages - now ensures only one case is created per customer conversation, even during high-traffic periods Clearer Integration Connection Errors: Integration connection failures now display helpful error messages …ViewsSign in to react to this postCommentsKhoros K1, Marketing, Care and Flow release cadence
As part of our ongoing commitment to reliability and transparency, we have adopted a continuous delivery model for Khoros K1, Care, Spredfast Marketing and Flow. This means improvements, fixes, and enhancements are deployed to production incrementally rather than through large, infrequent releases. This approach minimizes operational risk, accelerates value delivery, and ensures that your environment benefits from the most stable and secure version of our product at all times. We recognize that visibility into product evolution is essential for planning and governance. To provide this transparency, we are introducing a regular changelog where you can review all functional, performance, and stability updates that have been deployed. Each entry will briefly describe what has changed and when, serving as a single source of truth for product updates. Our initial plan is to publish changelog updates on a regular cadence (approximately bi-weekly) on the release notes space, ensuring timely and consolidated communication without excessive notifications. As the product continues to evolve, we may adjust this frequency to align with customer needs and product maturity—always maintaining consistency and clarity in how updates are communicated.ViewsSign in to react to this postCommentsKhoros Flow v25.04.2 Release Notes
Enhancements Deprecated Channels Removed from UI The following deprecated channels with no activity are no longer shown in the UI: Apple Front MessageMedia Mavenir Rocket Chat Telekom RBM Kik Viber Google Business Messages Twilio Facebook Messenger WhatsApp This cleanup helps reduce clutter and prevent confusion from unsupported options. Users now see only active, supported channels when integrating Flow projects. However, users can still add these channels to their projects from the Khoros Care integration as shown below:ViewsSign in to react to this postCommentsKhoros Flow v25.03.2 Release Notes
Enhancements Variables rev2 In this release, we have introduced the ability to reuse data variables and system variables, along with UI improvements for managing variables. Managing variables helps developers to reuse data across their bot architecture without hardcoding it in code actions. Additionally, it ensures that text variants ingested into Gen AI personas remain consistent, reducing the risk of errors caused by accidental edits. These enhancements provide a more seamless and reliable experience when working with variables in bots. The following screenshot shows the changes in Configurations > Variables: Improved visual appearance: Reduces clutter by distinctly separating variable types. Separated entities: Variables are displayed as distinct entities, allowing future possible enhancements like project-based selection. Resizable text area: Text variables now auto-resize, making it easier to view and edit long entries. New data variable type: Supports JSON input, enabling users to store and manipulate structured data without creating multiple individual variables. Following is an example of how you can now use them in your flow: When you select EDIT for the TRIGGER ACTION, the code action opens and you can add the data variables you want. The below screenshot shows the “var_vehicle” variable used in the code action. Here, the variable is used to create a carousel. You can view the values in the array from the LOGS tab on the left pane. The following is a screenshot showing how the carousel renders during user-bot interaction. The code action pulls in all vehicle data to create the carousel in real time. Terminology Knowledge In this release, we introduce a way to add knowledge sources that allows businesses to define and manage their specific terms and acronyms. By defining terms and acronyms, AI-driven assistants interpret terms accurately within the right context, reducing misinterpretations and improving response quality. By providing a structured way to handle terminology, this feature enhances workflow efficiency and minimizes user frustration. With Terminology Knowledge you can: Create new terminology. Create a new segment or multiple segments under the same terminology. Move terminology within sub-segments or into different segments. terminology from one source to another. terminology from a parent segment to a child segment of the same source. Import and export terminology. Delete a parent terminology along with its child segments. Automation Rules Logs In this release, we introduce dedicated automation logs, similar to bot logs, to enhance the troubleshooting and debugging process for automation rules. These logs feature distinct visual cues for "WHEN," "IF/OR," and rule execution activities, making it easier to track rule behavior. On your…ViewsSign in to react to this postCommentsKhoros Flow v25.03.1 Release Notes
Enhancements Add conditions to conversations With this release, you can add Condition (enables branching based on user input) reply blocks directly in your flows for Google Dialogflow projects. This enhancement offers greater flexibility, improving automation and user experience without extra coding and building for more dynamic and responsive chatbot interactions within Flow. The following is an example of a Dialogflow project where there is a condition to check if a shop is currently open. The below screenshot shows the Condition block added to check if they are open: The following screenshot shows the Condition block added to check if they are closed: The below screenshot shows the preset Business hours: The below screenshot shows how Dialogflow interacts with the user in real time.ViewsSign in to react to this postCommentsKhoros Flow v25.01.1 Release Notes
Enhancements Updates for changing persona in UI Previously, you could select only from the pre-defined prompt templates in Flow to set up Personas for your Bot or Agent Assist. With this release, we’ve introduced the ability to use an external source for Bot and Agent Assist Personas. By leveraging external sources, you can now align Personas more closely with your brand voice, business requirements, or specialized use cases, offering an improved and more personalized customer experience. To enable this functionality, use the new field called Config Type under ORGANIZATIONS > Personas. By default, Config Type is set to Internal. You can select one of the prompt templates from the Prompt template drop-down menu. To use an external Persona source, select External from the Config Type drop-down menu and enter the URL containing the Persona details into the Url field. Learn more about Persona UI. Support triggering events in other languages from Code Actions Previously, you could trigger events in other languages using Event Replies. With this release, you can now achieve the same functionality using Code Actions. Add the following to your code in Code Actions: trigger("Change language", { language: "language preferred” }) If no language is specified, the conversations are continued in English. You found it! We fixed it! Excel sheets now import successfully into Knowledge projects. When you sync languages, event triggers with a specific language selected retain their language setting instead of being reset to Current Language. When you switch to the secondary language, all events related to the language load successfully in the Events drop-down menu.ViewsSign in to react to this postCommentsKhoros Flow v25.02.1 Release Notes
Enhancements Add delays to conversations In this release, we've introduced a Delay option in Replies in Dialogflow projects. When the bot sends multiple replies, you can add short pauses between messages to create a more natural conversational flow and enhance the user experience. These delays help ensure messages are processed and displayed in the correct order. In flows where the bot sends multiple text replies, a delay in delivering each message gives users enough time to read them. The following screenshot shows an example of multiple long messages that the bot sends. A delay added between the 2 messages allows users to take time to read the message as it appears. Read more on Delays.ViewsSign in to react to this postCommentsKhoros Flow v24.12.1 Release Notes
Enhancements Enhanced URL Validation Previously, only URLs starting with https:// were allowed, limiting flexibility for specific customer needs. With this release, we have expanded the types of URLs accepted during validation to support a broader range of use cases, including those involving custom protocols. Supported URL formats now include: Standard web URLs (https://, http://) Custom protocols (sms:, tel:, mailto:, etc.) This update ensures greater compatibility with diverse customer use cases, such as those requiring custom protocol links. Expanded Language Support for Named Entity Classification Earlier, support for Named Entity was available only for Chinese. With this release, we’ve expanded language support to include the following: Catalan Chinese Croatian Danish Dutch English Finnish French German Greek Italian Japanese Korean Lithuanian Macedonian Norwegian Polish Portuguese Romanian Russian Slovenian Spanish Swedish Ukrainian Multi-language (for unsupported languages) You Found It. We Fixed It. Timers, Delays, and Event triggers Fields for Timers, Delays, and Event triggers are now locked in the production environment to prevent modifications. This ensures the stability and integrity of live flows. Priority reply type visibility The Priority reply type visibility logic has been updated to ensure consistency, making it visible only for channels integrated through Button actions payload All button actions now generate the appropriate payload, with the payload structure updated to include necessary fields like trigger type and name, and integration compatibility between Brand Messenger and Flow verified across environments.ViewsSign in to react to this postComments
183Views
0Comments
