---
title: "Aivastark — AI support agent for SaaS"
description: "An AI support agent for SaaS: answers how-to, API and billing questions from your docs with code examples, opens bug tickets for your helpdesk, 24/7."
canonical: "https://www.aivastark.com/industries/saas"
source: "https://www.aivastark.com/industries/saas.md"
updated: "2026-10-07"
---
# Aivastark — AI support agent for SaaS
> An AI support agent for SaaS: answers how-to, API and billing questions from your docs with code examples, opens bug tickets for your helpdesk, 24/7.
Answers how-to, API, billing and account questions inside your app from your docs and help center, opens a ticket when it's a bug, and hands the rest to your team.
## What is an AI support agent for SaaS?
Aivastark is an AI customer-support agent for SaaS and software companies. It answers your users' how-to, API, billing and account questions inside your app and on your docs site, from your help center, API reference and documentation, with code examples in the reply. It can be told who the signed-in user is, look things up through your own API or MCP server, open a prioritised ticket for a bug and sync it to Zendesk, Freshdesk, HubSpot, Salesforce or ClickUp, score trial and demo requests, and hand the conversation to your team in one inbox.
## What users ask
- **“How do I invite my team?”** — Step-by-step answers from your docs and help center, in the user's own language.
- **“Why is the API returning 401?”** — Answers from your API reference, with code examples in the reply.
- **“What does my plan include?”** — Limits, pricing and upgrade paths from your pricing pages, and the user's own plan when you pass it.
- **“I'm locked out of my account”** — The recovery steps from your docs; anything that needs identity checks goes to your team.
- **“This button does nothing”** — Collects what happened and opens a ticket marked as a bug, synced to your helpdesk.
- **“Can we get a demo for 40 seats?”** — Captured as a lead, scored 0 to 100 and routed to the right person on your team.
## Answers from your docs, not from a forum thread
Point it at your docs site and help center, upload your API reference and changelog, and add the answers your team gives every day. The agent searches that knowledge for every question and answers from it; where your docs are thin it can draw on general knowledge, which you can see and fix. Your team sees the passages behind each reply in the inbox, and Answer Gaps lists what users asked that your docs couldn't answer, with drafted answers to approve.
- **Docs site and help center crawl** — Reads your sitemap and pages; up to 25 pages per source on Free, more on each plan above. (every plan)
- **Files, FAQs and pasted text** — PDF, Word (DOCX), TXT or Markdown: API references, changelogs, runbooks. (every plan)
- **Refresh when you ship** — Refresh a source once a day on Starter; schedule daily, weekly or monthly re-crawls on Growth. (Starter and above)
- **Answer gaps** — The questions your docs couldn't answer, with drafted answers to approve: 25 drafts a month on Starter, unlimited on Growth. (Starter and above)
## API questions answered with code, at 3am in any time zone
Developer questions rarely wait for business hours. The agent reads your API reference and guides like any other source and answers with the endpoint, the parameters and a code example, rendered as a code block in the widget. Users can write in any of 80+ languages and get the answer back in theirs.
- **Code in the reply** — Code blocks and inline code render in the widget, so a curl example keeps its formatting. (every plan)
- **Your API reference as a source** — Crawled as web pages or uploaded as files; there is no OpenAPI import. (every plan)
- **80+ languages** — Replies in the language each user writes in; limit it to the ones your team supports. (every plan)
- **Escalates what docs can't fix** — When the answer runs out, it opens a ticket or hands the user to an engineer with the thread attached. (Starter and above)
## Knows who's asking, and can look things up
Pass the signed-in user to the widget (id, name, email, plan, company and your own traits) with an HMAC signature of their id computed on your server, and the agent answers with that context: “on your Team plan you can keep two live keys”. Connect your own MCP server or API endpoints and it can look up the user's workspace, usage or invoices through your systems; on an MCP server it can act with the user's own token, and anything that changes data waits for the user to confirm.
- **Signed-in users** — Name, email, plan, company and custom traits as context, with the user id verified by your HMAC signature. (Growth and above)
- **Your MCP server** — Reads and actions through your own server, with the user's own token if you choose; writes need the user's confirmation. (Starter and above)
- **API lookups** — GET endpoints you define, such as status or usage, called when a question needs them. (Starter and above)
## Bugs become tickets your team can act on
When a user hits something the docs can't fix, the agent opens a ticket with the conversation attached, a category such as bug or billing, and a priority from low to urgent. Response targets run from your SLA policy (4 hours to first response and 48 to resolution by default, in business hours), and tickets sync to Zendesk, Freshdesk, HubSpot, Salesforce, ClickUp or your own webhook, filtered by category or priority.
- **Tickets with priority and SLA** — Opened from the chat with a category and priority, timed against your SLA policy. (Starter and above)
- **Helpdesk sync** — Zendesk, Freshdesk, HubSpot, Salesforce, ClickUp or a signed webhook; send only bugs, or only high priority. (Starter and above)
- **Slack alerts and replies** — Handoffs and tickets post to a Slack channel, and a reply in the thread reaches the user in the widget. (every plan)
- **Human handoff** — When a user asks for a person (or, if you switch the trigger on, hits two dead ends in a row), the chat passes to your team with the thread. (Solo and above)
## Turns trial and demo questions into scored leads
Not every chat is support. When a visitor asks about seats, annual pricing or a demo, the agent captures their details, classifies the lead (demo request, pricing, quote request and more), scores it 0 to 100 into a hot, warm or cold band and routes it by your rules. Automations can open the conversation when someone lingers on your pricing page or moves to leave.
- **Lead capture and scoring** — Category, signals and a 0 to 100 score with the reasons listed. (every plan)
- **Routing rules** — “Hot demo requests go to Sam”: route by category, signal or band. (every plan)
- **Lead webhook and HubSpot** — Each lead sent to your endpoint or HubSpot as it's captured, with retries. (Solo and above)
- **Page and behaviour triggers** — Start a flow on a page visit, time on page, pages viewed, scroll depth or exit intent. (Starter and above)
## Your support team stays in charge
Every conversation lands in one inbox, with the passages behind each AI reply one click away, so your team can see why it answered and fix the doc that misled it. Take over any chat, and give each teammate access to just the sections they need. Users can rate the conversation when it ends.
- **One inbox** — Website, email and messaging conversations in one list, with the agent's sources in a “Why?” drawer. (every plan)
- **Roles and section access** — Owner, admin and member roles, per-member section access and an exportable activity log; 3 seats on Starter. (Starter and above)
- **CSAT** — Users rate the conversation when it ends. (Starter and above)
- **Several products** — A separate agent and knowledge base per product: 2 projects on Starter, 5 on Growth, 15 on Scale. (Starter and above)
## How to set it up
1. **Add your docs** — Paste your docs and help center URLs, and upload your API reference, changelog and the answers your team gives every day. Aivastark builds the knowledge base the agent answers from.
2. **Paste one script tag** — Add the widget to your app and docs site. Pass the signed-in user if you want plan-aware answers, and connect your MCP server or API for lookups.
3. **Route what it can't answer** — Switch on tickets and helpdesk sync, set your SLA policy, connect Slack, and turn on handoff so your team takes over when a user asks.
```html
```
- **Script tag** — Any site or web app. Client-side route changes in React, Next.js or Vue apps are followed automatically. See https://www.aivastark.com/integrations/chat-widget
- **WordPress** — A plugin for your marketing site or docs on WordPress.
- **Webflow** — Install on a Webflow marketing site or docs. See https://www.aivastark.com/integrations/webflow
- **Slack** — Handoff and ticket alerts in a channel, with replies from the thread. See https://www.aivastark.com/integrations/slack
## What it doesn't do
- **No SSO or SAML** — Your team signs in with email and password or Google. Roles, per-member access and an activity log are there; single sign-on is not.
- **No Linear, Jira or GitHub Issues** — Tickets sync to Zendesk, Freshdesk, HubSpot, Salesforce, ClickUp or your webhook; use the webhook to reach anything else.
- **No OpenAPI import** — Your API reference is read as web pages or files, not imported from a spec.
- **No npm package** — It installs with one script tag, which works in React, Next.js and Vue apps.
- **Sources stay with your team** — Users see the answer, not a citation; your team sees the passages behind it in the inbox.
- **Docs refresh on a schedule, not instantly** — Refresh a source once a day on Starter, or schedule daily, weekly or monthly re-crawls on Growth.
## AI agent vs help center search and a ticket form
| | Help center search | Ticket form | Aivastark |
|---|---|---|---|
| Answers the actual question | Lists articles to read | Next business day | In the chat, from your docs |
| API questions with code | If an article has it | An engineer replies later | Code examples in the reply |
| Knows the signed-in user | No | From the email address | Name, plan and traits you pass (Growth) |
| Bug reports | No | Free-text tickets | A bug ticket with priority, synced to your helpdesk (Starter) |
| Other time zones | Self-serve only | Waits for your team | Any hour, in 80+ languages |
| Shows what's missing from your docs | Searches with no results | Only if someone tags it | Answer Gaps with drafted answers (Starter) |
| Hands off to a person | No | It is a person | With the whole thread (Solo) |
## Which plan a SaaS team needs
- **Free** — Answer from your docs: Widget on your app and docs, Docs crawl, files and FAQs, 80+ languages, Lead capture and scoring.
- **Solo** — Bring a person in: Human handoff, Email alerts with a summary, Lead webhook and HubSpot.
- **Starter** — Tickets, tools and your helpdesk: Tickets with SLA and helpdesk sync, Your MCP server and API lookups, Answer Gaps and CSAT, Refresh now, automations, 3 seats.
- **Growth** — Signed-in users and scheduled refresh: Verified signed-in users, Scheduled docs re-crawl, Unlimited Answer Gap drafts, 5 projects, 5 seats.
Every paid plan starts with a 7-day free trial. See [Pricing](https://www.aivastark.com/pricing.md) for prices.
## Frequently asked questions
### What is an AI support agent for SaaS?
An AI support agent for SaaS answers users' questions about your product inside your app and on your docs site, from your own documentation, around the clock. A capable one also knows who is asking, looks things up through your systems, opens tickets for real bugs and hands the conversation to a person when needed. Aivastark does all of that, from a free plan.
### Does it answer from our docs or make things up?
It searches your docs, help center, files and FAQs for every question and answers from what it finds. Where your content is thin it can draw on general knowledge, so the fix for a weak answer is usually a better doc. Your team sees the passages behind each reply in the inbox, and Answer Gaps lists the questions your docs couldn't answer.
### Can it answer API and developer questions?
Yes. Crawl your API reference or upload it as files, and the agent answers endpoint, parameter, authentication and webhook questions with code examples, rendered as code blocks in the widget. There is no OpenAPI import; the reference is read like any other documentation. When the docs run out, it opens a ticket or hands the user to your team.
### Can it identify the logged-in user?
Yes. Pass the signed-in user to the widget through window.AivastarkConfig, with their id, name, email, plan, company and your own traits, plus an HMAC-SHA256 signature of the id computed on your server. The agent uses that context in its answers. A missing or wrong signature means the user is treated as unverified, not blocked. It is listed on the Growth plan.
### Can it look up a customer's account or take actions?
Through your systems, yes, from Starter. Connect your own MCP server and the agent can read and act through it, optionally with the signed-in user's own token, and anything that changes data waits for the user to confirm. Custom API tools call GET endpoints you define, such as status or usage. It has no access to your database or billing unless you connect it.
### How does it handle bug reports?
It opens a ticket with the conversation attached, a category such as bug and a priority from low to urgent, timed against your SLA policy. Tickets sync to Zendesk, Freshdesk, HubSpot, Salesforce, ClickUp or a signed webhook, and you can send only bugs or only high-priority ones. There is no direct Linear, Jira or GitHub Issues integration; use the webhook.
### Does it work with Zendesk, Intercom or Help Scout?
Zendesk, Freshdesk, HubSpot, Salesforce and ClickUp receive tickets directly, from the Starter plan, and Slack gets handoff and ticket alerts with replies from the thread. There is no Intercom, Help Scout or Front integration; a signed webhook can push tickets to any system that accepts one.
### How does it stay current when we ship?
On Starter you can refresh a docs source once a day with Refresh now; on Growth you can schedule daily, weekly or monthly re-crawls. Re-uploading a file adds a new source rather than re-indexing the old one, so remove the outdated file when you upload its replacement. Answer Gaps shows where users are asking about something your docs don't cover yet.
### Does it work in a React or Next.js app?
Yes. The widget installs with one script tag and follows client-side route changes in single-page apps built with React, Next.js, Vue or anything else. There is no npm package or React component. A WordPress plugin, a Google Tag Manager template and Webflow and Wix apps cover marketing and docs sites.
### How is it different from Intercom Fin?
Fin is an AI agent inside Intercom's helpdesk, billed per resolution. Aivastark is an AI agent you can put in front of any helpdesk, on flat monthly plans with a permanent free plan, and tickets sync to Zendesk, Freshdesk, HubSpot, Salesforce or ClickUp. If you want one vendor for the helpdesk and the AI, Intercom is the more complete suite; our comparison page has sourced, dated pricing.
### What security controls does it have?
There is no SSO or SAML today. Every plan with a team has owner, admin and member roles, per-member section access and an activity log you can export. A DPA is available, and Aivastark doesn't train or fine-tune AI models on your data. Messages reach the AI model as written, so keep secrets out of your docs.
### How does pricing work for a SaaS team?
Flat monthly plans with a monthly credit allowance, priced in US dollars, and a permanent Free plan that answers from your docs. Paid plans never stop answering: past the allowance, extra usage bills at the plan's published overage rate. Tickets, tools and helpdesk sync start on Starter; verified signed-in users and scheduled re-crawls on Growth. Every paid plan starts with a 7-day trial.
## Related
- [Features](https://www.aivastark.com/features) — Every capability, with the plan it needs.
- [Chat widget](https://www.aivastark.com/integrations/chat-widget) — Install, styling and the signed-in user config.
- [Slack integration](https://www.aivastark.com/integrations/slack) — Alerts for handoffs and tickets, replies from the thread.
- [AI sales agent](https://www.aivastark.com/ai-sales-agent) — Lead capture, scoring and routing for trials and demos.
---
*Aivastark · https://www.aivastark.com · updated 2026-10-07*
This document is machine-readable documentation for AI assistants and search engines. The complete index is at https://www.aivastark.com/llms.txt and the full corpus at https://www.aivastark.com/llms-full.txt. The human-readable version of this page is https://www.aivastark.com/industries/saas.
Questions: support@aivastark.com · Security: security@aivastark.com