AI search
Customers get direct answers from your articles.
[ INTAKE · PRODUCT ]
Docs help, but they are not enough when the answer depends on the user’s plan, settings, usage, or account state. With Actions, Intake can also call your API to resolve it.

Acts, not just answers
You define the endpoints and access level. The agent makes GET and POST requests to your product to check real state or run the next step.

AI resolution
AI answers with documentation and real account state. If it cannot resolve, it escalates with context.

Human control
When AI should not answer alone, you get the thread, history, account state, and what the agent tried.

Contextual docs
The agent combines articles with plan, settings, usage, and state to give a specific answer.

Publish answers, connect documentation, and let AI use trusted knowledge before escalating to the team.
Explore help center
Customers get direct answers from your articles.
The team replies with up-to-date and consistent knowledge.
Create clear articles with images, blocks, and useful sections.
Embedded widget inside your SaaS to resolve where the user gets blocked.
Turn repetitive emails into tickets with visible account state.
Handle Slack questions with account context before replying.
Every conversation arrives with history, plan, settings, usage, and what the agent already checked so you resolve faster.

AI answers with docs and real account state to reduce repetitive tickets.

The team sees history, plan, previous conversations, and relevant signals without opening other tools.
Plan, settings, usage, and state next to every conversation.
Notes and context when a person needs to step in.
Measure which tickets did not reach the team.
Help the team reply to customers in different languages.
The agent is designed to work with customer data in a controlled way, with secure access and human decisions when they matter.
Yes. It answers using documentation and real user context: plan, settings, usage, and account state.
Actions are GET and POST calls the agent makes to your API within the permissions you define, to check real state or run a change instead of just describing it.
The agent is an AI support agent embedded in your SaaS. It reads real account context and answers repeated questions before they add load to the team.
No. The agent reduces repeated work and escalates the cases where a person adds judgment.
Yes, but it does not stop there. The agent combines docs with plan, settings, usage, and real account state.
Most teams start with the repetitive questions creating the most load and the account data needed to resolve them.