Use this article to understand what Fin Skills are, compare Skills with Procedures, create and configure your first Skill, test and deploy it, and check which Fin Skills features are available during the closed beta. To set up a Skill where Fin starts the conversation, see How to set up proactive outreach with Fin Skills.
Fin Skills are in closed beta. To request access to Fin Skills in the Intercom helpdesk, join the Fin Skills waitlist.
Fin Skills are a more agentic way to configure Fin to resolve complex, multi-step queries, without step-by-step authoring. Instead of prescriptive steps, you give Fin a set of tools plus a free-text goal, and Fin decides which tools to call, in what order, and when the job is done.
What is a Fin Skill?
A Skill gives Fin a set of tools — like your knowledge base, data connectors, attributes, tags, and handover targets — plus a short, free-text description of the goal for a particular process. When the Skill is triggered, Fin decides which tools to call, in what order, and when the job is done.
What does a Skill consist of?
Trigger — when Fin should use the Skill. Add any that apply: Customer sends a message (a description of what the customer says, trigger examples — "Use when" and "Do not use when", we recommend 10–20 — plus audience and channel targeting), Reach out proactively (Fin starts the conversation for people who match an audience, with up to 14 follow-ups), or Based on an event (started from the Inbox, a call, a website element click, or an API (application programming interface) call).
Available tools — data connectors Fin can call (Call data connector); content to prioritize, such as internal articles, public articles, and snippets (Prioritize content); teams, teammates, or reusable workflows to hand off to (Handoff to team, Run a workflow); attributes Fin may read or update; tags; Procedures (Run a procedure); Python code (Run code); and questions for a teammate (Loop in teammate / agent). Fin determines when to use these tools based on the instructions you provide.
Instructions — a free-form prompt where you describe the Skill's goal, any added guidance, and other context for Fin to follow
Guidance — the guidance categories that apply to this Skill (for example, Communication style or Escalation guidance). Selecting a category means the relevant workspace guidance rules shape how Fin behaves within the Skill. If a Skill's instructions conflict with workspace guidance, Fin follows the Skill. To choose guidance categories, select the settings (gear) icon at the top of the Skill editor, then open the Guidance tab.
What can Fin do within a Fin Skill?
When a Skill is triggered, the Skills Agent — the part of Fin that works out which tools to call, in what order, and when the job is done — takes over the conversation and executes the Skill autonomously. Once the Skill ends, Fin hands the conversation back to its default mode of answering questions from your knowledge base and other configured content. We call this default mode the general information agent, to distinguish it from the goal-driven Skills Agent that runs during a Skill. Within a Fin Skill, Fin can do all of the following:
Plan and track its own progress against the objective
Search content you've provided in the Skill
Call any data connectors you've made available
Message the customer, including asking follow-up questions
Hand off to a configured handover target, or escalate generically to a human, unless the Skill's instructions say not to
Declare the Skill complete and return the conversation to Fin
Search your knowledge base if the customer asks an informational question outside the Skill's scope
Generate Fin thoughts explaining what it's doing and why
Ask a teammate a question and wait for their answer before continuing
Run code you've added to the Skill
Update attributes you've allowed it to change
Send the customer an email
Close the conversation
How to choose between a Fin Skill and a Procedure
A Skill and a Procedure are two different ways to configure Fin, and we treat them as complementary rather than competing — you can use both in the same workspace. A Skill gives Fin a goal and a set of tools and lets Fin decide the path; a Procedure gives Fin a fixed, step-by-step script to follow. Both guide Fin in handling a conversation, but they suit different situations.
The table below compares Skills and Procedures across four dimensions — what each is best suited for, how you configure it, the setup effort involved, and how predictable Fin's behavior is.
How do Skills and Procedures compare at a glance?
| Skills | Procedures |
Best for | Open-ended goals where the conversation could go in different directions | Specific, well-defined cases that follow a set path |
How you set it up | Describe the goal and give Fin the tools it needs | Write out the steps Fin should follow, in order |
Setup effort | Lower. Less detail needed | Higher. You write out each step |
Behavior | More flexible, less predictable | More consistent, closer to a script |
When should you use a Fin Skill?
A Skill tells Fin what you want to achieve and lets Fin work out how to get there. Because you aren't scripting every step, Skills are quicker to set up.
Use a Fin Skill when:
You aren't sure what the customer will ask for or how the conversation will end.
You have a clear goal but no fixed path to it.
You want Fin to handle a conversation that may change direction partway through.
The outcome needs judgment and dynamic reasoning, like troubleshooting where the path is unclear.
There are many possible causes, and a Procedure would need a branch for every one.
What should you know before using a Fin Skill?
Fin has your full instructions and tools in view for the whole conversation, so it can respond sensibly when a customer changes topic or raises more than one issue.
Fin can move between different Fin Skills as the conversation evolves.
Because Fin decides how to reach the goal, its approach will vary more from one conversation to the next.
When should you use a Procedure?
A Procedure is a step-by-step walkthrough for a specific scenario — Fin follows the steps you write, in order, rather than deciding its own path. If you already have a written, step-by-step process your team follows, you can give it to a Procedure and Fin will carry it out.
Use a Procedure when:
The process is well-defined and should be done the same way each time.
You need Fin to follow a script closely.
The process is fixed, repeatable, and standardized.
What should you know before using a Procedure?
Procedures work best when the customer stays on the expected path.
Fin focuses on the part of the procedure it's currently working through rather than holding every step in mind at once. If a customer brings up something that relates to a different part of the procedure, Fin may not have that context.
Procedures are less suited to conversations where the customer raises several issues.
How to configure a Fin Skill
Skills can be created, edited, and tested using Operator (recommended) or manually in the product.
How to create a Fin Skill using Operator (recommended)
The fastest way to create, test, and deploy a Fin Skill is with Operator. You can get a first version working and ready to test within 15–20 minutes.
Explicitly ask Operator to create a Fin Skill and describe the goal you want it to handle.
Note: During the beta, Operator will only suggest Procedures by default — you need to explicitly ask it to create a Skill. Operator will draft the Skill in Fin AI Agent > Train > Skills, ready for you to review and test before setting it live.
After Operator drafts the Fin Skill, open it in the Skill editor and review its triggers, tools, and instructions. Then continue to How to test and deploy a Skill.
How to create a Fin Skill manually
How to build a Fin Skill from scratch
The Skill editor has three sections: Triggers, Tools, and Instructions. Work through them in order, then save the Skill.
Create the Skill. Go to Fin AI Agent > Train > Skills and select + New skill. A menu opens with Let Operator draft your skill, Create from scratch, and a Proactive outreach template. To build the Skill yourself, select Create from scratch.
Set when the Skill starts. In the Triggers section, edit the default What the customer says trigger and select + Add trigger to add others. Fin Skills support three kinds of trigger, and they're independent, so you can combine them:
Customer sends a message (called What the customer says in the editor) — the default. Describe what the customer says to trigger the Skill, add trigger examples ("Use when" and "Do not use when" — we recommend 10–20), then set the audience and channels.
To add trigger examples, select Train Fin on examples. In the panel that opens, use the Use when and Do not use when tabs to add at least 10 examples (we recommend 10–20) so Fin understands when to use the Skill.
To set who the Skill applies to, use the audience and channel options in the trigger. The Channels and audiences panel opens beside the editor. Fin only uses the Skill when a matching message comes from this audience on these channels. By default, Audience is Everyone and Channels is All channels.
To limit the Skill to specific channels, open the Channels dropdown and check the channels you want. The options are grouped as Messenger (Web, iOS, Android), Social (Facebook, Twitter, WhatsApp, Instagram), and Other (Email).
Reach out proactively — select + Add trigger in the Triggers section, then choose Reach out proactively, to have Fin start the conversation for people who match an audience, instead of waiting for the customer to message first. To configure it, see How to set up proactive outreach with Fin Skills.
Based on an event — starts the Skill from the Inbox, a call, a website element click, or an API call, instead of from a customer message or proactive outreach.
This is optional: select + Add trigger and choose a trigger type: Inbox trigger (lets a teammate manually start the Skill from the Inbox), Website element click (starts the Skill when a customer clicks a specified element on your website), or API call (starts the Skill via the Intercom API).
For Website element click and API call triggers, Fin writes the initial outreach message to the customer — the same behavior as Reach out proactively.
Let Fin continue after this skill ends — applies to Reach out proactively and Based on an event (not a customer message). Configure what Fin can still do after the Skill ends (use content, follow guidance, detect attributes), and where to hand off if unresolved: choose a Team or Workflow, and set what Fin says to the customer first.
Add the tools you want Fin to use. The Tools section of the Fin Skill editor lists your tools, and the Add tool menu groups the tools you can add.
You can add any of these tools:
Call data connector: Live lookups from external systems (for example, order status or account data)
Prioritize content: Specific articles or snippets Fin can cite
Handoff to team: Teams, teammates, or workflows Fin can route to
Run a workflow: Fin ends this skill and starts a workflow
Use attribute: User, company, or conversation data Fin can read or update (set each attribute to "Read only" or "Read and update")
Tag: Tags Fin can apply to the conversation
Run a procedure: A step-based procedure Fin can switch to
Add event: An action the customer has taken in the product
Loop in teammate / agent: Ask a teammate a question and wait for their answer before continuing (see "How to let Fin ask a teammate before it continues")
Run code: Run Python code you've added to the Skill (see "How to let Fin run code in a Fin Skill")
Tip: Toggle on Add a note (under Built-in tools) to let Fin leave a note for the team in the instructions.
Add your instructions. In the Instructions field, describe the Skill's goal in plain language — what Fin should do, how it should behave, and any guardrails or edge cases. Write it as guidance, not a numbered sequence; Fin decides the moment-to-moment steps itself. Provide as much information as possible in the instructions. Any information not provided may be incorrectly inferred by Fin.
Use @ to reference any tool you've added directly in the instructions — type @ to search and insert by name. This tells Fin exactly when and how to use it.
A strong instruction covers:
Purpose — what customer intent this Skill handles
Guidance — how Fin should approach it (tone, what to gather, what to avoid)
Tool usage — when to call a @data connector, hand off to @a team, or cite @content
Edge cases — what to do if an action fails or the customer's request is out of scope
Choose the guidance categories and set the end message. At the top of the Skill editor, select the settings (gear) icon. In the Guidance tab, select Select categories, check the categories you want (Communication style, Context and clarification, Content and sources, Spam, Other, or Escalation guidance), then select Save. The categories you choose decide which workspace guidance rules shape how Fin behaves in this Skill. To set the last message Fin sends when the Skill ends, open the End message tab in the same Settings window, enter the exact message, and select Save. Leave the message empty to send nothing.
Save the Skill. Select Save to Fin Main. The Skill appears in your Skills list as Disabled, so it isn't active for customers yet. To test it and switch it on, continue to How to test and deploy a Skill. The buttons at the top of the Skill editor are Test and Publish to Fin Main.
When the Skill is switched off for every Fin agent, the main button reads Save to Fin Main instead. This opens the options to Save to release draft or add it to a New release draft.
How to add optional tools to a Fin Skill
After you've created and saved your first Fin Skill, you can add these optional tools: sending an email, asking a teammate before Fin continues, and running code. Each one is set up in the Skill editor, and each one needs a reference in the Skill's instructions.
How to let Fin send an email in a Fin Skill
You can let Fin send an email while a conversation continues, for example to give setup steps or a daily reminder. In the Skill editor, turn on the Send an email tool under Tools, in Built-in tools. The Send an email tool is off by default. Fin then sends the email when the Skill's instructions tell it to, or when the customer asks for one.
The Send an email tool is the first tool in the Built-in tools list. Switch on its toggle.
The Built-in tools section in the Skill editor lists these tools:
Send an email: asks Fin to send an email in the instructions.
Add a note: asks Fin to leave a note for the team in the instructions.
End skill: asks Fin to stop this Skill and carry on with the conversation.
Close conversation: asks Fin to close the conversation and prevent replies if needed.
Read customer data: Fin reads enabled customer data in the Skill. Select View data to see which data is enabled.
Use Fin Memory: Fin recalls earlier conversations. Select View settings to change the Fin Memory settings.
How to let Fin ask a teammate before it continues
You can let Fin ask a teammate a question and wait for their answer before it continues a Skill, for example to approve a refund. To set up the Loop in teammate tool:
Add it as a tool. In the Skill editor, select + Add tool > Loop in teammate / agent, choose a review team or teammate, and set how long Fin should wait (up to 7 days).
Refer to it in your instructions. Tell Fin when it should loop in the teammate. For example: "Before issuing a refund over $200, loop in Billing to confirm it's approved."
In the Add tool menu, Loop in teammate / agent is listed under Routing.
When the Skill's instructions call for it, Fin pauses the Skill and asks the teammate a question in the Inbox, with context and optional suggested answers. Fin reads the teammate's reply and continues the Skill. If no one replies within the wait time, the conversation is handed over to the selected team or teammate.
Note: Loop in teammate works on Messenger and email conversations. It isn't available when you use Fin for platforms.
How to let Fin run code in a Fin Skill
You can let Fin run Python code you've added to a Skill, for example to work out a refund amount or format a date. To set up the Run code tool:
Add it as a tool. In the Skill editor, select + Add tool > Run code. Add a name and description so Fin knows when to call it, the Python code (up to 64 KB), and its data inputs: attributes, data connector outputs, or values Fin collects from the customer.
Test the code. Select Test code to check the code works before you publish the Skill.
Refer to it in your instructions. Tell Fin when it should run the code. For example: "Before offering a refund, run Calculate refund amount to work out how much the customer is owed."
In the Add tool menu, Run code is listed under Resources. When the Skill's instructions call for it, Fin runs the code like any other tool and can use its output later in the Skill.
How to test and deploy a Skill
How to test a Fin Skill with Simulations
Skills work well with Simulations (automated test conversations that validate how Fin handles different scenarios). You can ask Operator to create and run simulations, then iterate based on the results. Since Skills are built around a goal, not a fixed set of steps, plan to test more than once. Even well-written instructions can miss a scenario. Test with Simulations to find gaps, refine your instructions, and test again to see how Fin performs across a variety of scenarios. You can also create Simulations manually.
How to deploy a Fin Skill
Once you're happy with your Fin Skill, follow these steps to deploy it. To deploy incrementally, use Releases.
In the Skill editor, switch on Service agent.
Select Publish to Fin Main to set the Fin Skill live.
Which Fin Skills features are available during the closed beta?
The following table shows which Fin Skills features are available, and which are coming soon.
Feature | Status |
Operator creation, editing, and testing | Available |
Trigger, trigger examples | Available |
Based on an event | Available |
Trigger via button or API | Available |
Reach out proactively | Available |
Channel and audience targeting | Available |
Agentic switching to other Skills and Procedures | Available |
Simulations | Available |
Manual preview | Available |
Data connectors | Available |
Handoff to team, teammate, and reusable workflow | Available |
Tags | Available |
Read attributes | Available |
Workspace guidance applying to Skills | Available |
Switch to another procedure | Available |
Add a note | Available |
Human in the loop | Available |
Agent in the loop | Coming soon |
Update attributes | Available |
Reporting | Available |
Run code | Available |
Prioritize content | Available |
Add event | Available |
Send an email | Available |
Close conversation | Available |
Releases | Available |
Frequently asked questions (FAQs) about Fin Skills
What should each Skill cover?
What should each Skill cover?
Each Fin Skill should focus on one problem. Rather than putting everything into one large Skill, create several smaller ones, each built around a single goal.
What happens if a customer raises more than one issue in the same conversation?
What happens if a customer raises more than one issue in the same conversation?
When a customer raises more than one issue in the same conversation, several Fin Skills can match at once, and they work in tandem rather than one at a time. Depending on what the customer asks, Fin draws on all the relevant Skills together, switching between them or combining steps as needed.
Say you want Fin to handle subscription cancellations and process refunds. Each would be its own separate Skill. If a customer reaches out asking to cancel their subscription and get a refund, both Skills match, and Fin uses them together to resolve the customer's request.
Why did only one Fin Skill finish when multiple Skills ran in my conversation?
Why did only one Fin Skill finish when multiple Skills ran in my conversation?
When multiple Fin Skills run in the same Fin conversation, only the first matched Skill has an end event. One Skill triggers the Skills Agent, which then pulls in additional Skills as needed. The Skills triggered along the way don't have a named end step.
What happens when a Fin Skill's instructions conflict with workspace guidance?
What happens when a Fin Skill's instructions conflict with workspace guidance?
When a Fin Skill's instructions conflict with workspace guidance, Fin follows the Skill. While a Skill is running, its instructions are the more specific direction for that job, so they take priority over any conflicting guidance rule.
For example, your workspace guidance might say "Never ask customers for their email address," while a Skill for changing a customer's email says to collect their current and new address. Fin collects both addresses while that Skill runs.
Skill instructions also take priority for handovers. If a Fin Skill's instructions say not to hand the conversation over, Fin doesn't hand over during that Skill, even if the customer asks to speak to a person or your guidance says to escalate. Fin acknowledges the request and continues with the Skill.
Note: If customers should always be able to reach your team, add an exception to the Skill's instructions. For example: "If the customer explicitly asks to speak to a person, hand over to @Support team." Only use absolute rules like "Never hand over" when you want that behavior in every case.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts

















