What I like best about Upland RightAnswers is the knowledge-authoring experience. The WYSIWYG editor is simple and intuitive for day-to-day use, and it allows us to create and segment content for multiple audiences while maintaining appropriate governance. The platform is flexible enough to support our Knowledge-Centered Service, or KCS, practices rather than requiring us to force our processes into a rigid model.
The keyword search is fast and effective, consistently placing relevant articles near the top of the results. Our users have been more satisfied with the search experience than they were with our previous knowledge platform. We have found its traditional keyword search particularly effective for our highly technical content.
Upland also provided strong support during implementation and helped us complete the setup and launch successfully. Their team works with us to understand our requirements and accommodate our needs within the product and their business constraints. Upland’s KCS v6-certified training is another significant advantage because we can receive KCS guidance from the same company that develops the platform. This gives us a stronger connection between the training, the product’s capabilities, and the KCS practices it is intended to support.
Although our Salesforce integration has room to improve, RightAnswers provides the core ability to search for and link knowledge from our CRM workflow. Overall, the combination of intuitive content creation, effective keyword search, KCS alignment, and responsive support makes RightAnswers valuable to our knowledge program. Upland has provided one of the best vendor experiences I have had during my 15 years with my company, and we have developed a strong, trusted working relationship. Review collected by and hosted on G2.com.
Upland RightAnswers can be difficult to implement and configure effectively. A successful implementation requires substantial training, professional-services support, a strong understanding of Knowledge-Centered Service, or KCS, and careful planning to ensure the platform supports the organization’s knowledge strategy and workflows.
I would like the platform to have a more modular architecture, particularly for integrations with third-party systems such as Salesforce and Microsoft Teams, as well as for compatibility with major browser engines. Our experience has been strong with Chromium-based browsers, but Firefox and Safari have presented additional challenges. Each environment can require significant customization instead of allowing customers to configure and reuse standard integration components. This increases implementation complexity, reliance on professional services, and the cost of maintaining or expanding the platform.
The Salesforce integration has been one of our largest frustrations. It does not provide a strong “create in the workflow” experience that allows support professionals to create or improve knowledge while remaining in Salesforce. Requiring users to leave Salesforce to complete common knowledge tasks interrupts the support workflow.
The standard integration also did not expose the RightAnswers fields that control audience visibility and governance, which was a major gap for us. We had to pay for custom development before we could apply those controls to linked solutions, include the appropriate solutions for each audience in case email templates, and expose eligible content on our customer-facing website. We consider these fundamental knowledge-integration capabilities rather than optional customizations.
I would also like stronger native Salesforce capabilities for searching and linking knowledge, using case information as search context, and creating or improving content directly within the CRM. Compared with current expectations for enterprise CRM integrations, the RightAnswers integration requires significant modernization.
Reporting is another area that could be improved. Some KCS reports cannot be produced out of the box without additional interaction with our CRM. I would like a more complete set of structured and interconnected KCS reports, along with stronger point-in-time and historical snapshot reporting.
Some workflows feel too one-directional and do not provide enough control to prevent users from taking actions that conflict with our intended governance model. Although Upland promotes and teaches KCS, we have occasionally needed to encourage greater consistency between those principles and the way its product features, integrations, and processes are implemented. Better alignment between the product and Upland’s KCS guidance would strengthen the overall experience.
Like many technology companies, Upland is placing greater emphasis on AI. However, the technology still feels experimental for some of our use cases. Cybersecurity teams are understandably cautious, and these capabilities introduce additional costs before an organization may have enough evidence to determine whether they are appropriate. Based on our experience with hybrid and neural search, I am concerned that AI-generated or AI-ranked results can become too generalized unless they are carefully scoped and grounded for a highly technical support environment.
The AI pricing model also feels too all-or-nothing. I would prefer a modular, menu-based model that allows customers to select and pay for individual AI capabilities according to their business requirements, security posture, technical suitability, and organizational readiness. This would make it easier to evaluate and adopt specific features without purchasing a broader package that includes capabilities we may not be ready or permitted to use.
We have also raised privacy and compliance concerns about enabling website analytics, performance monitoring, and troubleshooting technologies across a global environment. In our experience, Upland does not currently provide a suitable consent-gating API that would allow us to activate these capabilities according to applicable regional consent requirements. This limits our ability to use potentially valuable analytics and diagnostic features consistently across jurisdictions.
Finally, the support experience varies depending on the escalation level. Front-line support is often fast and responsive, but progress can become much slower when an issue requires escalation or engineering involvement. Clearer ownership after escalation, more consistent status updates, and more predictable resolution targets would improve the handling of complex technical issues. Review collected by and hosted on G2.com.
