Skip to main content

Use Procedures over Fin Voice

Procedures on the phone, with the power of Procedures on chat.

Written by Bethany Clark

Use this article to build your first voice procedure using Operator or manual creation, test it before going live, and understand which capabilities differ from chat procedures. You need the Can manage workspace data permission to create procedures.

  • More agency. Fin combines tools and changes its plan during the call. It works to the outcome that you set. It does not follow a fixed script.

  • One way to build. A voice Procedure uses mostly the same steps and tools as a chat Procedure.

  • The call keeps moving. Fin speaks to the caller while it works. It tells the caller when a look-up takes time.

  • Operator writes it for you. Describe the Procedure in plain words and Operator builds the steps.


How to build a Fin Voice Procedure

Start with Operator — describe your procedure in plain language and it builds the steps for you. You can edit the result by hand afterwards.

Option 1: Use Operator (recommended)

Describe the outcome, the information that Fin must collect, and the end condition. Don't describe the steps — Operator writes those.

Example: "Build a voice procedure for order status. Trigger it when the caller asks where their order is. Ask the caller for the order number, look it up with the Order lookup connector, then read the status and the delivery date back to the caller and end the procedure. If the connector finds nothing, escalate."

The Operator interface showing a plain-language prompt input field where you describe a voice procedure. Operator uses this description to automatically generate the procedure steps.

Option 2: Manual creation

  1. Go to Fin AI Agent > Train > Procedures and click + New procedure.

  2. Choose Voice as the procedure type.

  3. Build your steps end to end.

  4. Save it to Fin Main.

  5. Test it using Preview, Simulations, or a real call (see How to test your Fin Voice Procedure below). Once satisfied, switch it on and click Publish to Fin Main.

The Fin AI Agent Procedures screen showing a new procedure being created with the Voice type selected.


How to test your Fin Voice Procedure

Preview and Simulations both work on voice procedures. Use all three methods — each one catches a different kind of problem.

1. Preview

Walk through the Procedure and watch it branch. Click the eye icon to see the events, not only the words.

The Procedure Preview panel for a voice procedure, showing branching steps and the eye icon used to inspect events at each step of the conversation.

2. Simulations

Run many caller behaviors together. This finds the branch that fails when the caller gives an unexpected answer.

The Simulations tab for a voice procedure, showing multiple test scenarios running in parallel with pass and fail results.

3. A real call

Add the audience rules, switch the Procedure on and publish it to Fin Main, then call the line and say something that triggers it. Fin can start the Procedure from what the caller says at any point in the call.

Tip: For the clearest test results, isolate the Procedure you're testing using audience rules, or pause older voice Procedures covering the same topic. Running overlapping Procedures on the same call can make results harder to interpret.


Triggering a voice procedure when a call comes in

By default, voice procedures trigger based on what the caller says and Fin detects their intent and starts the right procedure. You can also trigger a procedure deterministically at the start of a call using the Inbound Call event. This runs the procedure as soon as the call connects, before the caller says anything.

When to use an Inbound Call trigger

Use the Inbound Call trigger when you want guaranteed, predictable behavior at the start of a call rather than relying on intent detection. Common use cases:

  • Triage callers before routing — gather information such as the reason for calling, account type, or language preference, then route the caller to the right procedure or team.

  • Collect information upfront — ask for an account number or order ID before Fin starts answering questions, so the data is ready when it’s needed.

  • Custom welcome flows — run a specific opening experience for a phone number, independent of what the caller says first.

How to set up an Inbound Call trigger

  1. Open your voice procedure in the editor.

  2. In the When to trigger section, go to Based on events and click Add.

  3. Select Inbound Call as the event type.

  4. Choose the phone number you want this procedure to run for. The procedure will start automatically when a call comes in on that number.

  5. Switch on Service agent and click Publish to Fin Main.

Note:

  • The Inbound Call trigger is available on simple deployment phone numbers. Each number can only have one procedure set to trigger on inbound calls at a time.

  • If you previously chose a Procedure to run for a number in simple deploy, Intercom moved it to an Inbound Call trigger automatically. To change which Procedure runs, edit the trigger in the Procedure editor.


How to migrate an existing voice Procedure to the latest version

If you were using the previous version of Voice Procedures, duplicate it or ask Operator to rebuild it. The previous version can no longer be set live. The copy picks up the latest voice capabilities.

A voice procedure card showing the Duplicate option, used to create a copy that picks up the latest voice capabilities.
  1. Duplicate the original procedure. The copy picks up the latest voice capabilities.

  2. Test the copy using Preview, Simulations, and a real call.

  3. Switch the copy on and publish it to Fin Main.

  4. Retire the original by pausing or archiving it from the Procedures list.


Voice-specific capabilities and limitations

Fin Voice Procedures inherit many tools and operations from the chat procedure editor, but there are some limitations and new capabilities to be aware of when creating your procedure.

The End step

The End step has a voice-specific option: choose what Fin does with the phone call when the procedure ends.

  • Continue the call — Fin stays on the line and keeps answering questions. This is the default behavior.

  • End the call — Fin says an automatically generated goodbye and hangs up.

This is set per End step, so a procedure can hang up on its success path while keeping the caller on the line from other branches.

The Handoff tool

A Handoff tool is a path that allows Fin to exit the procedure and handoff to a team or a process. There are four handoff types:

  • Pass to team — rings the team you select.

  • Request a callback — takes a voicemail and ends the call so a teammate can call back.

  • Forward call — sends the caller to an external phone number.

  • Pass to reusable workflow — hands the call to a reusable workflow for more deterministic control.

If you use Fin with a helpdesk outside of Intercom (Fin for platforms), only the Forward call handoff type is supported.

The type is set per Handoff step, so different steps or branches of the same Procedure can hand off in different ways.
If Fin calls any handoff tool, the conversation is billable as a Procedure handoff.
Choose a handoff from the @ commands list to get started!

Switching procedures

A voice Procedure can hand the call to another Procedure during the call. Switches are deterministic: Fin moves to the Procedure you choose.

With Agentic Switch, Fin can change Procedure on its own when it detects a different intent from the caller. To turn it on, click the gear icon in the Procedure editor and select Enable Procedure Switching.

Limitations

The following capabilities are available in chat Fin Procedures but are not currently available in voice Fin Procedures. Where a workaround exists, it's noted:

  • Loop in teammate / agent

  • Waiting for a webhook

  • End message — Use the End the call option on the End step instead. This generates an automatic goodbye before hanging up.


FAQs

Will my existing voice Procedures stop working?

Yes. The previous version of voice Procedures was retired on October 20th, 2026 and can no longer be set live. When you rebuild them, they will automatically use the latest capabilities. Alternatively, you can ask Operator to help you rebuild.

Can I move a Procedure back after I've moved it across?

No. Once a Procedure has moved across it can't go back, which is why we recommend duplicating rather than editing the original.

Do I have to write voice Procedures differently from chat Procedures?

A voice Fin Procedure uses mostly the same steps and tools as a chat Fin Procedure, with a few differences: voice doesn't support Loop in teammate / agent, Wait for Webhook, or end messages. A voice Procedure can hand off the call, switch to another Procedure during a call, and run on the Inbound Call event. The End step also has a voice-specific option to end the call (hang up) or continue the call. See the Voice-specific capabilities and limitations section of this article for the full list.

Can I duplicate a chat Procedure to create a voice Procedure?

Yes, you can duplicate a chat Procedure and choose to duplicate it as a voice Procedure, rather than starting from scratch. However, a chat Procedure won't automatically work on voice. You'll still need to review and update the steps for voice, including any capabilities that aren't supported (see Voice-specific capabilities and limitations above), before publishing and going live.

Are Fin Voice Procedures billed the same way as chat Procedures?

Yes, Voice Procedures follow the same outcome-based billing as chat Procedures, but the cost depends on the rate in your contracted plan. See Fin AI Agent outcomes for the outcome-based pricing definitions.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?