Parahelp

What it is

Parahelp is an AI support agent that sits on top of the help desk you already run and resolves tickets end to end: it reads the ticket, follows your written procedures, calls your internal tools through their APIs, and either closes the ticket or hands it to a human with the context attached. It is built for software companies whose tickets are technical and account-specific — a failed deploy, a billing dispute, a usage-limit question that needs a look at the customer’s actual account — rather than questions a help-center article answers.

The company was founded in 2024 by Danish founders Anker Bach Ryhl and Mads Lunau Liechti, went through Y Combinator, and is based in San Francisco. It announced $21.2M on 2025-09-11: a $3.2M seed led by Blake Robbins at Hidden Capital and an $18M Series A led by Jack Altman at Alt Capital, with Hanabi, Y Combinator, Perplexity Fund, ByFounders and Skyfall participating. The public customer list is almost entirely AI and developer-tool companies: Perplexity, Replit, HeyGen, Framer, Bolt, Photoroom and Cursor, with Kit and Fyxer on the current homepage.

Two agents ship. The Customer Agent handles the conversation across email, live chat and Slack. The Internal Agent (launched as “AI Manager”) is how your team builds and tunes the Customer Agent: you tell it in plain language to change a procedure, it tests the change against old tickets and simulated scenarios, and it reports what moved.

Why it shows up in dev-tool support stacks

• It bills only on fully resolved tickets. A ticket the agent escalates to a human costs nothing. That is the same meter Intercom Fin and Lorikeet use and the opposite of per-conversation billing, which charges the failures at the same rate as the wins.
• It does not replace your help desk. It runs on Zendesk, Intercom, Front, Plain and Pylon, so there is no migration project and your human agents keep their queue, macros and reporting.
• Tool access is open-ended. Anything with an API can be connected — Stripe for refunds and plan changes, Linear to file a bug with the reproduction steps, internal admin endpoints for account lookups. That is what lets it close a “why was I charged twice” ticket instead of quoting the refund policy.
• Configuration is a conversation, not a flow builder. Procedures are written as SOPs in plain language and the Internal Agent turns edits into tested changes. Parahelp claims setup in one day with no engineers; plan for longer if your tools need new API scopes.
• The security basics are on the page. SOC 2 Type II audited, GDPR compliant, and a stated commitment not to train models on customer data.

Pricing reality

Parahelp publishes its rates, which puts it with Lorikeet and Fin and apart from Decagon and Sierra.

• Start — $1,000/month, for teams under 3,000 tickets a month. $1.25 per resolved ticket.
• Scale — $4,000/month, for 3,000–20,000 tickets a month. $1.00 per resolved ticket, plus SSO/SAML, role-based access and priority support.
• Custom — 20,000+ tickets a month, negotiated per-ticket rate, custom SLAs.
• Internal Agent — billed separately on every tier at model token usage plus 20%.
• Trial — 14 days, “no-cure-no-pay”.

Third-party pricing breakdowns read the monthly figure as a prepaid credit minimum, one credit per resolved ticket: $1,000 buys 800 resolutions on Start, $4,000 buys 4,000 on Scale. On that reading, Start is priced for teams resolving at least 800 tickets a month; below that, you pay for resolutions you did not get.

Against the per-unit market, Parahelp sits at the top of the published band. Fin charges $0.99 per outcome with a 50-per-month minimum; Lorikeet $0.80–$0.95 for chat and email; eesel AI $0.40 per ticket handled, whatever the outcome. It undercuts Zendesk’s roughly $1.50 per committed automated resolution. And the help desk subscription stays on the invoice: at 2,000 resolutions a month, Parahelp Start costs about $2,500 before the Internal Agent’s token bill, on top of whatever you already pay Zendesk or Intercom per seat.

Best for

Support leads at developer-tool, AI and PLG software companies doing roughly 1,000–20,000 tickets a month, whose ticket mix is technical and account-specific, whose support team is small relative to its user base, and who want an agent on their existing Zendesk, Intercom, Front, Plain or Pylon desk rather than a new help desk. It fits best where most tickets need an action in Stripe or an internal admin tool to close.

Skip it if your tickets are mostly answerable from docs, where a cheaper deflection agent resolves the same volume for less; if you need voice, which Parahelp does not list; or if you are a B2C or regulated-industry support organization, where the customer references and compliance depth are thin.

Versus the alternatives

The market-share leaders are the AI layers of the desks you already own. Intercom Fin is the pick when you run Intercom and most tickets are answerable: $0.99 per outcome, no new vendor, and the lower price per resolution. Zendesk AI is the pick when procurement will not add a vendor and you already pay for Zendesk Suite. Choose Parahelp over both when a large share of tickets needs a tool call to close and the native agents stall there.

The fastest-growing entrant is Sierra, which raised $950M in May 2026 at a $15.8B valuation; pick it when you need voice and enterprise transaction workflows and can fund a $150K+ annual contract. Decagon is the enterprise alternative above roughly 10,000 monthly resolutions, where a negotiated rate beats $1.00 despite its ~$50,000 platform fee. Lorikeet is the closest like-for-like on published per-resolution pricing and cheaper per ticket; pick it for fintech or healthtech workflows and voice, Parahelp for developer-tool support run from Slack and email. eesel AI wins on cost when your resolution rate is high and you are testing the category.

If none fit, keep humans on the technical queue and run Fin or eesel on the FAQ tier only. An agent needs documented procedures and API access to close tickets; without them, any vendor on this list will escalate most of the queue.

Watch-outs

• The monthly figure and the per-ticket rate are published without saying how they combine. Read as a credit minimum, a slow month wastes credits; read as a platform fee, every resolution costs $1.25 on top of $1,000. Guard: get the definition of the $1,000/$4,000 figure, credit rollover and overage rate into the order form, and model the bill on your lowest-volume month of the last year.
• “Fully resolved” is the whole commercial model and the page does not define it. A ticket closed by the agent and reopened two days later can be billed as a resolution. Guard: agree a reopen window (7 days is a reasonable ask) that voids the charge, and track your own reopen rate from the help desk rather than the vendor dashboard.
• The Internal Agent is a second, open-ended meter. Token usage plus 20% scales with how much your team iterates, not with ticket volume. Guard: ask for last quarter’s Internal Agent spend on a customer of your size, and set a monthly cap in the contract.
• Small vendor, narrow reference base. The public customers are nearly all AI and developer-tool companies, and the company has raised $21.2M in a category where Sierra raised $950M this year. Guard: request the SOC 2 Type II report before signing, keep your SOPs in your own repository rather than only in Parahelp, and confirm transcripts and procedure exports in the agreement so you can switch in weeks, not months.