- Signal: Timeline identified · High
- Next step accepted: confirm Okta before renewal
- HLP-142 created from the conversation
- Task planner scoped the work
- Code builder opened PR #318
- Waiting for approval
- Review agent: checks passed
- Merged by Sam
Where SaaS teams answer customers, ship fixes, and close deals.
Helpin puts your support inbox, help center, project tracker, and CRM on one customer record. AI agents draft replies, plan work, and open pull requests inside it, and ask before they act.
Audience-first headline. "SaaS teams" is the subject; the three verbs map to support and docs, projects, and CRM. The frame is a placeholder for the real company page in the seeded workspace.
Wire concept. One line, four stages on the page grid, one customer. The line draws left to right, each stage hangs its artifact off it, and the work inside Decide and Ship ticks off item by item. The approval moment is explicit in Ship: the run waits, an Approve pill appears, then "Approved by Sam." About ten seconds, plays once, finished state under reduced motion, vertical on phones. Every intermediate state is readable text; nothing overlaps mid-transition.
Order: the wire comes first, then the headline and description, so the story plays while the reader arrives at the sentence that names them. The animated customer record is the visual for section two and starts when scrolled into view.
DECISION "View on GitHub" assumes the repository and a release bundle are public. CLOUD Until the Community module decision, this frame shows Cloud.
One record per customer. Support, product, and sales read the same one.
In a SaaS company of ten or forty people, the same customer talks to support on Tuesday, comes up in the roadmap meeting on Wednesday, and renews on Friday. Most tools keep three versions of that story. Helpin keeps one, and everything that happens attaches to it.
What lands on the record:
Website chat and email, in a shared inbox with assignment, notes, tags, and saved replies.
A notetaker joins Google Meet, Zoom, Teams, or Webex. You get the recording, a speaker-attributed transcript, a summary, decisions, objections, and next steps.
Pipelines and stages, with buyer signals detected from email, meetings, and support, each linked to its source.
Created from a conversation, a meeting action item, or a plan. Linked back to whatever started them.
Help-center articles and internal documents, including the ones a customer was sent and the ones their questions produced.
Gmail and calendar sync put the thread and the appointment on the same timeline.
CONFIRMED Meeting intelligence fields, Recall.ai and Vexa providers, Meet, Zoom, Teams, Webex; Gmail and calendar sync; associations across conversation, task, deal, contact, company. VERIFY Whether "calls" has its own capture path; whether "Emails" covers support email as well as Gmail-synced sales email.
One customer, start to finish.
This is the loop Helpin is built around. Here it is with one account and one week.
Hear
Everything the customer says, wherever they say it.
1. Send Okta SAML mapping steps
2. Security sign-off by the 30th
The meeting and the chat land on the same record. The renewal signal and the support question are one story before anyone connects them by hand.
Decide
What needs attention, and the next step.
A person accepts the next step. The task is drafted from the conversation with the context attached, and it links back to the chat, the meeting, and the deal.
Ship
From task to pull request, with a person approving.
HLP-142-okta-saml-mapping
Agents do the work you hand them. The task planner scopes it, the code builder opens the PR, the review agent checks it. Your team approves the request and merges.
Tell
The answer goes back out, and into the docs.
The gap becomes an article, the article answers the next customer. Maya gets a reply with its source. The renewal signal closes when the deal does.
One account, one week, five tools' worth of work, in one record. Nobody copied anything between systems, and the help center is one article better.
Four verbs, seven frames, one customer. Also the script for the recorded demo. Capture every frame from the seeded workspace.
CAREFUL Meeting action items become tasks only after a person accepts them. The PR is merged by a person. Deal stage changes are human actions unless deal automation is on (Growth). CLOUD Decide and Ship need PM and CRM, which are not in Community 0.1.
You decide when the AI acts.
In support, the agent has three settings. Most teams start at private notes and move up once the drafts have earned it. Everywhere else, actions can be set to ask first.
People reply. AI only helps with search and rewriting drafts.
AI drafts a reply as an internal note on each new conversation. Your team edits and sends.
AI answers when it finds a confident match. Everything else waits for a person.
A customer can ask for a person at any time. When the team is busy or offline, conversations queue instead of stalling.
Any agent can be set to request approval before it runs a command, changes files, or takes an action. The request appears where you are working.
Runs stream live. You see the steps and the reasoning as they happen, and you can reply mid-run when the agent needs a decision.
Each AI draft shows the article it used. If it used nothing, the question is logged as a gap.
Anthropic, OpenAI, or OpenRouter. Change the model per agent. Community uses only the keys you connect.
CONFIRMED Support modes off / internal note / AI-first; escalation and handoff states; approval, review-checkpoint, and user-input interactions with a pending-interaction card; live streaming of run segments and reasoning; providers Anthropic, OpenAI, OpenRouter. VERIFY Exact wording of the paused-run card.
Ten agents with a job each. Rules that run them.
Every agent runs on the same runtime and sees the same record. Pick one, give it a target, and choose whether it asks first.
Build your own: choose tools, targets, schedule, and approval mode. Growth
When this happens, do that.
Triggers from tasks, pull requests, releases, published docs, approvals, or a schedule. Actions that run an agent, move a task, merge a branch, or run a command.
Team: Product · stop on match
Only if the description mentions a customer
Cron · requires approval before publishing
Conditions can be written in plain language. Automations are included on Growth.
CONFIRMED Ten presets plus researcher; custom agents gated by entitlement. Triggers, actions, ordering, stop-on-match, natural-language conditions, automation_flows entitlement. VERIFY One-line job descriptions against each preset's prompt and tools; replace the example rules with rules from the seeded workspace.
Run it yourself, or let us.
The Community edition is the same product on your own servers. It's open source because the record of what your customers said and what you did about it should be yours to keep.
The application is AGPL-3.0-only. The JavaScript SDK and widget are Apache-2.0, so embedding them in your product carries no copyleft obligation.
Conversations, deals, tasks, articles, transcripts, and AI credentials live in your Postgres and your object storage.
Community has no managed AI route and no AI billing. Connect Anthropic, OpenAI, or OpenRouter and pay your provider directly.
No telemetry, no Helpin account required, and the support widget sends no analytics events to us.
One bundle with Postgres, Redis, NATS, Temporal, and object storage. Backup, restore, and public-deployment guides included.
| Community, self-hosted | Cloud | |
|---|---|---|
| Price | Free, AGPL-3.0 | From $99/month, unlimited seats |
| Chat, inbox, help center, AI agents | Included | Included |
| Projects and CRM | Included pending decision | Included |
| Meeting notetaker | To decide pending decision | Included |
| AI model keys | Bring your own | Included allowance, or bring your own |
| Hosting, upgrades, backups | You | Us |
| Support | Community, best effort | Priority on Growth |
Community 0.1 ships support, docs, and agents and is a beta. Read the scope and known limitations before serving production traffic.
DECISION Projects and CRM in Community; meeting notetaker in Community (it needs a Recall.ai or Vexa account). CONFIRMED License scopes; BYOK-only Community; no telemetry; Compose bundle contents; no Helm chart. VERIFY Which Growth entitlements are ungated on a self-hosted install.
Built to be run, extended, and worked on by agents.
Install
curl -fsSL https://helpin.ai/install.sh | bash
helpin install
# or, from a downloaded bundle:
./setup.sh install · edit .env · ./setup.sh startA guided installer that checks Docker, verifies the bundle, generates secrets, and starts the services. Linux or macOS, Docker Engine, Compose v2, 8 GB RAM and 20 GB disk to evaluate.
MCP, both directions
Connect Claude Code, Codex, or any MCP client to your workspace over OAuth 2.1, with scoped tools and workspace permissions re-checked on every call. Give your own agents external MCP servers too, with Linear, Sentry, and Customer.io presets, each run on a short-lived credential.
Git, SDK, runtime
GitHub App and GitLab integration with branch templates and PR status on the task. Apache-2.0 JavaScript SDK with React, Vue, and Next.js packages. Agent runs on the native runtime, Codex, or OpenCode.
CONFIRMED A CLI at community/cli with install, status, logs, and doctor; the curl bootstrap requires a published Community release with CLI assets. MCP server at /mcp with OAuth 2.1; external MCP connections in Settings; GitHub App and GitLab; runtime kinds native, codex, opencode. BLOCKER Source builds still need the private agent-runtime repository; no release bundle is confirmed.
Built by a team that runs support, sales, and product on it.
Helpin is made by the team behind ContentStudio, ContentPen, and Usermaven. We built it for our own customer queues and our own roadmap first, and we publish what works and what doesn't, in the open.
Products from the same company. Not third-party customers.
“[Real pilot quote goes here. One sentence about the before, one about the after, with a measurable change if the customer agrees to it.]”
Name, role, company — with written approvalVERIFY That the named products run support, sales, or product work in Helpin today. NEEDS EVIDENCE No testimonial or metric exists yet; keep the placeholder until a pilot yields one.
Free to run yourself. One price per workspace to let us.
Community
- Chat, inbox, help center, AI agents
- Projects and CRM pending decision
- Your own model keys
- AGPL-3.0, no telemetry
Starter
- Unlimited seats
- Every module included
- Standard AI allowance
- Help center on your domain, GitHub integration
Growth
- Everything in Starter
- 3× AI allowance
- Custom agents, automations, scheduling, AI routing
- Remove branding, priority support
14-day Growth trial, no card required. Annual billing is 20% less. Full plan details.
CONFIRMED Prices, unlimited seats, trial, annual discount; Growth entitlements. DROP "SLA management" and PM "custom fields" from the live matrix. VERIFY Meeting notetaker availability by plan; desktop and mobile apps are at beta stage and stay off the page.
Before you decide.
Will the AI do things without my team seeing?
In support, only in "AI replies first" mode, and only with a confident match in your published articles. Elsewhere, any agent can be set to ask before it runs a command, changes files, or takes an action, and the request appears where you are working. We recommend starting with approvals on.
How do meetings get in?
A notetaker joins your Google Meet, Zoom, Teams, or Webex call. Afterwards the meeting sits on the customer's record with the recording, a transcript, a summary, decisions, objections, and next steps. Action items become tasks when a person accepts them.
Which AI models can I use?
Anthropic, OpenAI, or OpenRouter, which routes to Gemini and other models. Community uses only the keys you connect. Cloud includes a monthly allowance and lets you connect your own keys as well.
What is in the open-source edition?
Website chat, the shared inbox, email support, the public help center, and AI agents on your own keys. Projects and CRM are being added to Community; the edition table above shows the current state.
Can I move from Intercom, Linear, or HubSpot?
Today Helpin imports help-center content from Help Scout and Nextra, projects from Shortcut, and contacts from CSV. There is no Intercom, Linear, or HubSpot importer yet. Tell us what you need to move and we'll say plainly whether we can help.
Does it replace GitHub or my editor?
No. Helpin connects to GitHub or GitLab, opens pull requests on your repositories, and shows PR status on the task. Claude Code, Codex, or any MCP client can work inside your Helpin workspace through the MCP server.
What do I need to self-host?
Docker Engine with Compose v2, Bash, OpenSSL, and an amd64 or arm64 host with about 8 GB of RAM and 20 GB of disk for evaluation. The install guide covers DNS, HTTPS, backups, and upgrades. There is no Kubernetes chart yet.
Is it ready for production?
Cloud is what we run our own products on. Community 0.1 is a beta with a published list of known limitations; read it before putting it in front of customers.
What is the license, exactly?
The application is AGPL-3.0-only. The SDK and widget packages are Apache-2.0. Code in enterprise directories, which covers billing and managed AI, is under a separate Helpin Enterprise License and is not needed to run Community.
DECISION The open-source answer says "being added"; change it to match whatever 0.2 ships. VERIFY "Cloud is what we run our own products on" needs the proof-section confirmation.
Start with one inbox, one repo, and one calendar.
Connect website chat, link a repository, invite the notetaker to one call, and turn on private notes. See the record fill itself in the first week.