Fin vs Parahelp

Actions

1. developerThe agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action

   weight 3 · round to Parahelp
   Fin~partialclaimed6/10

   Fin's Procedures feature explicitly supports multi-step business logic with third-party systems (refunds, order changes, etc. are common examples in docs like 'Takes action to update external systems' and Procedures training), and data connectors (Stripe, Shopify) plus MCP/API access enable real API calls. However, evidence does not detail per-action scoped authentication/authorization — no documentation on granular auth scoping per action, permission boundaries, or audit trails for individual API calls. missing for 10: explicit scoped-auth-per-action documentation, permission/authorization model for individual actions, and independent verification that real refunds/subscription updates are executed successfully in production.

   • [claimed-docs] “Takes action to update external systems”
   • [claimed-docs] “Building Fin Procedures”
   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”
   • [claimed-docs] “Data connector templates are now generally available, with ready-to-install templates across Stripe, Shopify and Statuspage.”
   • [claimed-docs] “The Fin API platform includes APIs for answer generation and knowledge retrieval, available as a set or independently.”
   • [claimed-docs] “give you the tools to safely deploy AI within your own boundaries.”

   proof ↗⚑ flag

   Parahelp✓fullclaimed7/10

   Docs show the agent executes real API actions (Stripe or internal endpoints) like refunds, with per-tool guardrails (e.g., Slack approval above $100), tool-level auto-approve settings, and role-based access control across the product. This covers real-action execution with approval/authorization gating per action, though evidence doesn't detail fine-grained per-action auth scoping (e.g., API-key/permission scoping distinct from approval workflows) beyond general RBAC mentions. Missing for 10: explicit documentation of per-action credential/auth scoping mechanics (vs. approval gates), and independent/hands-on verification of action execution in production.

   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “By default, every action requires manual approval. You can set specific tools to auto-approve per task or automation”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”
   • [claimed-docs] “Tools can use any service with an API: public integrations like Stripe, or your own internal endpoints.”
   • [claimed-docs] “Role-based access across the product.”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”

   proof ↗⚑ flag

Procedures

1. support ops leadI encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching

   weight 2 · round to Fin
   Fin✓fullclaimed8/10

   Fin has a dedicated "Building Fin Procedures" feature explicitly for encoding multi-step SOPs with business logic and branching, plus "Giving Fin Guidance" and escalation-rule configuration to control deterministic branching to humans or other steps, and a testing suite to validate procedures before launch. This directly matches the story of encoding SOPs with deterministic branching for known issue types. Missing for 10: independent hands-on verification of branching logic depth/determinism and more detail on how conditional branches are authored (docs are descriptive marketing/help-article summaries rather than technical specs).

   • [claimed-docs] “Building Fin Procedures”
   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”
   • [claimed-docs] “Giving Fin Guidance”
   • [claimed-docs] “Manage Fin AI Agent's escalation guidance and rules”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”
   • [claimed-docs] “Train Fin on your Procedures, knowledge, and policies, test performance before launch, deploy across every channel, then analyze and improve…”

   proof ↗⚑ flag

   Parahelp~partialclaimed6/10

   Parahelp lets ops encode conditional rules (e.g. 'if enterprise account, transfer with summary', 'if refund >$100, require Slack approval') and lets the Internal Agent configure task flows from natural-language descriptions of policies/tools, which supports rule-based branching for known issue types. However, there's no evidence of an explicit step-by-step SOP builder or visual decision-tree/flowchart for deterministic multi-step branching beyond simple guardrail conditions. Missing for 10: explicit multi-step SOP/workflow authoring UI, evidence of complex nested/deterministic branching logic beyond single-condition guardrails, and independent validation of branching behavior in production.

   • [claimed-docs] “Describe the flow you want in natural language - the policies, knowledge, and tool connections it combines - and the Internal Agent configur…”
   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “When a ticket is about an enterprise account, transfer it to the enterprise team with a summary note.”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Parahelp
   Fin✓fullprobed8/10

   A live probe confirms Fin publishes an llms.txt file at https://fin.ai/llms.txt (HTTP 200) explicitly framed to help LLMs understand its content structure, and Fin also offers an MCP server and a CLI agents can be pointed at for setup. Missing for 10: markdown-doc mirrors (docs-md probe 404) and a discoverable OpenAPI spec (all candidates 404), which would round out agent-friendly documentation.

   • [probe] “PROBE llms.txt: HTTP 200 at https://fin.ai/llms.txt # Fin — llms.txt > This file helps large language models (LLMs) understand the content …”
   • [claimed-docs] “Point your AI coding Agent at the Fin CLI to set up Fin on your website and configure your Intercom helpdesk — all without leaving your codi…”
   • [probe] “official MCP server documented at https://developers.intercom.com/docs/guides/mcp”
   • [probe] “PROBE docs-md: HTTP 404 at https://fin.ai/help/en/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fin.ai/openapi.json, https://fin.ai/swagger.json, https://fin.ai/api/openapi.json, https://f…”

   proof ↗⚑ flag

   Parahelp✓fullprobed9/10

   Direct probe evidence confirms Parahelp's docs serve a working llms.txt (HTTP 200) and per-page .md mirrors via Mintlify, making the docs agent-legible and directly consumable by an AI agent. Missing for 10: no independent third-party report of an agent actually consuming this llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.parahelp.com/llms.txt # Parahelp docs - [Introduction](https://docs.parahelp.com/get-started/intro…”
   • [probe] “PROBE runtime (recorded 2026-09-10): Parahelp's docs are agent-legible (Mintlify) — https://docs.parahelp.com/llms.txt serves '# Parahelp do…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Parahelp
   Fin~partialclaimed6/10

   Fin exposes a programmatic Agent API and Node/TypeScript SDK (intercom-fin-docs-3, intercom-fin-gh-3) that allows calling Fin from external code/services, which supports headless/CI-style automation, and webhooks (intercom-fin-docs-6) enable event-driven automation without a UI. However, there is no documented CI-specific tooling (e.g., a CLI test runner, GitHub Action, or exit-code-based automation harness) and the orchestration endpoints needed for autonomous agent-style headless runs are only in a Preview API (intercom-fin-docs-4). missing for 10: dedicated CI/CD integration or GitHub Action, documented headless test/run mode with exit codes, independent confirmation of automation reliability outside preview APIs.

   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”
   • [claimed-docs] “Webhooks allow you to subscribe to real-time notifications of events happening in Intercom; a Contact created, an incoming Conversation rece…”
   • [github] “The Intercom TypeScript library provides convenient access to the Intercom APIs from TypeScript.”

   proof ↗⚑ flag

   Parahelp~partialprobed7/10

   Parahelp exposes a documented API for triggering agent actions programmatically, supports auto-approve mode to bypass manual gating, and automations can run on schedules or triggers like a GitHub PR merge — all consistent with headless/CI-style automation. However, there's no explicit CLI, CI-pipeline example, or SDK documentation, and no independent/hands-on confirmation of running it in a real CI environment. Missing for 10: dedicated CLI or CI-integration docs, and third-party confirmation of headless automation in production.

   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system.”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public API reference at https://app.parahelp.com/api/docs is reachable keylessly — no login wall in…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Fin
   Fin✓fullclaimed7/10

   Fin's own docs state it 'works through MCP or API Data Connectors for your business tools' (docs-40/54) and explicitly describe connecting the 'Zapier MCP connector to Fin' (intdir-3), confirming Fin can consume external MCP servers as tools. Missing for 10: independent/hands-on verification of MCP tool usage in production and a broader list of supported MCP servers beyond the Zapier example.

   • [claimed-docs] “It works through MCP or API Data Connectors for your business tools, integrations with Intercom or your existing helpdesk”
   • [claimed-docs] “It works through MCP or API Data Connectors for your business tools, integrations with Intercom or your existing helpdesk, and native suppor…”
   • [claimed-docs] “Connect the Zapier MCP connector to Fin Manage workspace owners”
   • [claimed-docs] “Learn how to use the Model Context Protocol (MCP) to enable AI agents to securely access and interact with your Intercom data whenever helpf…”
   • [claimed-docs] “MCP is a protocol that enables AI tools and applications to securely access and interact with your Intercom data whenever helpful.”

   proof ↗⚑ flag

   Parahelp—none0/10

   Parahelp's tools connect via its own APIs and integrations (Stripe, internal endpoints, ticketing systems) but there is no mention of MCP server support or the ability to plug in MCP servers so the agent can use their tools. Missing for 10: any reference to MCP protocol, MCP server connection, or standardized tool-plugin interface.

   ⚑ flag

4. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Fin~partialprobed7/10

   Fin ships a documented Fin Agent API and an official TypeScript SDK (intercom-node) with concrete usage examples, plus a separate API platform for answer generation/knowledge retrieval, giving AI-native users a real programmatic path to drive Fin. However, key orchestration endpoints (Discover capabilities, Ask Fin, Run a procedure, Escalate) are only in Preview API version, and automated probes found no discoverable OpenAPI/swagger spec, suggesting the public API surface is not fully standardized/discoverable yet. Missing for 10: stable (non-preview) orchestration endpoints, a machine-readable OpenAPI spec, and independent hands-on developer corroboration beyond vendor docs/SDK repo.

   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”
   • [claimed-docs] “The Fin API platform includes APIs for answer generation and knowledge retrieval, available as a set or independently.”
   • [claimed-docs] “Build world-class customer experiences, agents, and products with the best-performing models for customer service.”
   • [github] “await client.aiContent.createContentImportSource({ url: "https://www.example.com" });”
   • [github] “List endpoints are paginated. The SDK provides an iterator so that you can simply loop over the items”
   • [github] “The Intercom TypeScript library provides convenient access to the Intercom APIs from TypeScript.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fin.ai/openapi.json, https://fin.ai/swagger.json, https://fin.ai/api/openapi.json, https://f…”

   proof ↗⚑ flag

   Parahelp~partialprobed7/10

   Docs explicitly describe driving both the Internal Agent and Customer Agent via API (ticket-free API intake, automation triggers, run-without-approval via API), and a runtime probe confirms a public API reference is reachable keylessly at app.parahelp.com/api/docs. However, standard OpenAPI/swagger spec endpoints all 404, so there's no machine-readable spec confirmed, only prose docs and a reference UI. Missing for 10: a confirmed OpenAPI/swagger spec, and independent hands-on confirmation of actually calling the API successfully.

   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system.”
   • [claimed-docs] “run it from your own tools via the API”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public API reference at https://app.parahelp.com/api/docs is reachable keylessly — no login wall in…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.parahelp.com/openapi.json, https://docs.parahelp.com/swagger.json, https://docs.parahel…”

   proof ↗⚑ flag

5. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Fin—none0/10

   Evidence covers API access, MCP, webhooks, and integrations, but there is no mention of scoped or least-privilege API credential/token issuance for agents (e.g., granular permission scopes, per-agent API keys). Absence of evidence for an applicable capability yields 'none'. missing for 10: scoped/least-privilege credential issuance, API key/token permission granularity, agent-specific credential management docs.

   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “Learn how to use the Model Context Protocol (MCP) to enable AI agents to securely access and interact with your Intercom data whenever helpf…”
   • [claimed-docs] “MCP is a protocol that enables AI tools and applications to securely access and interact with your Intercom data whenever helpful.”

   proof ↗⚑ flag

   Parahelp—none0/10

   Parahelp documents role-based access control, approval guardrails per-tool, and API access for triggering agents, but no evidence describes issuing scoped or least-privilege API credentials/keys specifically for an agent's tool access. Missing for 10: any documentation of API key scoping, credential minting, or permission-limited tokens issued to an agent.

   • [claimed-docs] “Role-based access across the product.”
   • [claimed-docs] “By default, every action requires manual approval. You can set specific tools to auto-approve per task or automation”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round to Fin
   Fin~partialprobed6/10

   Intercom publishes an official TypeScript/Node SDK (intercom-node) with convenient API access and iterator support, plus a documented Fin Agent API and API platform for programmatic use. However, only one official SDK language is evidenced, there's no public OpenAPI spec (probe returned 404s across all candidate paths), and no independent corroboration of SDK quality/adoption exists. Missing for 10: multi-language SDK coverage, publicly discoverable OpenAPI/schema, and third-party validation of SDK reliability.

   • [github] “await client.aiContent.createContentImportSource({ url: "https://www.example.com" });”
   • [github] “List endpoints are paginated. The SDK provides an iterator so that you can simply loop over the items”
   • [github] “The Intercom TypeScript library provides convenient access to the Intercom APIs from TypeScript.”
   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “The Fin API platform includes APIs for answer generation and knowledge retrieval, available as a set or independently.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fin.ai/openapi.json, https://fin.ai/swagger.json, https://fin.ai/api/openapi.json, https://f…”

   proof ↗⚑ flag

   Parahelp—none0/10

   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.

   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.parahelp.com/openapi.json, https://docs.parahelp.com/swagger.json, https://docs.parahel…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public API reference at https://app.parahelp.com/api/docs is reachable keylessly — no login wall in…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to Fin
   Fin✓fullclaimed8/10

   Intercom's developer docs explicitly document webhooks for subscribing to real-time event notifications (Contact created, Conversation received, Outbound Message receipt), directly matching the story. Missing for 10: independent/hands-on corroboration of webhook reliability and broader event coverage beyond the three examples cited.

   • [claimed-docs] “Webhooks allow you to subscribe to real-time notifications of events happening in Intercom; a Contact created, an incoming Conversation rece…”
   • [claimed-docs] “Webhooks allow you to subscribe to real-time notifications of events happening in Intercom”

   proof ↗⚑ flag

   Parahelp—none0/10

   No evidence pack item mentions webhooks or event subscriptions; Parahelp's automation/trigger docs reference schedules and GitHub PR merges but nothing about outbound webhook subscriptions for third-party consumption. missing for 10: any mention of webhook subscription/registration, event types, or push-notification mechanism.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Fin~partialclaimed6/10

   Fin's 'Insights', 'AI Recommendations', 'AI Topics', 'Trends', and CX Score features (docs-16, docs-47, docs-61) show it surfaces AI-generated analysis of conversation data, and 'Monitors'/'Custom AI Scorecards' extend this to proactive alerting. However this is framed around support-conversation analytics rather than a general 'insights from your data' experience, and there's no independent/hands-on validation of accuracy or usefulness of these AI-generated insights. missing for 10: independent corroboration of insight quality, broader data-source coverage beyond support conversations, concrete UI examples of AI-generated suggestions.

   • [claimed-docs] “Operator, CX Score, AI Topics, Trends, AI Recommendations, Monitors, Custom AI Scorecards, Incident Detection”
   • [claimed-docs] “Insights continuously analyzes every Fin and human conv”
   • [claimed-docs] “With Insights, Monitors New, and Recommendations, you have everything you need to understand, measure, and improve your customer experience”
   • [claimed-docs] “Train Fin on your Procedures, knowledge, and policies, test performance before launch, deploy across every channel, then analyze and improve…”

   proof ↗⚑ flag

   Parahelp~partialclaimed6/10

   Parahelp's Internal Agent generates insights from data: it analyzes historical tickets to auto-build a Customer Agent (docs-19) and runs automations that surface gaps in tools/support queues on their own (docs-17). This is AI-generated insight/suggestion behavior tied to the user's own data, but it's narrowly scoped to ticket/gap analysis rather than a general-purpose insights feature across all product data. Missing for 10: a dedicated insights/analytics dashboard surfacing trends or recommendations beyond gap detection and agent bootstrapping, and independent/hands-on confirmation of insight quality.

   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”
   • [claimed-docs] “the Internal Agent analyzes your last 500-1,000 resolved tickets along with your existing context to build the first version of your Custome…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Parahelp
   Fin~partialcommunity6/10

   Fin's Procedures, Tasks, Workflows, and Proactive Outbound Suite are documented as letting Fin autonomously handle multi-step customer queries, business logic, and third-party system actions end-to-end without human intervention, and Fin resolves a majority of queries (76%) without agent involvement. However, evidence is entirely vendor marketing/help docs with no independent or hands-on confirmation of scheduling/background execution mechanics, and one community comment questions whether open-ended autonomous agent behavior is even desirable versus deterministic workflows. Missing for 10: independent verification of autonomous background execution, technical detail on triggers/scheduling for Procedures/Tasks, and hands-on confirmation that these run without ongoing human oversight.

   • [claimed-docs] “Building Fin Procedures”
   • [claimed-docs] “Manage your Fin workflows”
   • [claimed-docs] “Introduction to Fin Tasks”
   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”
   • [claimed-docs] “Proactive Outbound Suite”
   • [claimed-docs] “Fin resolves 76% of customer queries on average, and handles multi-step queries end to end. Your customers get fast, accurate answers. Your …”
   • [community] “A commenter with a decade of customer-service AI/NLP experience argued 99% of support tasks (order status, returns, troubleshooting) are ful…”

   proof ↗⚑ flag

   Parahelp✓fullclaimed8/10

   Docs explicitly describe automations as Internal Agent tasks that run on a schedule or trigger (e.g., weekday 9am, GitHub PR merge), configurable with auto-approve so they act without waiting for manual approval, enabling background autonomous operation. Additional support covers auto-approve per tool/task, API-driven triggering, and monitoring/reverting via releases. Missing for 10: independent third-party verification of long-running unattended automations in production and more detail on failure/alerting handling during autonomous runs.

   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”
   • [claimed-docs] “By default, every action requires manual approval. You can set specific tools to auto-approve per task or automation”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”
   • [claimed-docs] “Configuration actions publish as a release on the Releases page, where you can track the impact and revert with one click.”
   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Fin
   Fin✓fullcommunity8/10

   Fin is itself a built-in AI agent that customers and support teams delegate tasks to — it resolves ~76% of queries end-to-end, handles multi-step 'Procedures' with business logic, takes actions on external systems, and works across channels (chat, email, voice, Slack, WhatsApp). This is documented extensively in first-party docs/help articles covering delegation-style use (Fin Tasks, Fin Procedures, escalation rules, API/Agent API for programmatic delegation). missing for 10: independent hands-on validation of delegation quality (one HN commenter says they've never seen Fin in the wild, and another questions whether autonomous agent reasoning is even the right approach vs deterministic workflows), and no live product screenshots/demo confirming smooth end-user delegation experience.

   • [claimed-docs] “Handles tickets, cases, emails, live chat, WhatsApp, SMS, and more”
   • [claimed-docs] “Takes action to update external systems”
   • [claimed-docs] “Building Fin Procedures”
   • [claimed-docs] “Introduction to Fin Tasks”
   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”
   • [claimed-docs] “Fin resolves 76% of customer queries on average, and handles multi-step queries end to end. Your customers get fast, accurate answers. Your …”
   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [community] “"I've never seen or interacted with Fin that I've noticed... I suspect it's very visible for Intercom, but not necessarily so for everyone e…”
   • [community] “A commenter with a decade of customer-service AI/NLP experience argued 99% of support tasks (order status, returns, troubleshooting) are ful…”

   proof ↗⚑ flag

   Parahelp✓fullclaimed7/10

   Parahelp's Internal Agent is a built-in AI assistant you delegate configuration and operational tasks to via natural language (docs-1), which can act autonomously per auto-approve settings (docs-8, docs-14), run on schedules/triggers (docs-5), and proactively surface gaps (docs-17), with the agent also bootstrapping itself from historical tickets (docs-19). Missing for 10: independent/hands-on user reports of delegating tasks and outcomes, and more detail on the breadth/limits of what can be delegated beyond configuration and support workflows.

   • [claimed-docs] “Describe the flow you want in natural language - the policies, knowledge, and tool connections it combines - and the Internal Agent configur…”
   • [claimed-docs] “the Internal Agent analyzes your last 500-1,000 resolved tickets along with your existing context to build the first version of your Custome…”
   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”
   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Parahelp
   Fin~partialclaimed6/10

   Fin's core function is responding to customer queries in natural language across channels, and admins can 'give Fin guidance' and train Procedures using natural-language instructions (docs-22, docs-44, docs-60); the Fin CLI also lets an AI coding agent configure Fin setup based on natural-language prompts (docs-38). However there's no clear evidence of a full natural-language command interface for operating/administering the product itself (e.g., configuring settings, running reports) beyond training/guidance content. Missing for 10: documented NL-driven admin console commands, evidence of broad NL task execution beyond content/guidance training, and independent verification of this capability in practice.

   • [claimed-docs] “Giving Fin Guidance”
   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”
   • [claimed-docs] “Point your AI coding Agent at the Fin CLI to set up Fin on your website and configure your Intercom helpdesk — all without leaving your codi…”
   • [claimed-docs] “Train Fin on your knowledge, data, policies, and tone of voice. Fin will use everything it knows to deliver consistent, accurate answers”

   proof ↗⚑ flag

   Parahelp✓fullclaimed7/10

   Parahelp's core interaction model is describing desired flows, policies, and guardrails in natural language, which the Internal Agent then configures into tasks, automations, and guardrail rules (e.g. 'Require Slack approval before refund tool runs above $100'). This covers configuring agent behavior via NL, though it's scoped to support/ops workflows rather than general-purpose NL command execution. Missing for 10: independent/hands-on evidence of NL command accuracy, and clarity on whether all product actions (not just configuration) can be triggered via natural language versus UI/API.

   • [claimed-docs] “Describe the flow you want in natural language - the policies, knowledge, and tool connections it combines - and the Internal Agent configur…”
   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “When a ticket is about an enterprise account, transfer it to the enterprise team with a summary note.”
   • [claimed-docs] “the Internal Agent analyzes your last 500-1,000 resolved tickets along with your existing context to build the first version of your Custome…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Fin—none0/10

   While Fin has API docs (developers.intercom.com) and an SDK on GitHub, there is no evidence of an interactive API reference with runnable/try-it examples; a probe explicitly found no OpenAPI/Swagger spec published at any candidate path, and no docs mention a live API console.

   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fin.ai/openapi.json, https://fin.ai/swagger.json, https://fin.ai/api/openapi.json, https://f…”
   • [github] “The Intercom TypeScript library provides convenient access to the Intercom APIs from TypeScript.”

   proof ↗⚑ flag

   Parahelp—none0/10

   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. try-it console, code samples execution); explicit openapi.json probes all 404'd, suggesting no standard interactive spec is exposed.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.parahelp.com/openapi.json, https://docs.parahelp.com/swagger.json, https://docs.parahel…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public API reference at https://app.parahelp.com/api/docs is reachable keylessly — no login wall in…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Fin—none0/10

   Fin has documented REST APIs (Fin Agent API, Node/TS SDK) but no evidence of a downloadable machine-readable spec; a direct probe for OpenAPI/swagger files at common paths returned 404 for all candidates, and no docs page links such a spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://fin.ai/openapi.json, https://fin.ai/swagger.json, https://fin.ai/api/openapi.json, https://f…”
   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”

   proof ↗⚑ flag

   Parahelp—none0/10

   Parahelp has a customer-facing API and a public API reference page (app.parahelp.com/api/docs), but explicit probes for a machine-readable OpenAPI/Swagger spec at all standard paths (openapi.json, swagger.json, etc.) returned 404, and no evidence shows a downloadable spec file.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.parahelp.com/openapi.json, https://docs.parahelp.com/swagger.json, https://docs.parahel…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public API reference at https://app.parahelp.com/api/docs is reachable keylessly — no login wall in…”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Parahelp
   Fin~partialclaimed4/10

   Fin documents a testing/preview workflow ('How to preview and test Fin', testing across thousands of scenarios before going live) that implies an isolated test/preview mode, but no evidence explicitly describes a sandbox environment separate from production data or confirms production data isolation during testing. Missing for 10: explicit sandbox/staging environment documentation, confirmation that test scenarios don't touch live customer data, and any independent/hands-on corroboration of this isolation.

   • [claimed-docs] “How to preview and test Fin”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation... …”

   proof ↗⚑ flag

   Parahelp~partialclaimed5/10

   Docs describe simulations that replay historical tickets or mock scenarios against configurations, which functions as a sandbox for testing without touching production, and separately note that 'production tests verify your tool connections' implying a distinction between simulated and production environments. However, there is no explicit mention of a dedicated sandbox environment, isolated test data store, or guarantee that simulations cannot write to production systems/tools. missing for 10: explicit documentation of an isolated sandbox environment separate from production data/tools, confirmation that simulated runs cannot trigger real side-effects, and independent/hands-on verification of this isolation.

   • [claimed-docs] “Simulations replay your historical tickets - or mock scenarios - against the configurations in the task, and production tests verify your to…”
   • [claimed-docs] “Configuration actions publish as a release on the Releases page, where you can track the impact and revert with one click.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Fin—none0/10

   The evidence shows Fin has a REST API with a 'Preview API version' for new endpoints (docs-4) and a general changes/changelog page (docs-1), but there is no documented versioning scheme or explicit deprecation policy (e.g., version sunset timelines, backward-compatibility guarantees) cited anywhere in the pack.

   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”
   • [claimed-docs] “See exactly when errors started, which status codes came back, and confirm a fix actually worked.”

   proof ↗⚑ flag

   Parahelp—none0/10

   There is evidence of an API existing (customer requests via API, run automations via API) and public API docs, but no mention of API versioning or a documented deprecation policy anywhere in the evidence pack. Missing for 10: versioning scheme, deprecation policy, changelog entries about breaking changes or API version sunset.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Parahelp
   Fin~partialclaimed3/10

   Fin exposes a programmatic API and TypeScript SDK with a pagination iterator for looping over items, plus a content-import endpoint, implying some capacity for scripted bulk actions, but there is no documented bulk-edit, bulk-resolve, or batch-action feature for AI-native users. missing for 10: explicit bulk operation/batch endpoint documentation, hands-on evidence of processing many items in one call, and any UI/CLI bulk-action support.

   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [github] “await client.aiContent.createContentImportSource({ url: "https://www.example.com" });”
   • [github] “List endpoints are paginated. The SDK provides an iterator so that you can simply loop over the items”

   proof ↗⚑ flag

   Parahelp~partialclaimed4/10

   Evidence shows batch-style processing (analyzing 500-1,000 historical tickets, simulations replaying many tickets, scheduled/triggered automations) which imply working across many items, but there's no explicit documentation of a user-facing bulk-action feature (e.g., mass-editing or resolving many tickets/items in one command). missing for 10: explicit bulk-operation UI/API (e.g., batch resolve/tag/update across selected items), evidence of throughput/rate limits for bulk actions, independent confirmation of bulk workflows in production.

   • [claimed-docs] “the Internal Agent analyzes your last 500-1,000 resolved tickets along with your existing context to build the first version of your Custome…”
   • [claimed-docs] “Simulations replay your historical tickets - or mock scenarios - against the configurations in the task, and production tests verify your to…”
   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”
   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Parahelp
   Fin~partialclaimed6/10

   Fin exposes several automation primitives that fit an event→action rule model: webhooks that fire on real-time Intercom events, configurable escalation guidance/rules, Fin Procedures/workflows, and Operator/Monitors for incident-triggered behavior. This is more than none, but the pack lacks a first-class 'if event X then action Y' rule-builder walkthrough or independent confirmation of how flexible/robust these triggers are. Missing for 10: a documented dedicated rules/automation builder UI, concrete example of a user-defined trigger-condition-action rule, and independent (non-vendor) evidence that automation rules work reliably in practice.

   • [claimed-docs] “Webhooks allow you to subscribe to real-time notifications of events happening in Intercom; a Contact created, an incoming Conversation rece…”
   • [claimed-docs] “Manage Fin AI Agent's escalation guidance and rules”
   • [claimed-docs] “Building Fin Procedures”
   • [claimed-docs] “Manage your Fin workflows”
   • [claimed-docs] “Operator, CX Score, AI Topics, Trends, AI Recommendations, Monitors, Custom AI Scorecards, Incident Detection”

   proof ↗⚑ flag

   Parahelp✓fullclaimed8/10

   Docs explicitly describe automations as Internal Agent tasks that run on schedules or triggers (e.g., GitHub PR merge), plus guardrail rules that trigger actions on events (Slack approval above $100, transfer enterprise tickets), matching the rule-based, event-triggered automation story. Missing for 10: independent/third-party corroboration of automation reliability and a broader list of supported trigger event types beyond the examples given.

   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”
   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “When a ticket is about an enterprise account, transfer it to the enterprise team with a summary note.”
   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”
   • [claimed-docs] “By default, every action requires manual approval. You can set specific tools to auto-approve per task or automation”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Parahelp
   Fin—none0/10

   Fin's evidence covers webhooks (event-driven, not scheduled), procedures, and a Proactive Outbound Suite, but nothing describes cron-like scheduling of recurring jobs or workflows on a time-based schedule. missing for 10: any documentation of scheduled/recurring workflow triggers, cron-style job scheduling, or recurring automation configuration.

   • [claimed-docs] “Webhooks allow you to subscribe to real-time notifications of events happening in Intercom; a Contact created, an incoming Conversation rece…”
   • [claimed-docs] “Proactive Outbound Suite”
   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”

   proof ↗⚑ flag

   Parahelp✓fullclaimed8/10

   Parahelp's docs explicitly describe automations as Internal Agent tasks that run on a schedule (e.g. every weekday at 9am) or on triggers, which directly matches recurring scheduled workflows, and these can be run via API for custom automation depth. Missing for 10: no independent/hands-on corroboration of scheduling reliability, and no detail on schedule configuration flexibility (cron-like options, timezone handling, etc.).

   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”
   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Parahelp
   Fin—none0/10

   The evidence pack shows Fin Procedures/workflow management and testing before go-live ('test it across thousands of scenarios before anything goes live, roll out changes with control'), but there is no concrete documentation of version history, diffing/review of automation changes, or an explicit rollback mechanism for Procedures/Workflows/Guidance. Nothing describes a changelog, version comparison, or a 'revert to previous version' feature for automations.

   • [claimed-docs] “Building Fin Procedures”
   • [claimed-docs] “Manage your Fin workflows”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”

   proof ↗⚑ flag

   Parahelp~partialclaimed6/10

   Parahelp supports release publishing with one-click revert and knowledge version history with diffs (parahelp-docs-4, parahelp-docs-9), directly covering versioning and rollback of configurations/automations. However, there's no explicit review/approval workflow for the versioning itself (approvals exist for actions, not for config changes review), and no evidence of branching, staged review, or audit trail beyond 'who published what and when'. Missing for 10: dedicated review/approval step before publishing a release, granular version comparison across automations (not just knowledge), and independent/hands-on confirmation of rollback working in practice.

   • [claimed-docs] “Configuration actions publish as a release on the Releases page, where you can track the impact and revert with one click.”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”
   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”

   proof ↗⚑ flag

Channels

1. support leaderOne agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social

   weight 2 · round to Fin
   Fin✓fullclaimed7/10

   Fin explicitly documents multi-channel support spanning live chat/messenger (in-app), email, Slack, WhatsApp, SMS, and voice, with dedicated channel pages for each (docs-9, docs-50, docs-51, docs-65, docs-48). Missing for 10: explicit named coverage of broader 'social' channels like Instagram/Facebook/X/Twitter — only 'and more' is implied, not documented by name, so the specific 'social' claim in the story is only partially evidenced.

   • [claimed-docs] “Handles tickets, cases, emails, live chat, WhatsApp, SMS, and more”
   • [claimed-docs] “Fin delivers unrivaled performance across every channel. Wherever customers reach out, Fin provides fast, accurate, personalized support”
   • [claimed-docs] “Fin over Email resolves everything from simple FAQs to complex threads with attachments and multiple recipients”
   • [claimed-docs] “Fin for Slack supports your customers directly in Slack communities and dedicated Connect channels, resolving questions instantly with repli…”
   • [claimed-docs] “Fin for messenger brings the highest-performing AI Agent for customer service to live chat, delivering exceptional, on-brand support”

   proof ↗⚑ flag

   Parahelp~partialclaimed5/10

   Parahelp's Customer Agent operates as a team member inside major ticketing/chat platforms (Intercom, Zendesk, Front, Plain, Pylon), and its Pylon integration explicitly covers email, live chat, and Slack tickets, showing some multi-channel reach. However, there is no evidence of native WhatsApp or social-media channel support, so the 'channels customers actually use' claim is only partially substantiated. Missing for 10: explicit WhatsApp support, explicit social media channel support, and independent confirmation beyond vendor docs.

   • [claimed-docs] “Your Customer Agent works as a team member in Intercom, Zendesk, Front, Plain, or Pylon.”
   • [claimed-docs] “Parahelp now integrates with Pylon! ... their agents resolve tickets across email, live chat, and Slack”

   proof ↗⚑ flag

Languages

1. support leaderThe agent supports customers in many languages, even where my knowledge base exists only in English

   weight 2 · round to Fin
   Fin✓fullclaimed7/10

   Intercom/Fin explicitly documents multi-language support ('Use Fin AI Agent in multiple languages') allowing Fin to answer in customers' languages even when the knowledge base content is authored in English, which directly matches the story. Missing for 10: independent/hands-on verification of translation quality or explicit detail on how English-only knowledge base content is translated/handled per language.

   • [claimed-docs] “Use Fin AI Agent in multiple languages”

   proof ↗⚑ flag

   Parahelp—none0/10

   No evidence in the pack mentions multilingual support, language detection, or translation capabilities for the Customer Agent; documentation focuses on ticketing integrations, tool connections, and knowledge management without addressing cross-language customer support.

   ⚑ flag

Voice

1. support leaderThe agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat

   weight 2 · round to Fin
   Fin✓fullclaimed7/10

   Fin Voice is a documented dedicated product ('Deploy Fin Voice', 'Fin Voice 2 runs on Apex Flash... latency-sensitive tasks', 'grounded in your knowledge base, and trained to apply your specific policies on every call'), indicating speech-in/speech-out phone support using the same knowledge base as chat. Missing for 10: independent/hands-on validation of voice call quality or action-taking parity specifically for phone, and no detail on how actions (e.g., updating systems) work identically on voice vs chat.

   • [claimed-docs] “Deploy Fin Voice”
   • [claimed-docs] “grounded in your knowledge base, and trained to apply your specific policies on every call.”
   • [claimed-docs] “Fin Voice 2 runs on Apex Flash - our latest Fin model, built for latency-sensitive tasks.”
   • [claimed-docs] “Fin delivers unrivaled performance across every channel. Wherever customers reach out, Fin provides fast, accurate, personalized support”

   proof ↗⚑ flag

   Parahelp—none0/10

   Parahelp's evidence describes a text-based Customer Agent that works via ticketing systems and API, with no mention of voice/telephony channels, speech-to-text, or text-to-speech capabilities. No citation addresses phone call handling.

   ⚑ flag

Handoff

1. support leaderWhen the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselves

   weight 3 · round to Fin
   Fin~partialclaimed6/10

   Docs confirm Fin can transfer/escalate to human agents within the preferred inbox, has configurable escalation guidance/rules, and supports hand-off via JavaScript and an orchestration 'Escalate to a human' API — showing escalation handoff is a real, built feature. However, none of the evidence explicitly confirms that a generated summary or a structured collection of gathered details is passed along with the full conversation to the human agent, so the 'never repeats themselves' guarantee is not directly documented. Missing for 10: explicit documentation of automatic conversation summary generation at escalation, evidence that collected customer details are packaged and handed off, and independent/hands-on confirmation the handoff actually eliminates repetition.

   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”
   • [claimed-docs] “Transfers to agents directly in preferred Inbox”
   • [claimed-docs] “Manage Fin AI Agent's escalation guidance and rules”
   • [claimed-docs] “Hand-off with JavaScript”

   proof ↗⚑ flag

   Parahelp~partialclaimed5/10

   Docs show guardrail rules that transfer tickets 'with a summary note' to human teams (parahelp-docs-7) and ticketing-system integrations where the agent works as a team member (parahelp-docs-15), implying handoff context is passed, but there's no explicit description of a full escalation package (full transcript + generated summary + structured collected details) reaching the human agent. missing for 10: dedicated documentation of the escalation handoff artifact itself (transcript, structured details form, summary format), evidence that customers never have to repeat themselves, and any hands-on/independent confirmation of this workflow.

   • [claimed-docs] “When a ticket is about an enterprise account, transfer it to the enterprise team with a summary note.”
   • [claimed-docs] “Your Customer Agent works as a team member in Intercom, Zendesk, Front, Plain, or Pylon.”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”

   proof ↗⚑ flag

Rules

1. support ops leadI configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys

   weight 2 · round drawn
   Fin~partialclaimed6/10

   Docs explicitly cover configuring escalation/handoff behavior — 'Manage Fin AI Agent's escalation guidance and rules', 'Giving Fin Guidance', 'Hand-off with JavaScript', an orchestration 'Escalate to a human' API endpoint, and 'Transfers to agents directly in preferred Inbox' — showing topic/guidance-based and explicit-request handoff configuration exists. However, none of the evidence specifically documents sentiment- or customer-tier-based handoff triggers, nor is there independent/hands-on verification that the agent reliably obeys these rules in practice. Missing for 10: explicit sentiment/tier-based escalation config docs, and third-party evidence confirming reliable adherence to configured handoff rules.

   • [claimed-docs] “Manage Fin AI Agent's escalation guidance and rules”
   • [claimed-docs] “Giving Fin Guidance”
   • [claimed-docs] “Hand-off with JavaScript”
   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”
   • [claimed-docs] “Transfers to agents directly in preferred Inbox”

   proof ↗⚑ flag

   Parahelp~partialclaimed6/10

   Docs show configurable guardrails that trigger handoff/escalation by topic (e.g., transfer enterprise-account tickets) and by threshold (Slack approval on refunds >$100), plus auto-approve vs manual-approval controls and release tracking for changes — evidence of rule-based handoff configuration and enforcement. However, there is no explicit documentation of sentiment-based triggers, customer-tier-specific rules beyond the enterprise example, or handling of explicit 'transfer me to a human' requests, and no independent/hands-on verification that these rules are reliably obeyed in production. Missing for 10: sentiment-based escalation rules, explicit-request handoff configuration, customer-tier granularity beyond one example, and third-party evidence of reliability.

   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “When a ticket is about an enterprise account, transfer it to the enterprise team with a summary note.”
   • [claimed-docs] “By default, every action requires manual approval. You can set specific tools to auto-approve per task or automation”
   • [claimed-docs] “Configuration actions publish as a release on the Releases page, where you can track the impact and revert with one click.”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”

   proof ↗⚑ flag

Hallucination

1. ai-native userGuardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess

   weight 3 · round to Fin
   Fin~partialclaimed6/10

   Docs show Fin is 'trained on your knowledge, data, policies, and tone' and grounded in the knowledge base (docs-46/60/49), with configurable 'escalation guidance and rules' (docs-25) and pre-launch testing across scenarios (docs-45/59), which together imply guardrails against off-knowledge answers and hand-off rather than free invention. However there is no explicit documentation of a 'safe decline' behavior or hallucination-refusal mechanism, and no independent/hands-on evidence confirming Fin actually declines rather than guesses on off-knowledge questions. Missing for 10: explicit safe-decline/refusal documentation, third-party or hands-on verification that Fin avoids inventing policies/prices, and quantified guardrail testing results.

   • [claimed-docs] “Train Fin on your knowledge, data, policies, and tone of voice.”
   • [claimed-docs] “Train Fin on your knowledge, data, policies, and tone of voice. Fin will use everything it knows to deliver consistent, accurate answers”
   • [claimed-docs] “Manage Fin AI Agent's escalation guidance and rules”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation... …”
   • [claimed-docs] “grounded in your knowledge base, and trained to apply your specific policies on every call.”
   • [claimed-docs] “give you the tools to safely deploy AI within your own boundaries.”
   • [claimed-docs] “We meet the world's leading compliance standards—and give you the tools to safely deploy AI within your own boundaries.”

   proof ↗⚑ flag

   Parahelp~partialclaimed4/10

   Parahelp's guardrails docs focus on approval gates for actions (e.g., refund thresholds, enterprise transfers) and versioned knowledge bases, which constrain what the agent can execute and what knowledge it draws from — but there is no explicit documentation of a 'safe decline' behavior when a question falls outside known knowledge/policy. Missing for 10: explicit fallback/decline behavior for off-knowledge queries, evidence of hallucination prevention or confidence thresholds, and independent confirmation the agent refuses rather than guesses.

   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “When a ticket is about an enterprise account, transfer it to the enterprise team with a summary note.”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”

   proof ↗⚑ flag

Supervision

1. support ops leadLaunch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer

   weight 2 · round to Parahelp
   Fin—none0/10

   Evidence shows Fin's guardrails center on escalation rules, hand-off to human agents, and pre-launch testing/preview (docs-25, docs-29, docs-31, docs-45), but nothing describes a supervised/draft-for-approval mode where Fin composes replies that a human must approve before they reach the customer on every interaction. Community commentary (comm-3) even argues for more deterministic, human-controlled workflows, but that's not evidence Fin ships this specific approval-gate mode.

   • [claimed-docs] “Manage Fin AI Agent's escalation guidance and rules”
   • [claimed-docs] “How to preview and test Fin”
   • [claimed-docs] “Hand-off with JavaScript”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”
   • [community] “A commenter with a decade of customer-service AI/NLP experience argued 99% of support tasks (order status, returns, troubleshooting) are ful…”

   proof ↗⚑ flag

   Parahelp✓fullclaimed8/10

   Docs explicitly state that by default every action requires manual approval, with per-tool/task auto-approve override, and cite concrete examples like Slack approval before refund actions run — directly matching a supervised human-approval-before-customer-impact mode. Releases page tracks and reverts config changes, adding auditability to this guardrail workflow. Missing for 10: independent/hands-on verification of the approval UI in practice and confirmation that 'draft for approval' specifically (vs. blocking tool actions) is the default behavior for all reply types.

   • [claimed-docs] “By default, every action requires manual approval. You can set specific tools to auto-approve per task or automation”
   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”
   • [claimed-docs] “Configuration actions publish as a release on the Releases page, where you can track the impact and revert with one click.”

   proof ↗⚑ flag

Topic controls

1. support ops leadI mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them

   weight 2 · round drawn
   Fin~partialclaimed6/10

   Fin has documented first-party features for exactly this: 'Giving Fin Guidance' and 'Manage Fin AI Agent's escalation guidance and rules' let ops teams define escalation/human-handoff rules, and the Agent API includes an 'Escalate to a human' capability. However this escalate-to-human orchestration endpoint is explicitly noted as Preview-only, and there is no independent or hands-on evidence confirming the agent reliably respects human-only topic boundaries without ever freelancing. Missing for 10: independent verification that escalation rules are strictly enforced (no freelancing), and GA (non-preview) status of escalate-to-human tooling.

   • [claimed-docs] “Giving Fin Guidance”
   • [claimed-docs] “Manage Fin AI Agent's escalation guidance and rules”
   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”

   proof ↗⚑ flag

   Parahelp~partialclaimed6/10

   Parahelp's guardrails let ops leads set conditional rules such as escalating enterprise-account tickets to a human team or requiring approval before certain tools run, and every agent action requires manual approval by default unless explicitly auto-approved — which supports building 'never freelance, hand off to human' rules for chosen topics. However, there's no dedicated 'mark topic as human-only' feature or explicit examples for legal threats/cancellations/security specifically, only generic escalation/approval guardrail examples. Missing for 10: explicit topic-blocklist UI, named legal/cancellation/security guardrail templates, and evidence the escalation is airtight (agent truly cannot act) rather than just gated by approval.

   • [claimed-docs] “Require Slack approval before the refund tool runs on amounts above $100.”
   • [claimed-docs] “When a ticket is about an enterprise account, transfer it to the enterprise team with a summary note.”
   • [claimed-docs] “By default, every action requires manual approval. You can set specific tools to auto-approve per task or automation”
   • [claimed-docs] “Enable auto-approve for a task or automation, and the Internal Agent can perform any action through the connection without asking for approv…”

   proof ↗⚑ flag

Analytics

1. support leaderDashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec team

   weight 3 · round to Fin
   Fin~partialclaimed4/10

   Fin's Insights/Monitors/AI Recommendations pages reference analyzing conversations and measuring CX, and CX Score/Trends are listed as features, implying some dashboard capability, but no evidence explicitly confirms a unified dashboard reporting resolution rate, CSAT, handoff rate, and cost per resolution together. missing for 10: explicit documentation or screenshots of a dashboard showing resolution rate, CSAT, handoff rate, and cost per resolution metrics; independent confirmation these specific KPIs are surfaced for exec reporting.

   • [claimed-docs] “Insights continuously analyzes every Fin and human conv”
   • [claimed-docs] “With Insights, Monitors New, and Recommendations, you have everything you need to understand, measure, and improve your customer experience”
   • [claimed-docs] “Operator, CX Score, AI Topics, Trends, AI Recommendations, Monitors, Custom AI Scorecards, Incident Detection”
   • [claimed-docs] “Fin resolves 76% of customer queries on average, and handles multi-step queries end to end. Your customers get fast, accurate answers. Your …”

   proof ↗⚑ flag

   Parahelp—none0/10

   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.

   ⚑ flag

Insights

1. support leaderThe platform clusters conversations by topic and surfaces emerging product issues before they spike ticket volume

   weight 1 · round to Fin
   Fin~partialclaimed6/10

   Fin's pricing page lists analytics features like 'AI Topics, Trends... Monitors... Incident Detection' and 'Insights continuously analyzes every Fin and human conversation,' indicating topic clustering and emerging-issue detection capability, but there is no deeper documentation, screenshots, or independent corroboration of how this works in practice. Missing for 10: detailed product docs on topic clustering methodology, evidence of proactive alerting before ticket-volume spikes, and independent/hands-on validation of the insights/analytics feature.

   • [claimed-docs] “Operator, CX Score, AI Topics, Trends, AI Recommendations, Monitors, Custom AI Scorecards, Incident Detection”
   • [claimed-docs] “Insights continuously analyzes every Fin and human conv”
   • [claimed-docs] “With Insights, Monitors New, and Recommendations, you have everything you need to understand, measure, and improve your customer experience”

   proof ↗⚑ flag

   Parahelp—none0/10

   Parahelp's docs describe automations that 'watch your tools and your support queue and surface gaps on their own' (parahelp-docs-17), but this is about detecting configuration/knowledge gaps, not clustering conversations by topic or flagging emerging issues before ticket volume spikes. No evidence pack item describes topic clustering, trend detection, or predictive volume analytics.

   ⚑ flag

Helpdesk

1. developerThe agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways

   weight 3 · round drawn
   Fin✓fullclaimed8/10

   Fin explicitly documents standalone deployment plus deep integrations with Zendesk, Salesforce, HubSpot, Freshdesk and 'any helpdesk', with two-way data sync (bring content/history over, surface data in inbox) and APIs/MCP/webhooks for programmatic ticket/context sync. Multiple dedicated integration pages (Zendesk, Salesforce, HubSpot, Freshdesk) and platform docs (Agent API, MCP, webhooks, data connectors) corroborate bidirectional context flow. missing for 10: independent/hands-on verification of the bidirectional sync working in production, and no direct evidence of Intercom-native standalone ticketing depth compared to third-party helpdesks.

   • [claimed-docs] “Fin AI Agent works seamlessly with any helpdesk, including Salesforce, HubSpot, and more.”
   • [claimed-docs] “How Fin integrates with Zendesk”
   • [claimed-docs] “How Fin integrates with Salesforce”
   • [claimed-docs] “bring your team over from any helpdesk without losing your content, your history, or a single day of support.”
   • [claimed-docs] “Surface data from Salesforce, HubSpot, and 450+ apps and integrations directly in the inbox”
   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “Learn how to use the Model Context Protocol (MCP) to enable AI agents to securely access and interact with your Intercom data whenever helpf…”
   • [claimed-docs] “Webhooks allow you to subscribe to real-time notifications of events happening in Intercom; a Contact created, an incoming Conversation rece…”
   • [claimed-docs] “It works through MCP or API Data Connectors for your business tools, integrations with Intercom or your existing helpdesk”
   • [claimed-docs] “Intercom connects to 450+ first- and third-party apps and integrations, including CRMs like Salesforce and HubSpot, dev tools like Jira, Lin…”

   proof ↗⚑ flag

   Parahelp✓fullclaimed8/10

   Docs explicitly confirm the Customer Agent works inside Zendesk, Intercom, Front, Plain, or Pylon as a 'team member,' with a standalone API mode for ticket-free workflows, and shared tool/knowledge connections across both agents. Ticket sync/context bidirectionality is implied by the 'team member' integration model and API mode, but no explicit two-way sync mechanics or Salesforce-specific mention are documented. Missing for 10: explicit mention of Salesforce support, and detailed description of two-way ticket/context syncing mechanics beyond high-level integration claims.

   • [claimed-docs] “Your Customer Agent works as a team member in Intercom, Zendesk, Front, Plain, or Pylon.”
   • [claimed-docs] “Parahelp now integrates with Pylon! ... their agents resolve tickets across email, live chat, and Slack”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”
   • [claimed-docs] “Connect a tool once, and both agents can use it”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system.”

   proof ↗⚑ flag

Freshness

1. support ops leadKnowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads

   weight 2 · round to Fin
   Fin~partialclaimed5/10

   Docs mention 'Sync and manage websites' and content import via API (createContentImportSource), implying re-syncing of website sources, but there is no explicit documentation of scheduled or change-triggered automatic re-syncing across all source types (docs, help centers, files) without manual re-upload. missing for 10: explicit scheduling/cron documentation for content refresh, confirmation of automatic change-detection re-sync for non-website sources (PDFs, articles), and independent/hands-on verification that sync happens without manual re-upload.

   • [claimed-docs] “Sync and manage websites”
   • [github] “await client.aiContent.createContentImportSource({ url: "https://www.example.com" });”

   proof ↗⚑ flag

   Parahelp~partialclaimed3/10

   Parahelp documents a generic automations feature that can run on a schedule or trigger (parahelp-docs-5) and shows live knowledge with version history (parahelp-docs-9), but there is no explicit documentation that knowledge sources are automatically re-synced on a schedule or on change rather than manually updated. missing for 10: explicit knowledge-source auto-sync mechanism, evidence of scheduled/triggered re-ingestion tied specifically to knowledge base content, independent confirmation of this behavior.

   • [claimed-docs] “An automation is an Internal Agent task that runs on a schedule, like every weekday at 9am, or a trigger, like a GitHub PR merging”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”
   • [claimed-docs] “the Internal Agent analyzes your last 500-1,000 resolved tickets along with your existing context to build the first version of your Custome…”

   proof ↗⚑ flag

Gaps

1. support ops leadThe platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions

   weight 1 · round to Parahelp
   Fin~partialclaimed4/10

   Fin's analytics stack (Insights, Monitors, AI Topics/Trends, AI Recommendations, Incident Detection) implies some ability to flag where Fin underperforms or topics trend poorly, and 'Giving Fin Guidance'/'Adding content to Fin' suggest content curation workflows, but no evidence explicitly describes detecting knowledge gaps or conflicting source content as a distinct surfaced capability. Missing for 10: explicit documentation of a 'knowledge gap' or 'content conflict' detection feature, and any hands-on/independent confirmation that such gaps are surfaced to support-ops leads.

   • [claimed-docs] “Operator, CX Score, AI Topics, Trends, AI Recommendations, Monitors, Custom AI Scorecards, Incident Detection”
   • [claimed-docs] “Insights continuously analyzes every Fin and human conv”
   • [claimed-docs] “With Insights, Monitors New, and Recommendations, you have everything you need to understand, measure, and improve your customer experience”
   • [claimed-docs] “Giving Fin Guidance”
   • [claimed-docs] “Adding content to Fin”

   proof ↗⚑ flag

   Parahelp~partialclaimed6/10

   Docs show explicit gap-surfacing automations that watch tools/support queues (parahelp-docs-17) plus knowledge version history with diffs and publisher attribution (parahelp-docs-9), which support detecting stale or conflicting knowledge. However, there's no evidence of conflict detection between multiple knowledge sources, no dashboard/reporting UI shown, and no independent/hands-on corroboration of gap surfacing actually catching missed or fumbled questions. missing for 10: evidence of explicit conflicting-content detection across knowledge sources, a surfaced-gaps UI/report example, and independent verification that this reduces missed/fumbled tickets.

   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”

   proof ↗⚑ flag

Grounding

1. ai-native userEvery answer is grounded in my own content and shows which article or source it drew from

   weight 3 · round to Fin
   Fin~partialclaimed5/10

   Fin's docs confirm it is trained/grounded on the customer's own content (help center, websites, docs, knowledge sources) via content import and knowledge retrieval APIs (e.g., docs-46/60 'train Fin on your knowledge', docs-28 'Adding content to Fin', docs-27 'Sync and manage websites', gh-1 content import API, docs-39 knowledge retrieval API), but no evidence explicitly shows that end-user answers surface or cite the specific source article they were drawn from. missing for 10: explicit documentation or UI evidence of in-answer source citation/attribution, independent/hands-on confirmation of citation behavior.

   • [claimed-docs] “Train Fin on your knowledge, data, policies, and tone of voice.”
   • [claimed-docs] “Train Fin on your knowledge, data, policies, and tone of voice. Fin will use everything it knows to deliver consistent, accurate answers”
   • [claimed-docs] “Adding content to Fin”
   • [claimed-docs] “Sync and manage websites”
   • [github] “await client.aiContent.createContentImportSource({ url: "https://www.example.com" });”
   • [claimed-docs] “The Fin API platform includes APIs for answer generation and knowledge retrieval, available as a set or independently.”
   • [claimed-docs] “grounded in your knowledge base, and trained to apply your specific policies on every call.”

   proof ↗⚑ flag

   Parahelp—none0/10

   Evidence shows Parahelp maintains a versioned knowledge base (docs-9) that the Customer Agent draws on, but there is no evidence that individual answers to users cite or surface the specific article/source they were grounded in. missing for 10: any documentation of per-answer source citation or attribution UI, evidence of end-user-facing 'grounded in X article' display.

   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”

   proof ↗⚑ flag

Ingestion

1. support ops leadThe agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring

   weight 3 · round to Fin
   Fin✓fullclaimed8/10

   Fin explicitly supports ingesting websites/help center content (createContentImportSource, 'Sync and manage websites', 'Adding content to Fin'), integrates with helpdesks (Zendesk, Salesforce, HubSpot, Freshdesk) preserving existing content/history, and pulls in Confluence, Notion, Zendesk content into a unified knowledge source alongside data connectors for third-party tools. This covers help center, docs, past ticket/helpdesk content, and wiki tools (Confluence/Notion) without manual re-authoring. Missing for 10: no explicit mention of ingesting 'internal wikis' broadly beyond Confluence/Notion, and no independent/hands-on verification of ingestion fidelity or effort required.

   • [github] “await client.aiContent.createContentImportSource({ url: "https://www.example.com" });”
   • [claimed-docs] “Sync and manage websites”
   • [claimed-docs] “Adding content to Fin”
   • [claimed-docs] “Bring content from your help center, Zendesk, Confluence, Notion, and more into one place, so Fin, Copilot, and your team always work from t…”
   • [claimed-docs] “bring your team over from any helpdesk without losing your content, your history, or a single day of support.”
   • [claimed-docs] “How Fin integrates with Zendesk”
   • [claimed-docs] “How Fin integrates with Salesforce”
   • [claimed-docs] “Your team stays on Freshdesk.”

   proof ↗⚑ flag

   Parahelp~partialclaimed5/10

   Parahelp's Internal Agent explicitly analyzes past resolved tickets and existing context to build the Customer Agent's knowledge/configuration automatically, and there's a live knowledge base with version history, but evidence only covers tickets and general 'existing context' rather than explicit ingestion of help center articles, docs, or internal wikis as named sources. missing for 10: explicit documentation of connectors/ingestion for help-center articles, internal wikis, and docs repositories as knowledge sources; independent evidence of successful re-ingestion at scale beyond ticket history.

   • [claimed-docs] “the Internal Agent analyzes your last 500-1,000 resolved tickets along with your existing context to build the first version of your Custome…”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”
   • [claimed-docs] “Describe the flow you want in natural language - the policies, knowledge, and tool connections it combines - and the Internal Agent configur…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Parahelp
   Fin~partialprobed4/10

   Fin exposes an Agent API, Node SDK, MCP, webhooks, and data-connector APIs for programmatic interaction, but there is no evidence of full UI/API parity — no OpenAPI spec was discoverable (404s on all candidate paths) and no documentation claims that every configuration (e.g., inbox setup, workflows, Procedures, escalation rules) manageable in the UI is also manageable via API. Missing for 10: comprehensive API reference/OpenAPI spec, explicit parity claims, evidence that admin/config UI actions (not just conversational/data actions) are API-accessible.

   • [claimed-docs] “Fin can be accessed programmatically via an API. You call Fin from your o”
   • [claimed-docs] “The new orchestration endpoints — Discover capabilities, Ask Fin, Run a procedure, and Escalate to a human — are currently available in the …”
   • [github] “The Intercom TypeScript library provides convenient access to the Intercom APIs from TypeScript.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fin.ai/openapi.json, https://fin.ai/swagger.json, https://fin.ai/api/openapi.json, https://f…”
   • [claimed-docs] “The Fin API platform includes APIs for answer generation and knowledge retrieval, available as a set or independently.”

   proof ↗⚑ flag

   Parahelp~partialprobed5/10

   Parahelp documents API access for core operational tasks—receiving customer requests via API (docs-13, docs-20) and running the Internal Agent's automations via API (docs-14, docs-22)—and a live API reference exists (parahelp-probe-rt-2). However, no evidence shows that configuration authoring, simulation/testing, release management, or knowledge-diff review (all UI-centric per docs-1/2/4/9) can be done via API, and no discoverable OpenAPI spec was found (parahelp-probe-2 shows 404s across standard paths). Missing for 10: API parity for configuration/build workflows, testing/simulation via API, release/rollback via API, formal OpenAPI spec confirming full surface coverage.

   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”
   • [claimed-docs] “let the Internal Agent act without waiting for approval, and run it from your own tools via the API.”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system.”
   • [claimed-docs] “run it from your own tools via the API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.parahelp.com/openapi.json, https://docs.parahelp.com/swagger.json, https://docs.parahel…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public API reference at https://app.parahelp.com/api/docs is reachable keylessly — no login wall in…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Fin
   Fin~partialclaimed2/10

   The only export-related evidence is a narrow feature to 'Export a saved View exactly as you see it,' not a comprehensive data export mechanism; migration language found in the evidence is framed only around bringing data INTO Intercom from other helpdesks, not exporting all data out in open formats. Missing for 10: bulk/full account data export, documented open file formats (CSV/JSON), a migration-out or offboarding process, and any independent confirmation of successful full data extraction.

   • [claimed-docs] “Export a saved View exactly as you see it”
   • [claimed-docs] “bring your team over from any helpdesk without losing your content, your history, or a single day of support.”
   • [claimed-docs] “bring your team over from any helpdesk without losing your content, your history, or a single day of support”

   proof ↗⚑ flag

   Parahelp—none0/10

   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.

   ⚑ flag

Pricing

1. support leaderPricing is outcome-based and published — I pay per resolution with caps and controls, not an opaque enterprise quote

   weight 2 · round to Fin
   Fin~partialcommunity4/10

   A community source states Fin charges '$1 per successful customer session', which is consistent with outcome-based, per-resolution pricing, and a dedicated fin.ai/pricing page exists (cited repeatedly for feature lists). However, none of the evidence shows the actual published rate table, caps, or usage controls on that pricing page — the citations only reference features (integrations, channels, AI Agent capabilities), not price mechanics or caps. Missing for 10: first-party documentation of the per-resolution rate/caps/controls on fin.ai/pricing, and independent corroboration beyond a single HN comment.

   • [community] “Fin charges $1 per successful customer session, incentivizing it to be helpful; at the time of an earlier interview Fin was reportedly still…”
   • [claimed-docs] “Fin AI Agent works seamlessly with any helpdesk, including Salesforce, HubSpot, and more.”

   proof ↗⚑ flag

   Parahelp—none0/10

   No evidence anywhere in the pack of published pricing, per-resolution billing, caps, or outcome-based pricing controls — evidence is entirely about product functionality (agents, guardrails, integrations), not commercial terms.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Fin—none0/10

   The evidence pack contains extensive documentation on Fin's features, integrations, and compliance messaging (e.g., 'meet the world's leading compliance standards') but no mention of data residency, region selection, or storage location controls anywhere in the docs or community evidence.

   ⚑ flag

   Parahelp—none0/10

   No evidence of data residency or region selection options; only related mention is disabling personal data storage entirely, not choosing storage region. Missing for 10: any mention of region/residency controls, data center location choices, or geographic compliance options.

   • [claimed-docs] “Workspace admins can disable all personal data storage in the platform if they do not want Parahelp to retain this data.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Parahelp
   Fin—none0/10

   No evidence in the pack addresses data being used for AI model training or an opt-out/data-use control; general trust/compliance mentions (e.g., trust-reliability page) do not specify training data usage or opt-out mechanisms.

   ⚑ flag

   Parahelp~partialclaimed4/10

   Parahelp only offers a data-retention control (admins can disable personal data storage) but no explicit statement about excluding customer data from AI model training. missing for 10: explicit no-training-on-customer-data guarantee, opt-out toggle for model training, third-party/independent confirmation of training data handling.

   • [claimed-docs] “Workspace admins can disable all personal data storage in the platform if they do not want Parahelp to retain this data.”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Parahelp
   Fin—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or user-facing controls over how long data is kept or when it is deleted; the docs cover integrations, channels, MCP access, and training but never retention/deletion settings.

   ⚑ flag

   Parahelp~partialclaimed6/10

   Parahelp's security docs state that workspace admins can disable all personal data storage, giving explicit control over retention, but there is no documented deletion mechanism (e.g., data export/erasure API, retention period settings) beyond this single toggle. missing for 10: explicit data deletion/export controls, granular retention period settings, independent confirmation of the disable-storage feature.

   • [claimed-docs] “Workspace admins can disable all personal data storage in the platform if they do not want Parahelp to retain this data.”
   • [claimed-docs] “Role-based access across the product.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Fin—none0/10

   No evidence pack items mention telemetry opt-out, usage tracking controls, or privacy settings for Fin; only trust/compliance marketing language and unrelated docs are present.

   ⚑ flag

   Parahelp—none0/10

   Evidence shows a workspace-level admin control to disable personal data storage, but nothing about opting out of telemetry/usage tracking for the product itself as an AI-native/dev-tool user; missing for 10: any telemetry opt-out setting, docs on analytics collection, or user-level tracking controls.

   • [claimed-docs] “Workspace admins can disable all personal data storage in the platform if they do not want Parahelp to retain this data.”

   proof ↗⚑ flag

Personalization

1. support leaderAnswers use the customer's live data — plan, order status, account history — not just generic help articles

   weight 2 · round to Fin
   Fin✓fullprobed7/10

   Docs show Fin connects to live business data via data connector templates (Stripe, Shopify, Statuspage), MCP/API data connectors, webhooks, and CRM integrations (Salesforce, HubSpot, Zendesk) that surface data like plan/order status directly in the inbox, plus Procedures that let Fin execute multi-step logic against third-party systems to update/retrieve real account data rather than just canned articles. Missing for 10: independent/hands-on verification that live data grounding actually improves accuracy in practice, and no case study quantifying resolution based specifically on live account/order data vs. help-article content.

   • [claimed-docs] “Data connector templates are now generally available, with ready-to-install templates across Stripe, Shopify and Statuspage.”
   • [claimed-docs] “Track data connector health over time”
   • [claimed-docs] “Takes action to update external systems”
   • [claimed-docs] “See everything in one view in the inbox — pull in data from tools like Shopify and Stripe alongside the conversation, so agents never have t…”
   • [claimed-docs] “Surface data from Salesforce, HubSpot, and 450+ apps and integrations directly in the inbox”
   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”
   • [claimed-docs] “MCP is a protocol that enables AI tools and applications to securely access and interact with your Intercom data whenever helpful.”
   • [probe] “official MCP server documented at https://developers.intercom.com/docs/guides/mcp”

   proof ↗⚑ flag

   Parahelp~partialclaimed6/10

   Docs show the Customer Agent can connect tools to any API (Stripe, internal endpoints) and both agents share connections, which enables pulling live account/order data rather than just static knowledge articles, but no concrete example or case study shows it actually surfacing plan/order-status/account-history data in an answer. missing for 10: a documented example or customer case showing live account/order lookups in a real resolution, and specifics on how live data is merged into agent responses vs. knowledge base content.

   • [claimed-docs] “Tools can use any service with an API: public integrations like Stripe, or your own internal endpoints.”
   • [claimed-docs] “Connect a tool once, and both agents can use it”
   • [claimed-docs] “Anyone can build tools for the Customer Agent without waiting on engineering.”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”

   proof ↗⚑ flag

Reasoning

1. support leaderThe agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer

   weight 2 · round to Fin
   Fin~partialcommunity6/10

   Fin's docs describe 'Procedures' that train it to handle multi-step queries with business logic across systems, and marketing claims it 'handles multi-step queries end to end,' supporting structured troubleshooting rather than single canned replies. However, no evidence explicitly documents Fin asking clarifying questions mid-conversation, and one HN commenter argues open-ended agentic reasoning is unnecessary versus deterministic workflows, adding some uncertainty. missing for 10: explicit documentation/example of clarifying-question behavior, independent hands-on proof of multi-step troubleshooting quality.

   • [claimed-docs] “Procedures let you train Fin to handle queries with multiple steps, business logic and third-party systems from start to finish.”
   • [claimed-docs] “Fin resolves 76% of customer queries on average, and handles multi-step queries end to end. Your customers get fast, accurate answers. Your …”
   • [claimed-docs] “Giving Fin Guidance”
   • [community] “A commenter with a decade of customer-service AI/NLP experience argued 99% of support tasks (order status, returns, troubleshooting) are ful…”

   proof ↗⚑ flag

   Parahelp—none0/10

   The evidence pack covers configuration, guardrails, approvals, integrations, and knowledge versioning, but nothing describes the Customer Agent's actual conversational behavior—no mention of it asking clarifying questions or performing multi-step troubleshooting dialogue rather than a single scripted reply.

   ⚑ flag

Resolution

1. support leaderThe agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces

   weight 3 · round to Fin
   Fin✓fullcommunity7/10

   Fin explicitly claims a resolution metric ("Fin resolves 76% of customer queries on average, and handles multi-step queries end to end") across multiple integration pages, plus dedicated testing/evaluation tooling ("evaluate every live conversation") and analytics (Insights, Monitors) framed around resolution outcomes rather than deflection. Community commentary raises philosophical skepticism about autonomous agents vs. deterministic workflows, but does not concretely contradict the stated resolution rate. Missing for 10: independent/third-party audit of the 76% figure, and clear definition distinguishing 'resolution' from deflection/bounce in the metric methodology.

   • [claimed-docs] “Fin resolves 76% of customer queries on average, and handles multi-step queries end to end. Your customers get fast, accurate answers. Your …”
   • [claimed-docs] “Perfect customer experiences no longer come with a migration project. Fin resolves 76% of customer queries on average... Your team stays on …”
   • [claimed-docs] “Perfect customer experiences no longer come with a migration project... Your team stays on HubSpot.”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation... …”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”
   • [claimed-docs] “With Insights, Monitors New, and Recommendations, you have everything you need to understand, measure, and improve your customer experience”
   • [community] “A commenter with a decade of customer-service AI/NLP experience argued 99% of support tasks (order status, returns, troubleshooting) are ful…”

   proof ↗⚑ flag

   Parahelp~partialclaimed3/10

   Docs describe the Customer Agent handling tickets end-to-end with tools/guardrails and note integrations 'resolve tickets across email, live chat, and Slack,' implying resolution capability, but there is no quantified resolution rate, case study, or benchmark distinguishing true resolutions from deflections/bounces. Missing for 10: measured resolution-rate metrics, customer case studies with numbers, and independent verification of end-to-end resolution vs. escalation rates.

   • [claimed-docs] “Your Customer Agent works as a team member in Intercom, Zendesk, Front, Plain, or Pylon.”
   • [claimed-docs] “Parahelp now integrates with Pylon! ... their agents resolve tickets across email, live chat, and Slack”
   • [claimed-docs] “Customer requests come in through the API instead of a ticketing system. Your Customer Agent handles them with the same configurations, tool…”

   proof ↗⚑ flag

Voice

1. support leaderI control the agent's tone and brand voice, and it stays consistent across topics and languages

   weight 1 · round to Fin
   Fin~partialclaimed6/10

   Docs support tone/brand control ("Customizable tone and answer length", "Train Fin on your knowledge, data, policies, and tone of voice") and multi-language support is documented ("Use Fin AI Agent in multiple languages"), plus multi-channel consistency claims (email, Slack, live chat, voice) suggest tone carries across surfaces. However, there is no independent evidence or hands-on validation that tone/brand voice actually stays consistent across topics and languages in practice — only vendor marketing claims. Missing for 10: independent/third-party validation of tone consistency, concrete examples of cross-language tone fidelity, and evidence of consistency across many topics rather than just a training feature description.

   • [claimed-docs] “Customizable tone and answer length”
   • [claimed-docs] “Train Fin on your knowledge, data, policies, and tone of voice.”
   • [claimed-docs] “Train Fin on your knowledge, data, policies, and tone of voice. Fin will use everything it knows to deliver consistent, accurate answers”
   • [claimed-docs] “Use Fin AI Agent in multiple languages”
   • [claimed-docs] “Fin for messenger brings the highest-performing AI Agent for customer service to live chat, delivering exceptional, on-brand support”
   • [claimed-docs] “Fin delivers unrivaled performance across every channel. Wherever customers reach out, Fin provides fast, accurate, personalized support”

   proof ↗⚑ flag

   Parahelp—none0/10

   The evidence covers configuration via natural language, knowledge base versioning, guardrails, and tool integrations, but nothing addresses tone/brand-voice control or consistency across topics and languages. Missing for 10: any documentation or claim about persona/tone settings, brand voice configuration, or multilingual consistency testing.

   ⚑ flag

Qa

1. support ops leadAI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent

   weight 1 · round to Fin
   Fin✓fullclaimed7/10

   Fin ships explicit QA tooling: fin.ai/testing describes testing across thousands of scenarios before launch and evaluating every live conversation, fin.ai/analyze describes Insights, Monitors, and Recommendations continuously analyzing every conversation, and pricing docs list Custom AI Scorecards and Incident Detection alongside guidance and procedure-editing docs that let fixes feed back into the agent behavior. missing for 10: independent or hands-on verification of the scoring and review loop, and detail on how flagged failures are routed to specific fixes.

   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation... …”
   • [claimed-docs] “Insights continuously analyzes every Fin and human conv”
   • [claimed-docs] “With Insights, Monitors New, and Recommendations, you have everything you need to understand, measure, and improve your customer experience”
   • [claimed-docs] “Operator, CX Score, AI Topics, Trends, AI Recommendations, Monitors, Custom AI Scorecards, Incident Detection”
   • [claimed-docs] “Giving Fin Guidance”
   • [claimed-docs] “Building Fin Procedures”

   proof ↗⚑ flag

   Parahelp~partialclaimed5/10

   Parahelp offers simulation-based testing before release (docs-2), release tracking/revert (docs-4), and automations that 'watch your tools and support queue and surface gaps' (docs-17), which map loosely to a QA/review loop feeding fixes back. However there is no evidence of a structured scored-sample QA program, explicit failure flagging on live conversations, or a dedicated review dashboard for support-ops to audit agent conversations. Missing for 10: scored sampling of live conversations, explicit failure-flag workflow, dedicated QA review UI/report distinct from gap-detection automations.

   • [claimed-docs] “Simulations replay your historical tickets - or mock scenarios - against the configurations in the task, and production tests verify your to…”
   • [claimed-docs] “Configuration actions publish as a release on the Releases page, where you can track the impact and revert with one click.”
   • [claimed-docs] “Set up automations that watch your tools and your support queue and surface gaps on their own.”
   • [claimed-docs] “See your live knowledge and its version history - who published what and when, with a diff for every change”

   proof ↗⚑ flag

Simulation

1. support ops leadI test the agent against historical tickets or simulated conversations before it faces real customers

   weight 2 · round to Parahelp
   Fin✓fullclaimed7/10

   Fin has a dedicated testing capability documented at fin.ai/testing ("test it across thousands of scenarios before anything goes live") and a specific help article "How to preview and test Fin," directly matching the support-ops need to validate the agent before it faces customers. Missing for 10: independent/hands-on corroboration of the testing workflow and explicit mention of importing historical ticket transcripts as test scenarios rather than only generic 'scenarios'.

   • [claimed-docs] “How to preview and test Fin”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation”
   • [claimed-docs] “you test it across thousands of scenarios before anything goes live, roll out changes with control, and evaluate every live conversation... …”
   • [claimed-docs] “Train Fin on your Procedures, knowledge, and policies, test performance before launch, deploy across every channel, then analyze and improve…”

   proof ↗⚑ flag

   Parahelp✓fullclaimed8/10

   Docs explicitly describe simulations that replay historical tickets or mock scenarios against configurations, plus production tests to verify tool connections, directly matching the story of pre-launch testing before facing real customers. Missing for 10: no independent/hands-on corroboration of simulation accuracy or third-party validation of the testing workflow.

   • [claimed-docs] “Simulations replay your historical tickets - or mock scenarios - against the configurations in the task, and production tests verify your to…”
   • [claimed-docs] “the Internal Agent analyzes your last 500-1,000 resolved tickets along with your existing context to build the first version of your Custome…”

   proof ↗⚑ flag