Aivastark
Start free
AI support agent · SaaS and software

The AI support agent for SaaS that answers from your docs, at any hour

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.

Start free →See how it works

Free plan for answers from your docs · tickets, tools and helpdesk sync from Starter

Product specialist working at a laptop in a bright studio office

Acme Cloud support

AI agent · replies any hour

  1. How do I rotate an API key without downtime?

  2. You're on the Team plan, so you can keep two live keys: create the new one, deploy it, then revoke the old key.

    curl -X POST $ACME_API/v1/keys \  -H "Authorization: Bearer $KEY" \  -d '{"name":"production-2"}'

  3. Deployed it, but my webhook now returns 401.

  4. Webhook signatures use the key's own secret, so your endpoint needs the new one. I've opened a ticket so the team can check your delivery logs.

    Ticket #2187 · bug · high priority

Illustrative conversation in a fictional app. The plan comes from the signed-in user you pass to the widget (Growth); tickets and helpdesk sync need Starter.

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.

answers in your app and on your docs site
24/7answers in your app and on your docs site
examples in the reply, rendered in the widget
Codeexamples in the reply, rendered in the widget
languages your users can write in
80+languages your users can write in
plan to start, no card
Freeplan to start, no card
Every day in a SaaS inbox

What your users ask, answered in the app

Most support conversations at a software company are the same handful of questions: how do I, why is this failing, what does my plan include. The agent answers them from your own docs in the moment, and sends the real problems to your team with the details already collected.

  • “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.

Answer

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

    All plans

    Reads your sitemap and pages; up to 25 pages per source on Free, more on each plan above.

  • Files, FAQs and pasted text

    All plans

    PDF, Word (DOCX), TXT or Markdown: API references, changelogs, runbooks.

  • Refresh when you ship

    Starter+

    Refresh a source once a day on Starter; schedule daily, weekly or monthly re-crawls on Growth.

  • Answer gaps

    Starter+

    The questions your docs couldn't answer, with drafted answers to approve: 25 drafts a month on Starter, unlimited on Growth.

Knowledge base

Example
docs.acme.example212 pages indexed
help.acme.example64 articles indexed
api-reference.pdf38 pages indexed
changelog.md1 file indexed
Support FAQs48 answers indexed

docs.acme.example/api-keys

API keys authenticate requests to the Acme API.

Each workspace can hold up to two live keys.

Webhook payloads are signed with the secret of the key that created them.

To rotate without downtime, create a second key, deploy it, then revoke the first.

Used for the answer

Answer gap

“Do you support SCIM provisioning?” · asked 14 times

Draft answer ready to approve

Your team sees the passage behind each reply in the inbox; users see the answer.
Developers

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

    All plans

    Code blocks and inline code render in the widget, so a curl example keeps its formatting.

  • Your API reference as a source

    All plans

    Crawled as web pages or uploaded as files; there is no OpenAPI import.

  • 80+ languages

    All plans

    Replies in the language each user writes in; limit it to the ones your team supports.

  • Escalates what docs can't fix

    Starter+

    When the answer runs out, it opens a ticket or hands the user to an engineer with the thread attached.

Developer working late at a laptop with code on a second monitor

Acme Cloud support

Example

I keep getting 429s from /v1/events. What's the limit?

/v1/events allows 600 requests a minute per key. Back off on 429 using the Retry-After header:

const res = await fetch(`${BASE}/v1/events`, {  headers: { Authorization: `Bearer ${KEY}` },});if (res.status === 429) await retryAfter(res);
Context

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

    Growth+

    Name, email, plan, company and custom traits as context, with the user id verified by your HMAC signature.

  • Your MCP server

    Starter+

    Reads and actions through your own server, with the user's own token if you choose; writes need the user's confirmation.

  • API lookups

    Starter+

    GET endpoints you define, such as status or usage, called when a question needs them.

Smiling man at a laptop in a bright office

Signed-in user

id verified
id
u_4821
plan
Team
company
Northfield Labs
traits
seats: 12 · region: EU

Your MCP server

get_usage(workspace) · with the user's token

182,400 of 250,000 API calls used this month

Raise the limit to 500,000?

ConfirmCancel

Changes wait for the user to confirm.

Escalate

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

    Starter+

    Opened from the chat with a category and priority, timed against your SLA policy.

  • Helpdesk sync

    Starter+

    Zendesk, Freshdesk, HubSpot, Salesforce, ClickUp or a signed webhook; send only bugs, or only high priority.

  • Slack alerts and replies

    All plans

    Handoffs and tickets post to a Slack channel, and a reply in the thread reaches the user in the widget.

  • Human handoff

    Solo+

    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.

Escalation

Example
  1. ChatWebhook returns 401
  2. Ticket#2187 · bug · high
  3. Your helpdeskZendesk

#2187 Webhook 401 after key rotation

High
Category: bugUser: u_4821First response due in 3h 58m

Conversation attached. The user rotated a key and redeployed; webhook deliveries return 401 since.

Synced to Zendesk · alert posted in #support

Syncs to Zendesk, Freshdesk, HubSpot, Salesforce, ClickUp or a signed webhook (Starter).
Grow

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

    All plans

    Category, signals and a 0 to 100 score with the reasons listed.

  • Routing rules

    All plans

    “Hot demo requests go to Sam”: route by category, signal or band.

  • Lead webhook and HubSpot

    Solo+

    Each lead sent to your endpoint or HubSpot as it's captured, with retries.

  • Page and behaviour triggers

    Starter+

    Start a flow on a page visit, time on page, pages viewed, scroll depth or exit intent.

New lead

Example

86

Hot

Priya · Northfield Labs

“Can we get a demo for 40 seats before our renewal in March?”

demo requestbudget mentionedtimeline given

Rule “hot demo requests → Sam” · lead sent to your CRM

Category, signals and a 0 to 100 score, with the reasons listed. Routing rules send it on.
Your team

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

    All plans

    Website, email and messaging conversations in one list, with the agent's sources in a “Why?” drawer.

  • Roles and section access

    Starter+

    Owner, admin and member roles, per-member section access and an exportable activity log; 3 seats on Starter.

  • CSAT

    Starter+

    Users rate the conversation when it ends.

  • Several products

    Starter+

    A separate agent and knowledge base per product: 2 projects on Starter, 5 on Growth, 15 on Scale.

Four colleagues talking around a table with laptops in a bright office

Why did the agent say this?

  • docs.acme.example/api-keys · “create a second key, deploy it…”
  • docs.acme.example/webhooks · “signed with the key's secret”
Take over chat

Team

  • AnaOwner
  • LeoAdmin
  • MiraMember · Inbox, Tickets
How it works

In your app this afternoon

One script tag puts the agent in your app and on your docs site, and it follows route changes in single-page apps. Tell it who is signed in if you want plan-aware answers; everything else is configured in the dashboard.

  1. 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. 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. 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.

<script>
  window.AivastarkConfig = {
    key: "YOUR_WIDGET_KEY",
    // Optional: tell the agent who is signed in.
    getUser: async () => ({
      id: user.id,
      name: user.name,
      email: user.email,
      plan: user.plan,
      signature: user.aivastarkSignature, // from your server
    }),
  };
</script>
<script src="https://www.aivastark.com/widget.js" async></script>
The signature is an HMAC-SHA256 of the user id with your signing secret, computed on your server. Widget and identity reference
The real thing

Connect your tools, run the inbox

These are the actual screens: the Tools page where your MCP servers, API tools and helpdesk connect, and the inbox your team works from.

Aivastark Agent Tools page with Shopify, Google Calendar, Cal.com, Zendesk, Postgres and MCP server connections
Tools: MCP servers, API tools and Zendesk
Aivastark unified inbox showing conversations filtered by channel with the AI agent's replies
The inbox your team answers from
Know before you start

What it doesn't do

Evaluating an agent for a software product means knowing its edges. Aivastark has no SSO, no Linear, Jira or GitHub Issues integration, no OpenAPI import and no npm package, and it shows sources to your team rather than to users.

  • 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.

Compare

AI agent vs help center search and a ticket form

How an AI support agent compares with help center search and a ticket form for a SaaS product
For your usersHelp center searchTicket formAivastark
Answers the actual questionLists articles to readNext business dayIn the chat, from your docs
API questions with codeIf an article has itAn engineer replies laterCode examples in the reply
Knows the signed-in userNoFrom the email addressName, plan and traits you pass (Growth)
Bug reportsNoFree-text ticketsA bug ticket with priority, synced to your helpdesk (Starter)
Other time zonesSelf-serve onlyWaits for your teamAny hour, in 80+ languages
Shows what's missing from your docsSearches with no resultsOnly if someone tags itAnswer Gaps with drafted answers (Starter)
Hands off to a personNoIt is a personWith the whole thread (Solo)
Compare

Each page states plainly what the other product is better at, with sourced and dated pricing.

See every comparison Each one states what the other product is better at, with sourced and dated pricing.

Product names and logos belong to their owners and are shown only to identify the products compared; no affiliation or endorsement is implied.

Plans

Which plan a SaaS team needs

Start free with answers from your docs. Solo adds a person to hand off to, Starter adds tickets, your tools and helpdesk sync, and Growth adds verified signed-in users and scheduled docs refresh. Every paid plan starts with a 7-day trial.

  1. Free

    $0forever

    Answer from your docs

    • Widget on your app and docs
    • Docs crawl, files and FAQs
    • 80+ languages
    • Lead capture and scoring

  2. Solo

    $12/month

    Bring a person in

    • Human handoff
    • Email alerts with a summary
    • Lead webhook and HubSpot

  3. Starter

    Most SaaS teams

    $39/month

    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

  4. Growth

    $129/month

    Signed-in users and scheduled refresh

    • Verified signed-in users
    • Scheduled docs re-crawl
    • Unlimited Answer Gap drafts
    • 5 projects, 5 seats

Every self-serve plan: Free $0 · Solo $12/mo · Starter $39/mo · Growth $129/mo · Scale $319/mo. Paid plans bill overage past their monthly credits instead of stopping.

Compare every plan
FAQ

Questions SaaS teams ask

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.

Let your docs answer at 3am. Let your team handle the rest.

  • Free plan, no card
  • 7-day trial on paid plans
  • One script tag
Start free →See every feature