Start free trial Webinars Certifications Catalog

Fin for Sales: Deploy in a Workflow

Set up workflows to control when, where, and how Fin for Sales engages your prospects across channels.

rate limit

Code not recognized.

About this course

 

Your playbook, content, guidance, and integrations are set. Now it’s time to put Fin to work. Deploying Fin for Sales happens through Workflows, and the way you set them up determines when Fin engages, on which channels, and what happens when a conversation doesn’t end in qualification.

This lesson is part of the Fin for Sales course.

Prerequisites

Before you begin, make sure the following are in place:

  • Fin for Sales access: Go to Fin AI Agent → Sales to get started.
  • Playbook, content, guidance, and integrations in place: Learn how to do this and more in the Fin for Sales course.

Video transcript

Deploying for sales is done through a parent workflow, the same way we deploy Fin for service. The easiest way to create one is directly from the deploy section. Since chat and email behave differently, we'll need a separate parent workflow for each channel we want to cover. When setting up the trigger, we can go inbound, so Fin responds when a prospect starts a conversation, or outbound, so Finn proactively reaches out at high intent moments, like when someone's spending time on your pricing page. The parent workflow is also where we handle the global orchestration. So if Fin recognizes that a prospect is asking a support question and can't qualify them, we can add a branch here to seamlessly hand off to Fin for service. At this point, Fin will know that its role of selling is done and put on its support hat. You can also add branches for other scenarios to nurture a lead, for example. So if Fin couldn't qualify but detects high intent through an attribute, you can trigger a nurture campaign through a reusable workflow to keep that prospect warm automatically.

 

Key workflow decisions

The video covers the full deployment setup. Here are the key decisions to keep in mind:

Decision What to consider
Channel Chat and email behave differently, so create a separate parent workflow for each channel you want to cover.
Trigger type Inbound: Fin responds when a prospect starts a conversation. Outbound: Fin proactively reaches out at high-intent moments, like time spent on your pricing page.
Support handoff Add a branch so Fin can seamlessly hand off to Fin for Service when a prospect is asking a support question instead of a sales one.
Nurture flows If Fin can’t qualify but detects high intent, trigger a nurture campaign through a reusable workflow to keep the prospect warm automatically.

 


What’s next?

Fin is deployed and ready to engage prospects, so what now?

Ready to go deeper?

Explore the full course to learn how to test before going live and analyze performance once Fin is running.
πŸ‘‰ Take the full Fin for Sales course

About this course

 

Your playbook, content, guidance, and integrations are set. Now it’s time to put Fin to work. Deploying Fin for Sales happens through Workflows, and the way you set them up determines when Fin engages, on which channels, and what happens when a conversation doesn’t end in qualification.

This lesson is part of the Fin for Sales course.

Prerequisites

Before you begin, make sure the following are in place:

  • Fin for Sales access: Go to Fin AI Agent → Sales to get started.
  • Playbook, content, guidance, and integrations in place: Learn how to do this and more in the Fin for Sales course.

Video transcript

Deploying for sales is done through a parent workflow, the same way we deploy Fin for service. The easiest way to create one is directly from the deploy section. Since chat and email behave differently, we'll need a separate parent workflow for each channel we want to cover. When setting up the trigger, we can go inbound, so Fin responds when a prospect starts a conversation, or outbound, so Finn proactively reaches out at high intent moments, like when someone's spending time on your pricing page. The parent workflow is also where we handle the global orchestration. So if Fin recognizes that a prospect is asking a support question and can't qualify them, we can add a branch here to seamlessly hand off to Fin for service. At this point, Fin will know that its role of selling is done and put on its support hat. You can also add branches for other scenarios to nurture a lead, for example. So if Fin couldn't qualify but detects high intent through an attribute, you can trigger a nurture campaign through a reusable workflow to keep that prospect warm automatically.

 

Key workflow decisions

The video covers the full deployment setup. Here are the key decisions to keep in mind:

Decision What to consider
Channel Chat and email behave differently, so create a separate parent workflow for each channel you want to cover.
Trigger type Inbound: Fin responds when a prospect starts a conversation. Outbound: Fin proactively reaches out at high-intent moments, like time spent on your pricing page.
Support handoff Add a branch so Fin can seamlessly hand off to Fin for Service when a prospect is asking a support question instead of a sales one.
Nurture flows If Fin can’t qualify but detects high intent, trigger a nurture campaign through a reusable workflow to keep the prospect warm automatically.

 


What’s next?

Fin is deployed and ready to engage prospects, so what now?

Ready to go deeper?

Explore the full course to learn how to test before going live and analyze performance once Fin is running.
πŸ‘‰ Take the full Fin for Sales course