Can I customize the customer-facing message Fin sends when an escalation rule happens?

Hi ​@בן גטניו , 
 

Doc says :

"Tip:...

...To customise the escalation to send a message/collect information, a workflow needs to be set up”

from here :  https://www.intercom.com/help/en/articles/12396892-manage-fin-ai-agent-s-escalation-guidance-and-rules#h_6db8eefa57

So here’s something you can do : 

Use a Workflow with Branches to send your own custom handoff message:

1. Create your Escalation Guidance/Rule in Train > Escalations

2. Go to your Fin Workflow (Deploy > Chat or Workflows)

3. Add Branches after the "Let Fin answer" step

4. Set the condition to "Escalation" → select your escalation rule

5. Add a "Send Bot Message" step with your custom text

6. Then add "Assign conversation" to route to the right team/inbox

Optional:

You can also adjust Fin's global tone of voice .

I don't think this will solve your exact use case if you're targeting a very specific handoff message, but it might  help someone if the issue is more about Fin's overall tone.

In Fin AI Agent → Train → Guidance → Basics, you can adjust the tone of voice, which can make all of Fin's messages more aligned with your support style.​
→ https://www.intercom.com/help/en/articles/13177409-customize-fin-ai-agent-tone-of-voice-and-answer-length


Hope it’ll help !

Thanks for your reply, ​@Cédric V!

We actually made several adjustments and added guidance to help Fin manage its communication style. That said, this message feels very specific - almost like it’s coming from a preset template Fin is using.

I was under the impression there was a way to edit that without needing to set up a dedicated workflow.

By the way, if we do decide to use a workflow, would it override or conflict with any existing workflows that include escalations?

Just to note - we hadn’t seen this message before we created the escalation rule.

Hi ​@בן גטניו,

You’re welcome, thanks for the extra context.

1. “I was under the impression there was a way to edit that without needing to set up a dedicated workflow.”

I think you’re not totally wrong to think that, because Intercom does let you influence what happens at escalation time with Guidance.
But FAQ states:

“How can I customize the Fin's introduction and escalation messages?”
→“While this default message itself cannot be directly edited or removed, you can influence this process by creating Guidance in Fin.”
(Here : https://fin.ai/help/en/articles/10763810-faqs#h_10327e706c )​

So if you want a fully custom, guaranteed, word‑for‑word handoff message, then yes, that does require using a Workflow with a “Send bot message” step on your escalation rule.​

2. “If we do decide to use a workflow, would it override or conflict with any existing workflows that include escalations?”

I know that doc says that for a given conversation, only one customer‑facing workflow can trigger.​
So that would mean:

• You don’t want multiple separate workflows all trying to handle the same Fin conversation in parallel.

• In my mind, the safest pattern would be: extend your existing Fin workflow and add a branch on your Escalation Rule, instead of creating yet another separate workflow just for this.​

If you do that i think:

• You won’t be “fighting” with another workflow, you’re just adding more logic inside the one that’s already running for Fin.

• Your other workflows will keep working off their own triggers/audiences

3. “We hadn’t seen this message before we created the escalation rule.”

I think that actually fits well how Fin is designed:

• Before you set up a specific escalation rule, Fin uses its more “default” escalation behaviour.​

• Once you add an explicit rule, the escalation path becomes more structured and consistent → so that message now shows up every time that rule fires.​

But honestly, the best way to be sure is to test it in a sandbox or with a test contact first. That way you'll see exactly how it behaves with your other workflows.

Thanks again for your reply, ​@Cédric V 

Right now, we have several workflows—some for “during office hours,” some for “outside office hours,” and a few others, such as a pop-up workflow for specific pages, etc.

I’ve tried to add a message that appears right after the escalation is triggered. For example:

The message in D.path is what we would like Fin to respond with right when it’s escalated to a human agent.

But the problem is that Fin is still using one of its own messages and the message we just set, which doesn’t make sense - we don’t want the customer to receive two messages.

For example:

Any idea how we can make sure that, when an escalation is triggered and we add a message to that workflow, only our message is sent to the customer - not both?

​@Cédric V 

Quick update: this worked really well so far 👍

I’ve set a Communication Style guidance like this:

When you decide to escalate to a human, send only this sentence:
"נראה שכאן עדיף שנציג אנושי ייכנס לתמונה 👋
אני מעביר אותך עכשיו, כבר חוזרים אליך."
What NOT to do:
Do not add extra explanations before or after this message.
Do not ask additional clarifying questions once you have determined the conversation is stuck.
Do not use your default escalation text.

At the moment, this behaves exactly as expected and gives us full control over the escalation copy.

However, here’s the challenge 👇
Escalation can be triggered from multiple different scenarios, and each scenario should ideally have a different message.

For example:

• If the customer explicitly asks to speak with an agent, the message should be one version

• If Fin decides on its own to escalate because it cannot resolve the issue, the message should be different

• Potentially other escalation reasons as well

Right now, Communication Style guidance seems global, so I can only define a single escalation message.

Is there a recommended way to vary the escalation message based on the escalation reason or trigger?

​@בן גטניו ,
 

This is a great result, thanks a lot for sharing,

As Communication Style / Escalation Guidance is global and you can only have one core escalation sentence there. To get different messages depending on why the escalation happened, i guess you’ll need to move that logic to the workflow + Fin Attributes / Escalation Rules layer.​

I’d do something like :

1. Keep Fin’s own escalation line very short and generic
   In Guidance, keep something minimal that can be used for all cases so Fin always says the same, very short sentence when it escalates.​ (ex. “Just a moment.”)

2. Model the different escalation reasons as rules/attributes
   For example:​

   • Escalation because the customer explicitly asked for a human → “ Escalation Rule A”.

   • Escalation because Fin is stuck / can’t resolve → “Escalation Rule B”.

   • Other reasons → additional rules/attribute values.

3. Branch in the workflow on those reasons and send different copy
   In your Fin workflow, after the “Let Fin handle” step and the handover, add branches on:​

   • either “Escalation Rule = A / B / C”,
     
     (or you use Fin Attribute)

Then in each branch, use a different Send bot message with the specific text you want for each scenario.

So in short:

• Guidance = one global, short escalation line from Fin.

• Per‑reason escalation copy = lives in the workflow branches, driven by your escalation rules / Fin attributes.