chathq

Generic AI does not know a company's policies, documentation, or internal processes. ChatHQ is built to turn those sources into assistants for customer support and internal teams.

A team creates an assistant, adds instructions and knowledge sources such as documents, websites, policies, and FAQs, then tests its responses before launch. The public documentation describes two delivery options: an embeddable website widget and a REST API. Workspace settings cover members, roles, branding, allowed domains, usage limits, and analytics.

The clearest fit is a team that wants separate assistants for support, sales, onboarding, IT help, or internal knowledge while managing the source material in one workspace. The site also presents education and training as a use case.

The public pricing page shows a free Starter tier with one assistant, 200,000 characters of shared knowledge, and 200 messages per month. Paid tiers add assistants, messages, embed domains, analytics, and integrations. Prices and limits can change, so buyers should confirm the current plan before choosing one.

ChatHQ gives the work around an assistant as much attention as the chat box. Source setup, prelaunch testing, domain controls, team access, delivery, and usage review all appear in the same public workflow. That makes the product easier to understand before signing up.

This Project Note is based on ChatHQ's public site and documentation. I did not create an account, test answer quality, inspect a private workspace, or verify access controls and deployment behavior.