Rank #3 of 6 in AI Customer Support Agents
Copilot Labs, Inc. (dba Parahelp) · commercial
Access
Try itExperimental
See what an agent can do with Parahelp before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://docs.parahelp.com/llms.txt | head -6recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agent actions — stories about agent actions in this arenaAgent actionsevidence →
Stories about agent actions in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Channels languages — stories about channels languages in this arenaChannels languagesevidence →
Stories about channels languages in this arena
Escalation handoff — stories about escalation handoff in this arenaEscalation handoffevidence →
Stories about escalation handoff in this arena
Guardrails safety — stories about guardrails safety in this arenaGuardrails safetyevidence →
Stories about guardrails safety in this arena
Insights analytics — stories about insights analytics in this arenaInsights analyticsevidence →
Stories about insights analytics in this arena
Integrations platform — stories about integrations platform in this arenaIntegrations platformevidence →
Stories about integrations platform in this arena
Knowledge grounding — stories about knowledge grounding in this arenaKnowledge groundingevidence →
Stories about knowledge grounding in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing economics — stories about pricing economics in this arenaPricing economicsevidence →
Stories about pricing economics in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Resolution quality — stories about resolution quality in this arenaResolution qualityevidence →
Stories about resolution quality in this arena
Testing qa — stories about testing qa in this arenaTesting qaevidence →
Stories about testing qa in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Parahelp stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent actions — stories about agent actions in this arenaAgent actions
Stories about agent actions in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~7/10
unlocks → Webhooks · Official SDKs · Scoped API keys · Machine-readable spec · Versioning policy · Full data export
Subscribe to events via webhooks
—–
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
n/an/a
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~5/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓7/10
unlocks → MCP client
Operate the product with natural-language commands
✓7/10
Plug MCP servers into this product so it can use their tools
—–
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
✓8/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Channels languages — stories about channels languages in this arenaChannels languages
Stories about channels languages in this arena
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
~5/10
The agent supports customers in many languages, even where my knowledge base exists only in English
—–
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat
—–
Escalation handoff — stories about escalation handoff in this arenaEscalation handoff
Stories about escalation handoff in this arena
Guardrails safety — stories about guardrails safety in this arenaGuardrails safety
Stories about guardrails safety in this arena
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess
~4/10
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer
✓8/10
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
~6/10
Insights analytics — stories about insights analytics in this arenaInsights analytics
Stories about insights analytics in this arena
Integrations platform — stories about integrations platform in this arenaIntegrations platform
Stories about integrations platform in this arena
Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding
Stories about knowledge grounding in this arena
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads
~3/10
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions
~6/10
Every answer is grounded in my own content and shows which article or source it drew from
—0/10
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring
~5/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing economics — stories about pricing economics in this arenaPricing economics
Stories about pricing economics in this arena
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Resolution quality — stories about resolution quality in this arenaResolution quality
Stories about resolution quality in this arena
Answers use the customer's live data — plan, order status, account history — not just generic help articles
~6/10
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer
—–
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
~3/10
I control the agent's tone and brand voice, and it stays consistent across topics and languages
—–
Testing qa — stories about testing qa in this arenaTesting qa
Stories about testing qa in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 7/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 7/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 5/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | full | 8/10 | Cclaimed | |
The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways C Helpdesk | developer | Integrations platform — stories about integrations platform in this arenaIntegrations platform | 3 | full | 8/10 | Cclaimed | |
The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action C Actions | developer | Agent actions — stories about agent actions in this arenaAgent actions | 3 | full | 7/10 | Cclaimed | |
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring C Ingestion | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 3 | partial | 5/10 | Cclaimed | |
When the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselves C Handoff | support leader | Escalation handoff — stories about escalation handoff in this arenaEscalation handoff | 3 | partial | 5/10 | Cclaimed | |
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess C Hallucination | ai-native user | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 3 | partial | 4/10 | Cclaimed | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | partial | 4/10 | Cclaimed | |
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces C Resolution | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 3 | partial | 3/10 | Cclaimed | |
Every answer is grounded in my own content and shows which article or source it drew from C Grounding | ai-native user | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 3 | none | 0/10 | ||
Dashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec team C Analytics | support leader | Insights analytics — stories about insights analytics in this arenaInsights analytics | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
I test the agent against historical tickets or simulated conversations before it faces real customers C Simulation | support ops lead | Testing qa — stories about testing qa in this arenaTesting qa | 2 | full | 8/10 | Cclaimed | |
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer C Supervision | support ops lead | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 2 | full | 8/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | full | 8/10 | Cclaimed | |
Answers use the customer's live data — plan, order status, account history — not just generic help articles C Personalization | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 2 | partial | 6/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 6/10 | Cclaimed | |
I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys C Rules | support ops lead | Escalation handoff — stories about escalation handoff in this arenaEscalation handoff | 2 | partial | 6/10 | Cclaimed | |
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching C Procedures | support ops lead | Agent actions — stories about agent actions in this arenaAgent actions | 2 | partial | 6/10 | Cclaimed | |
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them C Topic controls | support ops lead | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social C Channels | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | partial | 5/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 4/10 | Cclaimed | |
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads C Freshness | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 2 | partial | 3/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Pricing is outcome-based and published — I pay per resolution with caps and controls, not an opaque enterprise quote G Pricing | support leader | Pricing economics — stories about pricing economics in this arenaPricing economics | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer C Reasoning | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 2 | none | untested | none yet | |
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat C Voice | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | none | untested | none yet | |
The agent supports customers in many languages, even where my knowledge base exists only in English C Languages | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | none | untested | none yet | |
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions C Gaps | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 1 | partial | 6/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 6/10 | Cclaimed | |
AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent C Qa | support ops lead | Testing qa — stories about testing qa in this arenaTesting qa | 1 | partial | 5/10 | Cclaimed | |
I control the agent's tone and brand voice, and it stays consistent across topics and languages C Voice | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 1 | none | untested | none yet | |
The platform clusters conversations by topic and surfaces emerging product issues before they spike ticket volume C Insights | support leader | Insights analytics — stories about insights analytics in this arenaInsights analytics | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 39 stories with headroom
What would move Parahelp’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Missing: any reference to MCP protocol, MCP server connection, or standardized tool-plugin interface.
Knowledge grounding — stories about knowledge grounding in this arenaEvery answer is grounded in my own content and shows which article or source it drew from
nonemoves PA Scoreimpact 30
Missing: any documentation of per-answer source citation or attribution UI, evidence of end-user-facing 'grounded in X article' display.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
No evidence of any data export functionality, open-format export, or account-closure/data-portability capability in the docs or probes; the material covers agent configuration, tools, and integrations but nothing about exporting user/knowledge data or leaving the platform with data intact.
Insights analytics — stories about insights analytics in this arenaDashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec team
nonemoves PA Scoreimpact 30
No evidence of any dashboard or reporting feature covering resolution rate, CSAT, handoff rate, or cost per resolution; the pack only covers agent configuration, guardrails, integrations, and API access, none of which mention analytics/metrics reporting for support leaders.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: any documentation of API key scoping, credential minting, or permission-limited tokens issued to an agent.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Parahelp documents a customer-facing API and webhook/automation triggers, but no evidence anywhere mentions official client SDKs (Python, JS, etc.); the OpenAPI/swagger probe also 404s across all candidate paths, suggesting no machine-readable spec for SDK generation either.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
Missing: any mention of webhook subscription/registration, event types, or push-notification mechanism.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
There is an API reference surface (app.parahelp.com/api/docs) and docs are agent-legible, but no evidence shows an interactive reference with runnable examples (e.g.
Showing the top 8 of 39 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map9 surfaces · 31 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Customer agent docs22 stories
- The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action
- I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Operate the product with natural-language commands
- Define rules that trigger actions automatically on events
- Version, review, and roll back my automations
- One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
- When the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselves
- I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys
- Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess
- Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer
- I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads
- The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions
- The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring
- Do everything through the API that I can do in the UI
- Answers use the customer's live data — plan, order status, account history — not just generic help articles
- The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
- AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent
Internal agent docs15 stories
- The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys
- Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer
- I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
- The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions
- AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent
- I test the agent against historical tickets or simulated conversations before it faces real customers
Resources docs13 stories
- The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Schedule recurring jobs or workflows
- One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
- I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys
- Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer
- I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- Do everything through the API that I can do in the UI
- The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
Platform docs10 stories
- Run the product headlessly / in CI for automation
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads
- Answers use the customer's live data — plan, order status, account history — not just generic help articles
docs.parahelp.com8 stories
- I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching
- Get AI-generated insights and suggestions from my data inside the product
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Perform bulk operations across many items at once
- Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads
- The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring
- I test the agent against historical tickets or simulated conversations before it faces real customers
API reference3 stories
Security docs3 stories
OpenAPI spec2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://docs.parahelp.com/llms.txt | head -6reproduced$ curl -s https://docs.parahelp.com/llms.txt | head -6 # Parahelp docs - [Introduction](https://docs.parahelp.com/get-started/introduction.md): Parahelp is the platform for building your AI support agent. - [Concepts](https://docs.parahelp.com/get-started/concepts.md): The core terms used across Parahelp. - [Quickstart](https://docs.parahelp.com/get-started/quickstart.md): You've completed the onboarding task, and your Customer Agent is built. Here's how to get your first ticket resolved and where to go from there. - [Introduction](https://docs.parahelp.com/customer-agent/introduction.md): Configurations are everything that shapes your Customer Agent.
$curl -s https://docs.parahelp.com/customer-agent/api.md | head -8reproduced$ curl -s https://docs.parahelp.com/customer-agent/api.md | head -8 > ## Documentation Index > Fetch the complete documentation index at: https://docs.parahelp.com/llms.txt > Use this file to discover all available pages before exploring further. # API > Run your Customer Agent outside a ticketing system, wherever you implement it.
$curl -sL https://app.parahelp.com/api/docs | head -c 400reproduced$ curl -sL https://app.parahelp.com/api/docs | head -c 400
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Parahelp API</title>
<link rel="shortcut icon" href="/favicon.ico">
<style>
@import url('https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=Geist+Mono:wght@400;500;600;700&display=swap');
:root {
--scalar-radius:
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
2 of 16 testable claims verified · 0 contradicted → integrity 13/100
20 distinct capability claims found in Parahelp’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
2
Verified
14
Unverified
0
Contradicted
15
Undersold
Verified (2)
“Customer requests can be handled purely via API instead of going through a ticketing system, using the same configs and guardrails”
Drive the product through a documented public APIpartialproof ↗
“Run the Internal Agent autonomously without approval waits, triggered from your own tools via API”
Run the product headlessly / in CI for automationpartialproof ↗
Unverified (15)
“Describe a support flow in plain language and the Internal Agent configures the policies, knowledge and tools for it”
Operate the product with natural-language commandsfullproof ↗
“Simulate agent behavior against historical tickets or mock scenarios, and run production tests to verify tool connections before launch”
I test the agent against historical tickets or simulated conversations before it faces real customersfullproof ↗
“Every agent action requires manual approval by default, with per-task/automation auto-approve overrides”
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customerfullproof ↗
“Configuration changes publish as trackable releases that can be reverted with one click”
“Automations can run on a schedule (e.g. every weekday 9am) or be triggered by external events like a GitHub PR merge”
“Automations can run on a schedule (e.g. every weekday 9am) or be triggered by external events like a GitHub PR merge”
Define rules that trigger actions automatically on eventsfullproof ↗
“Set conditional approval rules, e.g. requiring Slack approval before a refund tool executes above a dollar threshold”
I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeyspartialproof ↗
“Automatically transfer tickets to the right human team with a summary note based on account type”
When the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselvespartialproof ↗
“Enable auto-approve so the agent can perform any action through a connected tool without human sign-off”
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customerfullproof ↗
“Workspace admins can disable all personal data storage/retention on the platform”
“Tools can call any service with an API, whether a public integration like Stripe or an internal company endpoint”
The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per actionfullproof ↗
“Customer Agent operates as a team member inside Intercom, Zendesk, Front, Plain, or Pylon”
The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both waysfullproof ↗
“Pylon integration lets the agent resolve tickets across email, live chat, and Slack”
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, socialpartialproof ↗
“Automations can watch tools and the support queue and proactively surface gaps on their own”
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questionspartialproof ↗
“The Internal Agent analyzes your last 500-1000 resolved tickets plus existing context to auto-build the first version of your Customer Agent”
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoringpartialproof ↗
Undersold (15)
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branchingpartialproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundfullproof ↗
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guesspartialproof ↗
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on thempartialproof ↗
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploadspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Prevent my data from being used to train AI modelspartialproof ↗
Answers use the customer's live data — plan, order status, account history — not just generic help articlespartialproof ↗
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bouncespartialproof ↗
AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agentpartialproof ↗
Claims outside our story set (4)
Real capability claims found in Parahelp’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“View live knowledge base content and full version history, including who published what and a diff for every change”
source ↗“Role-based access control across the product”
source ↗“A tool connection is configured once and shared between both the Internal Agent and Customer Agent”
source ↗“Anyone, not just engineers, can build new tools for the Customer Agent”
source ↗
Business model
Credit-based usage pricing, published: Start $1.25/credit (min 800/mo), Scale $1/credit (min 4,000/mo), custom above 20K tickets; 1 credit per resolved ticket; 14-day no-cure-no-pay trial.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt up (tracking since Sep 11 '26)