Fin vs Pylon

Actions

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

   weight 3 · round to Fin
   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

   Pylon~partialprobed5/10

   Pylon documents that AI agents can 'take action' and that admins can define Custom API tools so agents can hit internal or third-party API endpoints (e.g., a company's own refund/order APIs), and that Pylon's own API/MCP integration uses OAuth authentication for issues/accounts/contacts. However, there's no concrete example or documentation of granular, action-level scoped auth (e.g., distinct permission scopes for 'refund' vs 'subscription update') — the OAuth scoping described applies to Pylon's own data objects, not to arbitrary external business APIs the agent might call. Missing for 10: explicit examples of refunds/order/subscription actions being executed, and documentation of per-action auth scoping for custom API tools beyond general OAuth.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “Using a combination of Webhooks, API, and/or Pylon MCP, you can connect your agent to ticketing workflows in Pylon.”
   • [claimed-docs] “If a system does not provide an MCP server, an administrator can define a Custom API tool that agents can use to hit internal or third party…”
   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the first-party MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.usepylon.com ans…”

   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

   Pylon~partialclaimed6/10

   Pylon's Runbooks feature lets ops leads write natural-language, step-by-step instructions for the AI Support Agent to follow for specific scenarios, and Skills provide reusable instructions for consistent handling of known workflows — directly matching the SOP-encoding need. However, the docs describe these as natural-language guidance rather than an explicit deterministic branching/decision-tree engine, and Triggers/automations are a separate rule system not tied to agent SOPs. Missing for 10: explicit conditional/branching logic constructs within runbooks, and evidence of deterministic (non-LLM-interpreted) path selection.

   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”
   • [claimed-docs] “Build your swarm of AI Agents to help augment your team.”
   • [claimed-docs] “Set up complex workflows and automations to execute your business processes”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round drawn
   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

   Pylon✓fullprobed8/10

   Probes confirm a live llms.txt index at docs.usepylon.com/llms.txt and working per-page .md mirrors (e.g. pylon-mcp.md), so an agent can be pointed at agent-oriented docs and consume them directly. missing for 10: independent third-party confirmation beyond the vendor's own probe, and some per-page md endpoints (e.g. pylon-docs.md) 404 showing coverage is inconsistent.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.usepylon.com/llms.txt # Pylon ## Pylon - [Introduction](https://docs.usepylon.com/pylon-docs/gett…”
   • [probe] “PROBE runtime (recorded 2026-09-10): Pylon's docs are agent-legible — https://docs.usepylon.com/pylon-docs/llms.txt serves a live '# Pylon' …”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.usepylon.com/pylon-docs.md # Page Not Found The URL `pylon-docs` does not exist. This page may have…”

   proof ↗⚑ flag

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

   weight 2 · round to Fin
   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

   Pylon~partialprobed5/10

   Pylon exposes a REST API, webhooks, and triggers that allow programmatic, non-UI interaction with the platform, which supports automation-style usage outside the web UI (pylon-docs-31, pylon-docs-32, pylon-docs-30, pylon-probe-rt-2). However there is no evidence of a CLI, headless mode, or explicit CI/CD integration story — the product is a SaaS support platform accessed via API/OAuth, not something designed to be invoked in a CI pipeline. Missing for 10: explicit CLI/headless execution mode, CI/CD pipeline examples or docs, evidence of automated/scripted runs outside a live SaaS API context.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [claimed-docs] “Set up complex workflows and automations to execute your business processes”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”

   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

   Pylon~partialclaimed5/10

   Pylon's agent 'connectors' documentation states that if a third-party system provides an MCP server, agents can use it directly (falling back to a Custom API tool only when none exists), indicating Pylon can consume external MCP servers as tool sources for its AI agents. However, this is a single thin doc line with no setup walkthrough, supported-server list, or hands-on/runtime confirmation of actually connecting to a third-party MCP server. missing for 10: a dedicated 'add MCP server' configuration flow/UI, documentation of supported transports/auth for third-party servers, and independent or runtime evidence of a working third-party MCP connection.

   • [claimed-docs] “If a system does not provide an MCP server, an administrator can define a Custom API tool that agents can use to hit internal or third party…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Pylon
   Fin✓fullprobed8/10

   Intercom publishes official docs for an MCP server that lets AI agents securely access and interact with Intercom data, and this is corroborated by a dedicated probe confirming the documented endpoint plus Fin's own integrations page referencing MCP connectivity. missing for 10: independent/hands-on confirmation of the MCP server working in practice beyond vendor docs, and clearer detail on scope/auth setup.

   • [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.”
   • [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…”
   • [probe] “official MCP server documented at https://developers.intercom.com/docs/guides/mcp”

   proof ↗⚑ flag

   Pylon✓fullprobed9/10

   Pylon is a customer-support platform (not itself an agent), and it ships a first-party MCP server documented at docs.usepylon.com/pylon-docs/integrations/pylon-mcp with OAuth 2.0 authentication, hosted at mcp.usepylon.com. Runtime probes independently confirm the server is live (proper 401/WWW-Authenticate challenge with oauth-protected-resource metadata), corroborating the docs beyond vendor claims. Missing for 10: no independent third-party hands-on report of an agent successfully completing a task via this MCP server.

   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [probe] “official MCP server documented at https://docs.usepylon.com/pylon-docs/integrations/pylon-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-10): Pylon's docs are agent-legible — https://docs.usepylon.com/pylon-docs/llms.txt serves a live '# Pylon' …”
   • [probe] “PROBE runtime (recorded 2026-09-10): the first-party MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.usepylon.com ans…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Fin—none0/10

   Evidence shows Fin has an API, Node SDK, and MCP server, but no official CLI tool is documented or referenced anywhere in the evidence pack.

   ⚑ flag

   Pylon—none0/10

   No evidence of an official Pylon CLI anywhere in docs, changelog, or probes; Pylon offers REST API, webhooks, and an MCP server but no CLI tool is mentioned. missing for 10: any mention of a CLI, CLI installation instructions, or CLI command reference.

   ⚑ flag

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

   weight 3 · round to Pylon
   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

   Pylon✓fullprobed8/10

   Pylon documents a public REST API (docs-31) and webhooks (docs-32), and runtime probes confirm the API is live and properly auth-gated (probe-rt-2). Docs also describe programmatic/agentic access patterns (Custom API tools, OAuth-based AI tool access via docs-34) reinforcing that the API is designed for agentic/programmatic drivers. missing for 10: no discoverable OpenAPI/swagger spec (probe-3 shows 404s across candidate paths) and no independent third-party corroboration of API robustness beyond Pylon's own docs.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.usepylon.com/openapi.json, https://docs.usepylon.com/swagger.json, https://docs.usepylo…”

   proof ↗⚑ flag

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

   weight 2 · round to Pylon
   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

   Pylon~partialprobed4/10

   Pylon's MCP integration uses OAuth 2.0 (via AuthKit) and the REST API requires Bearer tokens, so credentials are authenticated and gated (pylon-docs-34, pylon-probe-rt-1/2/3), and access is limited to 'the data you can see in Pylon,' giving a coarse form of least-privilege tied to the issuing user's own permissions. However there is no evidence of a dedicated mechanism to mint distinct, granularly-scoped API keys or OAuth scopes specifically for an agent (e.g., read-only vs write, per-object scoping) separate from a full user account's access. Missing for 10: documented ability to configure fine-grained scopes/permissions per API credential, evidence of agent-specific token restriction UI, and independent confirmation of least-privilege enforcement beyond basic auth gating.

   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [probe] “PROBE runtime (recorded 2026-09-10): Pylon's docs are agent-legible — https://docs.usepylon.com/pylon-docs/llms.txt serves a live '# Pylon' …”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the first-party MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.usepylon.com ans…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   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

   Pylon~partialprobed6/10

   Pylon exposes a documented REST API, webhooks, and an OAuth-secured official MCP server (confirmed live via runtime probes), which together let AI-native developers build integrations and agents against Pylon data. However, there is no evidence of traditional language-specific client SDKs (e.g., Python/Node packages) or an OpenAPI spec (probe found 404s for openapi/swagger endpoints), so 'SDK' support is really API+MCP+webhooks rather than packaged SDKs. Missing for 10: dedicated official SDK packages, publicly discoverable OpenAPI/swagger spec, independent developer corroboration of SDK usage.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the first-party MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.usepylon.com ans…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.usepylon.com/openapi.json, https://docs.usepylon.com/swagger.json, https://docs.usepylo…”

   proof ↗⚑ flag

9. 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

   Pylon✓fullclaimed7/10

   Pylon documents a dedicated webhooks feature for receiving events happening in Pylon, directly matching the story. missing for 10: no independent/hands-on corroboration of webhook delivery, no detail on event types/payload schema, or subscription management UI/API specifics.

   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [claimed-docs] “Using a combination of Webhooks, API, and/or Pylon MCP, you can connect your agent to ticketing workflows in Pylon.”

   proof ↗⚑ 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

   Pylon~partialclaimed6/10

   Pylon documents AI summarization of customer conversations synced to CRM accounts (Salesforce), AI-powered knowledge base features, and analytics dashboards, plus AI Support Agents that surface context and take action — all suggesting embedded AI insight generation. However, there's no dedicated 'insights' feature that proactively surfaces suggestions from the user's own data (e.g., trend detection, anomaly alerts) beyond conversation summarization and agent responses. Missing for 10: a first-party 'insights' or 'suggestions' dashboard feature explicitly generating recommendations from account/ticket data, and independent/hands-on validation of insight quality.

   • [claimed-docs] “Every day, Pylon scans your customer channels for conversations that were had. For every conversation, we use AI to summarize the details, a…”
   • [claimed-docs] “Pylon comes with a number of default analytics dashboards with common support metrics. All dashboards are filterable by a wide selection of …”
   • [claimed-docs] “A dedicated place to host your support content, including question-and-answer style articles, internal runbooks, and more -- all supercharge…”
   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Pylon~partialclaimed6/10

   Pylon documents triggers/automations to execute business processes, webhooks, API access, and AI agents that autonomously handle issues assigned to them with monitoring via issue logs, supporting background autonomous automation. However, evidence is mostly first-party docs with no independent/hands-on confirmation of unattended reliability or long-running autonomy at scale. Missing for 10: independent/hands-on verification of autonomous background execution, detail on failure handling/retries in triggers, and third-party confirmation of agent autonomy in production.

   • [claimed-docs] “Set up complex workflows and automations to execute your business processes”
   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Pylon✓fullclaimed8/10

   Pylon ships built-in AI Support Agents that users can build, assign to issues, give runbooks/skills, and monitor outcomes—clearly a built-in assistant users delegate tasks to (assign issues, define workflows, review AI-taken actions). Missing for 10: independent/third-party hands-on validation of assistant task quality and no user-facing UI screenshots/demos beyond docs.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “Build your swarm of AI Agents to help augment your team.”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Pylon~partialprobed6/10

   Pylon exposes a live first-party MCP server (confirmed by runtime probes) that lets AI tools authenticate via OAuth and read/update issues, accounts, and contacts, effectively letting an AI-native user drive Pylon via natural-language-mediated agent actions; runbooks and skills also let admins encode natural-language instructions for agent behavior. However, this is achieved through external AI-tool/agent integration rather than a native in-app NL command interface for end users. Missing for 10: evidence of a built-in chat/command-bar UI where a human directly issues natural-language commands to operate Pylon itself, and independent confirmation of real-world NL-driven task completion.

   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”
   • [probe] “PROBE runtime (recorded 2026-09-10): Pylon's docs are agent-legible — https://docs.usepylon.com/pylon-docs/llms.txt serves a live '# Pylon' …”
   • [probe] “PROBE runtime (recorded 2026-09-10): the first-party MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.usepylon.com ans…”
   • [claimed-docs] “Using a combination of Webhooks, API, and/or Pylon MCP, you can connect your agent to ticketing workflows in Pylon.”

   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

   Pylon—none0/10

   Pylon documents a REST API and webhooks (pylon-docs-31, pylon-docs-32) but there is no evidence of an interactive API reference with runnable/try-it examples — probes explicitly found no OpenAPI/Swagger spec at any candidate path (pylon-probe-3), only static markdown docs.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.usepylon.com/openapi.json, https://docs.usepylon.com/swagger.json, https://docs.usepylo…”

   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

   Pylon—none0/10

   Pylon has a REST API and docs, but explicit probes for OpenAPI/Swagger spec files at standard paths all returned 404, and no evidence anywhere shows a downloadable machine-readable spec (OpenAPI, JSON Schema, etc.) for its API.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.usepylon.com/openapi.json, https://docs.usepylon.com/swagger.json, https://docs.usepylo…”
   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”

   proof ↗⚑ flag

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

   weight 1 · round to Fin
   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

   Pylon~partialclaimed3/10

   Pylon's Support Agent docs mention a 'test' feature to simulate interactions with the AI without deploying it live (pylon-docs-17), which suggests some sandboxed testing before touching real customer issues, but there's no documented sandbox environment, staging API, or test dataset separate from production data. Missing for 10: explicit sandbox/staging environment, test API keys or test accounts isolated from production, and confirmation that simulated interactions don't touch real customer/production data.

   • [claimed-docs] “Simulate an interaction with the AI and see how it handles different questions.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”

   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

   Pylon—none0/10

   Evidence shows Pylon has a REST API, webhooks, and MCP server, but no documentation of API versioning scheme or a deprecation policy anywhere in docs/changelog; openapi spec probes 404 and no version headers or changelog entries reference API deprecations. Missing for 10: versioning scheme (e.g., v1/v2 paths), documented deprecation timeline/policy, changelog entries about breaking changes.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.usepylon.com/openapi.json, https://docs.usepylon.com/swagger.json, https://docs.usepylo…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”

   proof ↗⚑ flag

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

   weight 2 · round to Pylon
   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

   Pylon~partialprobed5/10

   Pylon's API (pylon-docs-31), MCP server (pylon-docs-34, pylon-probe-rt-1/3), and triggers/automations (pylon-docs-30) give AI agents and scripts programmatic read/update access to issues, accounts, and contacts, which could be used to script bulk changes, but no evidence describes a dedicated bulk-edit/bulk-action UI or batch-endpoint for acting on many items in one call. Missing for 10: an explicit bulk-update/bulk-action API or UI feature, and any documentation or demo of multi-item batch operations rather than single-record CRUD via API/MCP.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [claimed-docs] “Set up complex workflows and automations to execute your business processes”
   • [probe] “PROBE runtime (recorded 2026-09-10): Pylon's docs are agent-legible — https://docs.usepylon.com/pylon-docs/llms.txt serves a live '# Pylon' …”
   • [probe] “PROBE runtime (recorded 2026-09-10): the first-party MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.usepylon.com ans…”

   proof ↗⚑ flag

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

   weight 3 · round to Pylon
   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

   Pylon✓fullprobed8/10

   Pylon has a dedicated Triggers platform docs page describing setting up complex workflows/automations tied to business processes, plus webhooks for events and an API to programmatically act on data, enabling event-driven automated actions. This directly matches rule-based automation triggering actions on events, with runtime probes confirming the API/webhook infrastructure is live. Missing for 10: detailed trigger-rule syntax/examples, independent hands-on validation of complex trigger logic, and explicit AI-agent-specific trigger configuration beyond general workflow automation.

   • [claimed-docs] “Set up complex workflows and automations to execute your business processes”
   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   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

   Pylon—none0/10

   Pylon's docs mention 'triggers' for building automations and workflows (pylon-docs-30) plus API/webhooks for programmatic action, but nothing in the evidence pack specifies time-based or recurring scheduling (e.g., cron-like jobs, scheduled runs) as opposed to event-triggered automations. No mention of a scheduler, recurring job configuration, or interval-based execution.

   • [claimed-docs] “Set up complex workflows and automations to execute your business processes”
   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Pylon—none0/10

   Pylon has automations/triggers, agent runbooks, and issue logs for monitoring outcomes, but there is no evidence of version history, diffing, review workflows, or rollback capability for automations/triggers/skills/runbooks. Missing for 10: version history for triggers/runbooks, change review/approval process, rollback to a prior automation version.

   • [claimed-docs] “Set up complex workflows and automations to execute your business processes”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”

   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

   Pylon~partialclaimed5/10

   Pylon clearly supports one-agent omnichannel routing across chat, email, and in-app (chat widget, Slack, email integrations, omnichannel-support doc), but the evidence pack never explicitly documents WhatsApp or social-media channel integrations, which the story specifically calls out. missing for 10: explicit WhatsApp integration docs, explicit social media (e.g. Twitter/Instagram) channel support, and confirmation these route into the same unified agent workflow as chat/email/Slack.

   • [claimed-docs] “Pylon can support you wherever you interact with your customers.”
   • [claimed-docs] “Pylon watches for customer issues in connected customer Slack channels and automatically bundles together relevant messages and creates trac…”
   • [claimed-docs] “Connect your email addresses with Pylon to track and response to support requests over email.”
   • [claimed-docs] “Fully customizable colors, branding, and workflows * Multiple separate chat widgets with different branding and workflows”
   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”

   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

   Pylon—none0/10

   No evidence in the pack mentions multilingual support, language detection, translation of knowledge base content, or the AI agent responding in customer languages other than English; docs cover agent building, knowledge base, and integrations but never address language coverage.

   ⚑ 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

   Pylon—none0/10

   Pylon's evidence covers omnichannel support (chat, email, Slack), AI support agents, knowledge bases, and MCP/API integrations, but nothing describes voice/phone call handling with speech-in/speech-out capability. The omnichannel doc (pylon-docs-24) is generic and doesn't mention telephony or voice at all.

   ⚑ 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

   Pylon~partialclaimed5/10

   Pylon's AI agent operates within the same ticket/issue thread that a human later takes over, and the issue log records the agent's steps and outcomes (pylon-docs-19), while the agent explicitly gathers internal context for the team (pylon-docs-13) and elsewhere Pylon auto-summarizes conversations for CRM sync (pylon-docs-33), suggesting summarization capability exists. However, there is no explicit documentation of an escalation-specific handoff package (conversation + AI summary + structured collected details) being automatically attached to a ticket when an agent escalates to a human. missing for 10: explicit escalation-handoff feature docs, evidence the summary/details are surfaced to the human agent at hand-off time, confirmation customer doesn't need to repeat themselves.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Every day, Pylon scans your customer channels for conversations that were had. For every conversation, we use AI to summarize the details, a…”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”

   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 to Fin
   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

   Pylon~partialclaimed4/10

   Pylon's Support Agent framework lets admins write natural-language runbooks for 'specific scenarios' and assign only certain issues to the agent, plus monitor outcomes via the issue log — this could be used to script handoff conditions, but there is no explicit documentation of built-in triggers for topic, sentiment, or customer-tier-based escalation, nor any evidence about reliability/guardrails ensuring the agent 'reliably obeys' handoff rules. Missing for 10: dedicated sentiment/tier/topic escalation configuration UI, explicit-request handoff trigger documentation, and evidence (docs or hands-on) of enforcement reliability.

   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”
   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”

   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

   Pylon~partialclaimed3/10

   Pylon's Support Agent is grounded in a curated knowledge base and runbooks/skills that define scenario-specific instructions, which implicitly limits it to trained content rather than free invention, and 'deflect using content' suggests answers are content-bound. However, there is no explicit documentation of a safe-decline behavior for off-knowledge questions, confidence thresholds, or anti-hallucination guardrails around prices/policies. Missing for 10: explicit safe-decline/escalation mechanism for unknown questions, documentation of hallucination prevention, and evidence of guardrails specifically around prices/policies/promises.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”
   • [claimed-docs] “A dedicated place to host your support content, including question-and-answer style articles, internal runbooks, and more -- all supercharge…”

   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 drawn
   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

   Pylon—none0/10

   Pylon's docs describe agent deployment controls (assigning which issues the agent handles, testing/simulating responses, and an issue log for post-hoc review) but nowhere document a supervised 'draft-for-human-approval-before-send' mode; the language instead emphasizes agents 'taking action' autonomously once deployed.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Simulate an interaction with the AI and see how it handles different questions.”

   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 to Fin
   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

   Pylon~partialclaimed4/10

   Pylon documents assignment-based control—agents only interact with issues explicitly assigned to them, giving admins 'full control of which customer issues your AI agent interacts with'—which could be used to withhold sensitive categories from the agent, and runbooks/skills let you write natural-language handling instructions. But there is no documented feature for marking specific topics (legal threats, cancellations, security) as categorically human-only or any guardrail that blocks the agent from acting on flagged topic types. Missing for 10: an explicit topic/category exclusion or block-list mechanism, enforcement guarantees against agent 'freelancing' on excluded topics, and independent verification that assignment-based control reliably prevents agent action on sensitive categories.

   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”

   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 Pylon
   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

   Pylon~partialclaimed5/10

   Pylon docs confirm built-in analytics dashboards with 'common support metrics' filterable by attributes, supporting general resolution/ticket reporting, but no evidence explicitly names CSAT, handoff rate, or cost-per-resolution as tracked metrics. missing for 10: explicit documentation of CSAT scoring, handoff-rate metric, and cost-per-resolution calculation in dashboards.

   • [claimed-docs] “Pylon comes with a number of default analytics dashboards with common support metrics. All dashboards are filterable by a wide selection of …”

   proof ↗⚑ 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

   Pylon—none0/10

   Evidence shows generic analytics dashboards with filterable metrics (pylon-docs-29) and AI summarization of Slack conversations synced to Salesforce (pylon-docs-33), but nothing describes topic clustering of conversations or proactive surfacing of emerging product issues before ticket volume spikes.

   • [claimed-docs] “Pylon comes with a number of default analytics dashboards with common support metrics. All dashboards are filterable by a wide selection of …”
   • [claimed-docs] “Every day, Pylon scans your customer channels for conversations that were had. For every conversation, we use AI to summarize the details, a…”

   proof ↗⚑ flag

Helpdesk

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

   weight 3 · round to Fin
   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

   Pylon~partialclaimed3/10

   Evidence shows a one-way sync of AI-summarized conversations into Salesforce Accounts and general 'omnichannel' support language, but there is no evidence of the AI agent embedding inside Zendesk or Intercom, nor of two-way ticket/context syncing with any named helpdesk — Pylon's docs otherwise position it as the standalone system of record. Missing for 10: Zendesk/Intercom integration evidence, bidirectional ticket sync (not just one-way conversation summaries), and confirmation the agent itself operates 'inside' another helpdesk's UI/workflow.

   • [claimed-docs] “Every day, Pylon scans your customer channels for conversations that were had. For every conversation, we use AI to summarize the details, a…”
   • [claimed-docs] “Pylon can support you wherever you interact with your customers.”
   • [claimed-docs] “Using a combination of Webhooks, API, and/or Pylon MCP, you can connect your agent to ticketing workflows in Pylon.”

   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

   Pylon~partialclaimed4/10

   Pylon's knowledge base and training-data docs mention connecting external knowledge sources (pylon-docs-22, pylon-docs-23), and product-data sync can be disabled mid-run (pylon-docs-8), implying some sync mechanism exists, but there is no documentation of a re-sync schedule, change-detection triggers, or automatic re-indexing cadence for knowledge sources. missing for 10: explicit scheduling/frequency controls for knowledge source re-sync, change-detection or webhook-triggered re-sync of external knowledge, and any evidence contradicting or confirming this works hands-on.

   • [claimed-docs] “Make them even more powerful by connecting any external sources of knowledge you have!”
   • [claimed-docs] “A dedicated place to host your support content, including question-and-answer style articles, internal runbooks, and more -- all supercharge…”
   • [claimed-docs] “Disabling a product-data sync now stops any run already in progress”

   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 Fin
   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

   Pylon—none0/10

   Pylon documents training-data ingestion, a knowledge base, agent simulation/testing, and issue logs for reviewing agent outcomes, but nothing in the evidence describes a feature that proactively surfaces knowledge gaps or flags conflicting content driving agent misses. This is a fair axis for a support-agent platform (comparable products ship content-quality/coverage analytics), so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Simulate an interaction with the AI and see how it handles different questions.”
   • [claimed-docs] “Make them even more powerful by connecting any external sources of knowledge you have!”
   • [claimed-docs] “A dedicated place to host your support content, including question-and-answer style articles, internal runbooks, and more -- all supercharge…”

   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 drawn
   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

   Pylon~partialclaimed5/10

   Pylon's Support Agents are documented to answer/deflect using a dedicated Knowledge Base and connected external knowledge sources (pylon-docs-13, pylon-docs-22, pylon-docs-23), which supports grounding in the user's own content, but there is no evidence that responses explicitly cite or display which specific article/source was used to generate an answer. missing for 10: explicit citation/source-attribution UI in agent answers, evidence of per-answer source linking, independent confirmation of grounding accuracy.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “Make them even more powerful by connecting any external sources of knowledge you have!”
   • [claimed-docs] “A dedicated place to host your support content, including question-and-answer style articles, internal runbooks, and more -- all supercharge…”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”

   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

   Pylon~partialclaimed5/10

   Pylon documents a 'training-data' page for connecting external knowledge sources and a Knowledge Base feature for hosting support content and runbooks, suggesting some support for knowledge grounding, but there is no concrete evidence of automated ingestion of help center content, past tickets, or internal wikis without manual re-authoring. Missing for 10: explicit documentation of connectors for help center/docs platforms, wiki integrations (Confluence/Notion), automatic ticket-history ingestion, and any hands-on evidence confirming these sources sync without manual re-entry.

   • [claimed-docs] “Make them even more powerful by connecting any external sources of knowledge you have!”
   • [claimed-docs] “A dedicated place to host your support content, including question-and-answer style articles, internal runbooks, and more -- all supercharge…”
   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”

   proof ↗⚑ flag

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

   weight 2 · round to Pylon
   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

   Pylon~partialprobed5/10

   Pylon documents a public REST API and webhooks for programmatically accessing/acting on issues, accounts, and contacts (pylon-docs-31, pylon-docs-32, pylon-docs-4), plus an MCP server that lets AI tools read/update the same core objects (pylon-docs-34, pylon-probe-rt-3). However, there's no evidence the API/MCP surface covers the full breadth of UI capabilities shown in the changelog (custom object forms, analytics dashboards, chat widget branding/customization, knowledge base authoring, triggers/automation config) — these appear UI-only in the evidence pack. Missing for 10: documented API/MCP parity for analytics dashboards, chat widget customization, knowledge base management, and workflow/trigger configuration.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [claimed-docs] “Added a GET /task-statuses API endpoint for enumerating configured task statuses”
   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”
   • [probe] “PROBE runtime (recorded 2026-09-10): the first-party MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.usepylon.com ans…”

   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

   Pylon—none0/10

   Evidence shows a REST API and webhooks for programmatic access to issues/accounts/contacts, but nothing documents a bulk data-export feature, open-format dump, or data-portability/account-closure workflow that would let a user extract all their data and leave.

   • [claimed-docs] “Pylon's API can be used to programmatically access and take action on data within Pylon.”
   • [claimed-docs] “Receive webhooks for various events happening in Pylon.”
   • [probe] “PROBE runtime (recorded 2026-09-10): the public REST API at api.usepylon.com is live and cleanly auth-gated — a keyless GET returned HTTP 40…”

   proof ↗⚑ 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

   Pylon—none0/10

   No evidence anywhere in the pack of outcome-based or per-resolution pricing, published pricing tiers, caps, or usage-based billing controls; Pylon's documentation covers product features, agents, and APIs but is silent on pricing model or billing transparency.

   ⚑ 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

   Pylon—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or storage location options; only compliance/certification via Vanta is mentioned, which does not address data residency choice. Missing for 10: any mention of regional data centers, residency options, or ability to select storage location.

   • [claimed-docs] “Our compliance and certification are managed by Vanta and our incredible audit partners.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Pylon—none0/10

   Evidence pack mentions Pylon's compliance is managed via Vanta (SOC2-type certification) but there is no mention of any AI-training data opt-out, data usage policy for model training, or controls letting users prevent their data from being used to train AI models. Missing for 10: explicit AI-training opt-out/data-usage policy, contractual or product-level control preventing training use, and any documentation addressing this specific privacy concern.

   • [claimed-docs] “Our compliance and certification are managed by Vanta and our incredible audit partners.”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   Pylon—none0/10

   The evidence pack shows security/compliance certification via Vanta and general data handling but contains no documentation of data retention periods, deletion policies, or user/admin controls to delete or export data. Missing for 10: retention policy documentation, deletion/export controls, data lifecycle settings.

   • [claimed-docs] “Our compliance and certification are managed by Vanta and our incredible audit partners.”

   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

   Pylon—none0/10

   No evidence Pylon offers any telemetry opt-out or usage-tracking controls; evidence only covers compliance certification (Vanta) and product features, not telemetry settings.

   ⚑ 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

   Pylon~partialclaimed6/10

   Pylon documents product-data syncs, Account Fields, custom objects, and Connectors/Custom API tools/MCP that let AI Support Agents pull in live account/product data (e.g., pylon-docs-8, pylon-docs-21, pylon-docs-22, pylon-docs-33) rather than relying solely on the knowledge base, and Skills/Runbooks let agents act on that data during resolution (pylon-docs-13, pylon-docs-20). However there's no first-party or independent case study showing an actual generated answer citing live plan/order-status/account-history data in a real resolution. Missing for 10: concrete example/transcript of an AI answer referencing live order status or plan data, and independent verification that synced data is actually surfaced in agent responses rather than just accessible to admins.

   • [claimed-docs] “Disabling a product-data sync now stops any run already in progress”
   • [claimed-docs] “If a system does not provide an MCP server, an administrator can define a Custom API tool that agents can use to hit internal or third party…”
   • [claimed-docs] “Make them even more powerful by connecting any external sources of knowledge you have!”
   • [claimed-docs] “Every day, Pylon scans your customer channels for conversations that were had. For every conversation, we use AI to summarize the details, a…”
   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”
   • [claimed-docs] “AI tools authenticate with your Pylon account via OAuth and can read and update issues, accounts, and contacts within the data you can see i…”

   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

   Pylon~partialclaimed5/10

   Pylon's Support Agent docs describe multi-step behavior—runbooks with natural-language instructions for specific scenarios, skills as reusable workflow instructions, gathering internal context, and taking action—plus an issue log showing 'outcomes and steps taken by the AI' (pylon-docs-13, pylon-docs-15, pylon-docs-20, pylon-docs-19). However, there is no explicit documentation that the agent proactively asks clarifying questions to the customer rather than issuing a single canned reply; the story's core 'asks clarifying questions' behavior is only implied, not confirmed. Missing for 10: explicit product documentation or example of the agent asking clarifying follow-up questions mid-conversation, and independent/hands-on evidence of multi-turn troubleshooting flows in practice.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Simulate an interaction with the AI and see how it handles different questions.”

   proof ↗⚑ 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

   Pylon~partialclaimed3/10

   Pylon's own docs describe the Support Agent primarily in terms of 'deflecting' questions and taking actions, with an issue log to inspect outcomes/steps, but there is no first-party or independent metric quantifying full end-to-end resolutions distinct from deflections or bounces. missing for 10: quantified resolution-rate reporting, evidence distinguishing true resolutions from deflections, independent/customer validation of resolution outcomes.

   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Pylon comes with a number of default analytics dashboards with common support metrics. All dashboards are filterable by a wide selection of …”

   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

   Pylon~partialclaimed3/10

   Pylon's AI Agent can be configured with natural-language runbooks and reusable 'skills' that dictate how it handles specific scenarios, which could be used to encode tone/brand-voice guidance, but the docs never explicitly mention persona/tone control or consistency across languages. missing for 10: explicit tone/brand-voice configuration settings, evidence of multilingual consistency, and any customer/independent proof the agent's voice stays consistent across topics.

   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”
   • [claimed-docs] “Support Agents can deflect customer questions using content, gather internal context for your team, and take action.”

   proof ↗⚑ 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

   Pylon~partialclaimed5/10

   Pylon documents a monitor-and-iterate loop: a 'test' simulation mode to probe agent behavior, an issue log to inspect outcomes/steps taken by the AI, and runbooks/skills that let ops feed corrections back into the agent's instructions. However, there's no evidence of structured QA scoring of samples or a formal flagged-failure workflow with review states — it's more free-form inspection than a scored QA/review pipeline. Missing for 10: sample scoring/rubrics, dedicated failure-flagging workflow with reviewer roles, and quantitative QA metrics tied back to agent training.

   • [claimed-docs] “Simulate an interaction with the AI and see how it handles different questions.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”
   • [claimed-docs] “Skills are reusable instructions that teach Pylon agents how to handle specific workflows consistently.”

   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 Fin
   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

   Pylon~partialclaimed6/10

   Pylon's docs explicitly describe a test/simulate feature ('Simulate an interaction with the AI and see how it handles different questions') plus an issue log to inspect outcomes, which supports pre-deployment validation and monitoring. However, there's no explicit mention of testing against historical ticket datasets in bulk, regression testing, or scoring accuracy across a corpus of past conversations. missing for 10: bulk/historical-ticket backtesting workflow, quantitative accuracy/regression metrics from test runs, independent/hands-on confirmation of the simulate feature's depth.

   • [claimed-docs] “Simulate an interaction with the AI and see how it handles different questions.”
   • [claimed-docs] “You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent int…”
   • [claimed-docs] “The issue log allows you to inspect all the issues the AI agent is associated with and inspect the outcomes and steps taken by the AI.”
   • [claimed-docs] “Write instructions in natural language to help your AI Agent handle specific scenarios.”

   proof ↗⚑ flag