- Company sizes or stages where this product is overkill or insufficient
- Organizations with extremely low support volume that can be served by a static FAQ or knowledge base.
- Highly regulated organizations that require independent security attestations for procurement.
- Industries or use cases where competitors may be more appropriate
- Regulated industries (healthcare, finance) that require documented SOC 2 Type II reports and detailed governance controls.
- Complex support operations that require deep helpdesk-native integrations and ticket lifecycle automation.
- Technical requirements that the product cannot meet
- Highly customized policy enforcement, custom tool execution, or deep backend integrations without third-party automation.
- Budget considerations where alternatives may be more appropriate
- Organizations with highly variable usage patterns may face forecasting challenges with credit-based pricing and should consider vendors with clearer overage economics.
- Specific workflows or integrations where the product falls short
- Native, auditable integrations into Zendesk/Salesforce/Jira with strict role-based approvals may be limited if integration is primarily via Zapier/Make.
- Red flags in the buying process
- If the vendor cannot provide a clear security package (subprocessor list, hosting regions, encryption details, access controls, incident response commitments) aligned to buyer requirements, procurement risk increases.
- Current limitations acknowledged by the vendor
- Product terms explicitly note the risk of hallucinations and that outputs may be incorrect or incomplete.
- Users are responsible for configuration and appropriate use.
- Features on the roadmap (not yet available)
- No public, dated roadmap was identified in the sources reviewed.
- Scale limitations (at what volume/size does it become constrained)
- Plan limits are documented (message credits, crawl pages, characters per bot). Practical scaling depends on content size, retrieval quality, operational governance, and channel load.
- Security or compliance gaps
- Absence of publicly documented SOC 2/ISO certifications and limited public information about SSO/SCIM/audit logging are potential procurement blockers for some buyers.
- Technical debt or architectural limitations mentioned in reviews
- Insufficient independent user feedback to draw conclusions about architectural limitations.
- API limitations or integration constraints
- Public documentation about APIs is not prominent; the vendor emphasizes Zapier/Make for integration breadth.
