Introduction
Airhop is the AI customer success agent that onboards, answers, and retains every account.
Airhop is an AI agent, not a chatbot. It onboards every account, answers from your real docs, watches health, and reaches out at the right moment. It decides the next move per account and loops in your team only when it counts.
Most support tools wait for a ticket. Airhop works the whole account: it answers questions in your widget, by email, and in Slack; it watches product usage and account health; and it acts across the customer lifecycle, pulling in a human before a renewal slips.
What Airhop does
Answers from your knowledge
Grounded replies from your help center, docs, and past tickets, with the sources shown. When it is not sure, it hands the thread to a human with full context.
Onboards every new account
Watches product events, tracks activation milestones, and nudges users toward their first real win so nobody stalls in week one.
Watches health and retention
Folds usage, sentiment, and call notes into one health read per account and surfaces the ones slipping while there is still time.
Acts across channels
Reaches out in the widget and by email, within guardrails like cooldowns and a weekly frequency cap so it stays helpful, never spammy.
Who it is for
Airhop is built for SMB and product-led teams who want support and customer success handled by one agent: the people answering questions, onboarding new accounts, and trying to keep customers from churning, without building a stack of separate tools.
How the pieces fit
There are three things you give Airhop, and it does the rest:
- Your knowledge. Point it at your help center URL and it crawls and indexes the pages so it can answer from them. See Connect your knowledge.
- The widget. One script tag puts the chat widget on your site or app, themed to your brand and aware of who the logged-in user is. See Install the widget.
- Product events. A few
identifyandtrackcalls tell Airhop who your users are and what they do. This is what powers activation, health, and retention. See Send product events.
From there, accounts and health, playbooks and triggers, and human handover build on the same data.