AI customer service with targeted knowledge, authenticated data lookups, multi-step Procedures, human handoff, and optional Operator.
Fin by Intercom
Explore features, practical uses and pricing below.
Fin by Intercom is an AI customer-service agent that answers questions from configured knowledge and can carry out support processes through connected tools. Teams can deploy it with Intercom or supported existing help desks, define when it should hand a conversation to a person, and inspect the resulting support work. Its current scope extends beyond finding a help article: Data Connectors provide account-specific information, Procedures organize multi-step processes, and the optional Fin Operator helps maintain the setup.
Fin is useful for support teams with recurring questions, documented policies, and a clear escalation route. A customer might ask how a feature works, request an order update, or need help with an account process. The team determines the content, eligible actions, audience rules, and approval requirements. Those decisions shape what Fin can do for a particular customer.
The Fin overview describes answers built from configured sources such as help-center material, internal articles, PDFs, and webpages. The content workspace gives a team a central place to manage the information used by the agent. Relevant material from more than one source can contribute to an answer.
Organize sources around the questions customers actually ask. An explanation of a feature should include the product version, prerequisites, and steps a customer can follow. A policy article should state its applicable conditions. Clear text instructions are useful even when an article also contains screenshots, because the customer may ask about a detail that is only implied by the image.
For connected knowledge systems, the import and sync guide distinguishes ongoing synchronization from an imported copy. Synced material is edited in the source system; imported material is maintained in Fin. The setup also lets teams select content scope, destinations, and audiences before syncing.
Choose the destination carefully. An internal troubleshooting document might be suitable for a teammate's Copilot while containing information that should not be used in customer-facing answers. Review which content is enabled for Fin and which is intended for internal assistance rather than treating every connected document as public support knowledge.
Fin audiences are reusable segments based on People and Company data. They can apply to content, guidance, Data Connectors, and other support configuration. A team might distinguish customers by plan, region, or brand so the answer uses the relevant information.
Untargeted material is available to everyone by default. This makes audience assignment important for a policy that only applies to one group. If a premium support procedure should be limited to eligible accounts, inspect both its targeting and the reliability of the account data used to identify that audience.
Audience rules are applied at the start of the conversation and do not change midway through it. Consider that behavior when a process changes an attribute during the conversation. An updated value should not be assumed to alter the already-selected audience. Use explicit Procedure logic where a decision depends on newly collected information.
Test the experience with realistic user profiles. A question that has a correct answer for one market can still be wrong for another. Use source-level audience rules for connected material where available, then verify the result for customers who match several conditions or have missing attributes.
Fin Guidance lets teams define communication style, clarification behavior, and preferred content sources. These settings serve different purposes. A style instruction can set tone, while a clarification instruction can identify information Fin needs before answering. Content guidance can point toward a particular enabled source.
Write one clear purpose per instruction. If a support question depends on the product version, tell Fin what it should clarify and why that information matters. If a policy article is authoritative for a particular topic, reference the actual source. Avoid a broad rule that combines tone, eligibility, escalation, and several unrelated actions.
The best-practices guide explains that separate guidance entries do not form a chain of workflow steps. Guidance is evaluated as applicable, so a process requiring a defined sequence belongs in a Procedure. It also cautions against asking for resources that do not exist in the configured content.
When a source should never be used for a customer, remove it from Fin's availability or assign the correct audience. A prose instruction to avoid the source is a weaker way to enforce that boundary. Keep the content settings and guidance aligned so the agent does not receive conflicting directions.
Data Connectors configure API calls to external systems. They can provide information such as order status or account details that a general help article cannot supply. The editor separates API configuration, returned data, Fin's use of the connector, and security settings.
A connector needs more than a working endpoint. Define which customer identifier is passed, which returned fields are relevant, and how the response should be interpreted. An order-status tool should distinguish an unknown order from a known order whose shipment has not started. A failed lookup should not become a confident statement that no order exists.
Fin's documentation requires configured user authentication before a connector is set live for users. Review the identity route and access scope with the person responsible for the backend. A customer should receive information for their own account, and the connector should expose only the data needed for the support task.
Start with a read-only lookup when that meets the requirement. If the process also changes data, identify the eligibility condition and the point where the customer or a teammate confirms the action. Keep error and empty-response handling visible in the Procedure that uses the connector.
Fin Procedures combine instructions, tools, and business logic for more involved conversations. A connector can answer one account-specific question; a Procedure can organize several steps, such as gathering information, checking eligibility, and completing a defined process.
The Procedure Builder can prepare a draft from a described process or a template. Teams can review the draft, add conditions, call connectors, use attributes, and configure handoff. Procedures have their own access requirements, and availability should be confirmed for the workspace.
For a subscription change, define the information Fin must collect, the policy it should apply, and the actions it may perform. Include a branch for an account that does not meet the policy and a route for a failed lookup. Use the actual handoff tool when the conversation must move to a team; mentioning handoff in explanatory prose does not by itself implement routing.
Procedure logic has specific limitations. The current builder guide describes restrictions on nested conditions and on mixing code with natural-language logic within a condition. Data Connector outputs also have a particular scope inside a Procedure. Review these details when designing a process that must persist information or transfer to another workflow.
The human-approval step can pause a Procedure while a decision is requested through an external system and returned through a webhook. It is useful for an exception or another action that requires a person to approve before the process continues.
Define what the approver receives and what response permits the next action. Include enough context to decide without exposing unnecessary customer information. Also specify the wait period and the route taken if no decision returns. Test both approval and rejection, including a late or malformed response.
Procedure versions distinguish unsaved changes, saved drafts, and live configuration. Saving a draft does not change the version used in customer conversations. The version history records previously live configurations and supports reviewing or restoring a prior setup.
This gives a support team a practical release process. Edit the draft, test the changed branches, review the intended effect, and set the version live when ready. Keep a short note explaining why the change was made so a later operator understands whether it corrected a policy, a connector, or conversation behavior.
The testing comparison distinguishes Previews, Batch tests, and Simulations. Preview is interactive and useful while building. Batch tests compare answers across a group of questions. Simulations evaluate a Procedure against configured success criteria and branches.
Use Batch tests to check knowledge coverage and answer behavior across realistic questions. They do not execute the full end-to-end Procedure. Ratings help people review the results; rating an answer does not itself train Fin. Audience-specific escalation testing also needs attention to the limits described in the preview guide.
Simulations do not call live external APIs. That makes them useful for checking logic without changing real records, but it also means a passing simulation does not prove a production connector is configured correctly. Preview can use live data for a selected user, so choose test accounts and expected actions deliberately.
Finish with the supported channel's live-testing path. An email thread and a chat conversation have different presentation and timing. Confirm that the deployed experience, handoff route, and customer-facing introduction behave as intended in the actual channel.
Fin supports several channels and integrations, with the specific setup depending on the deployment. It can operate with Intercom or supported existing help desks. Check the integration guide for the particular platform rather than assuming every help desk uses the same ticket states or routing behavior.
Escalation rules and guidance determine when Fin should hand a conversation to a person. Workflows determine what happens afterward. A support team should configure both: recognizing an escalation is useful only if the next team receives the conversation and can act on it.
For example, Freshdesk handoff documentation explains that Fin clears itself as responder and opens the ticket, while the help desk's routing determines the receiving group. The organization must make sure a suitable routing rule and available teammate exist.
In a supported HubSpot deployment, Fin uses documented properties and tags to track its involvement and ticket handling. Review those states before building downstream automations. A tag representing a particular stage in Fin's handling should not be given an unrelated business meaning.
Fin Operator is an optional operational agent available through the Pro add-on. It can analyze support work, investigate conversations, and propose changes to content, guidance, or Procedures. The proposal system presents changes for review before they go live.
A knowledge manager can provide an approved product update and ask Operator to find affected material. The knowledge-management guide describes proposed edits across articles and snippets. Review each change against the approved source, especially when several policies use similar terminology.
For an incorrect answer, conversation debugging can inspect the transcript, source use, and Procedure trace, then suggest a remedy. This helps distinguish a missing article from a conflicting instruction or an unexpected tool result. Apply the change that addresses the cause, then test a similar conversation again.
Operator access and usage have their own requirements. Current documentation describes a paid Pro add-on, appropriate permissions, and an allowance of Operator credits. Include those requirements when evaluating an operational maintenance workflow rather than treating Operator as part of every basic Fin setup.
Suppose an ecommerce support team wants Fin to answer delivery-status questions. Connect the authenticated order lookup, select the fields needed for the answer, and provide the approved shipping policy. The normal route can explain the current status and the customer's next step.
Add branches for an unknown order, an unavailable API, and a status that needs investigation. If the customer requests an exception, use a Procedure to collect the relevant details and check the policy. A human-approval step can handle an exception requiring authorization, while a handoff gives the specialist team the conversation when the automated route cannot complete it.
Test the common question, an ambiguous request, and the exceptional paths. Review the actual account data in a controlled preview, then check the channel's live experience. After deployment, inspect failures and handoffs to see whether the issue belongs in the knowledge, connector, or Procedure configuration.
Fin pricing is based on defined outcomes, with commercial requirements depending on whether it is used with Intercom or an existing help desk. Intercom plans can include seat charges, while existing-help-desk access can involve minimum commitments or a base arrangement. Confirm the current account quote and any add-ons.
The outcome guide distinguishes a resolution from a configured Procedure handoff that counts as a completed outcome. Resolutions can be confirmed or assumed according to documented conversation behavior. Review these definitions alongside support-quality reports rather than equating every billable outcome with an explicitly satisfied customer.
Usage notifications and hard limits help manage consumption. Scope the expected channels, conversation volume, Procedures, and Operator usage before estimating cost. A time-limited trial is useful for evaluation; continued production access is paid.
Does Fin require a help-center article for every question? It can use several configured knowledge sources and Data Connectors. The relevant information still needs to exist and be available to the applicable customer audience.
Can it perform account actions? Supported Procedures and authorized tools can perform defined processes. Configure identity, eligibility, errors, and approval for the particular action.
Does a simulation test the live API? No. Simulations test Procedure logic without live API calls. Use the documented Preview and channel-testing paths for the remaining integration checks.
Is Fin Operator included everywhere? It requires the current paid Pro add-on and relevant access, with separate usage allowances.
What should a first rollout cover? Start with well-documented questions and a reliable human handoff, then add account-specific lookups and reviewed Procedures as the team establishes the required data and policy controls.