- Situations where the product may be unnecessary or suboptimal
- If a knowledge base is relatively stable and product changes are infrequent, automated maintenance may not justify procurement and operational cost.
- If the primary need is a full-featured KB platform (themes, multi-language support, structured authoring, and detailed permissions) rather than ticket-driven maintenance, consider a KB-first platform such as Document360.
- Industries/use cases where competitors may be superior
- Organizations standardized on Zendesk that prefer native capabilities and minimized vendor footprint may favor evolving Zendesk knowledge tooling.
- Heavy developer documentation or API portals are likely better served by specialized documentation platforms.
- Technical requirements the vendor did not publicly document
- If SSO/SAML, SCIM, strict data residency, or comprehensive audit logging are required, confirm availability during procurement; these features were not clearly documented in public sources reviewed.
- Budget constraints
- If pricing is tied to ticket volume, rapidly scaling support organizations should verify cost trajectories in a quote request or pilot.
- Workflow/integration gaps
- Deeply customized ticketing systems or niche KB hosts could require additional integration effort; validate integration depth in a trial.
- Procurement red flags
- If the vendor cannot provide a SOC 2 report or detailed security documentation during procurement despite marketing claims, treat that as a procurement and security risk.
- Current limitations acknowledged in public materials
- The vendor does not maintain a public limitations page in the sources reviewed; most public-facing content is product-focused.
- Features on the roadmap
- Public LinkedIn activity by leadership references a planned KB health score feature across multiple dimensions, with no public timeline provided.
- Scale limitations
- No public documentation was found for explicit scale limits (for example, maximum tickets/day, maximum sources, or performance SLAs).
- Security or compliance gaps
- The vendor makes compliance claims (SOC 2, GDPR) but detailed evidence and scope were not publicly documented in the sources reviewed.
- API limitations or integration constraints
- Public details on API rate limits, supported endpoints, or integration depth were not clearly documented in accessible sources; confirm during technical evaluation.