# FIN

You can get **really creative** when integrating Birdie into your support flow with FIN.

But one **common, minimal-yet-powerful setup** is this:

> 🧩 **Offer users a simple way to record their screen** when they face an issue, bug, or error — so when the conversation gets handed off to a human agent, agents already have the context they need: a screen recording, console logs, network activity, repro steps...

This helps agents resolve issues faster and makes escalations to engineers much smoother.

Here is what it looks like in action: 

<figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FNq1FkQdI2fHwqu71j3gn%2FScreenshot%202025-07-15%20at%2016.37.17.png?alt=media&#x26;token=7c61a75c-52bf-49d1-9939-c262403d184b" alt="" width="375"><figcaption></figcaption></figure>

***

## Video Tutorial

Here is the complete walkthrough:

{% embed url="<https://youtu.be/xULIXqiM6y8>" %}

## 🧪 Step 1 — Craft the Wording FIN Will Use

{% hint style="info" %}
At this step, you **don’t need to add anything to FIN yet**. You’ll do that in **Step 3**.\
Right now, the goal is simply to decide **what** FIN should say when it suggests using Birdie
{% endhint %}

Before training FIN, start by deciding **exactly what you want FIN to say** when offering a screen recording option.

Why? Because without fixed wording, FIN might **hallucinate** and generate different messages each time — diluting the user experience.

**We recommend writing a short, clear, consistent sentence** that FIN will reuse every time it suggests using Birdie. Here’s a proven wording that works great (feel free to update it):

*<mark style="color:green;">We recommend taking a screen recording to help us see the issue from your perspective, enabling a quicker and more accurate answer:</mark>*

<mark style="color:green;">Click on this link to record your screen:</mark> <mark style="color:purple;">\[Add Birdie Request Link Here]</mark>

*<mark style="color:green;">Pro tip: For best results, enable audio and talk us through the steps leading to your issue while recording</mark>*

*<mark style="color:green;">Once you’re done:</mark>*

1. *<mark style="color:green;">Go to the “Recording” tab</mark>*
2. *<mark style="color:green;">Click on Finish</mark>*
3. *<mark style="color:green;">Click “Copy the link”</mark>*
4. *<mark style="color:green;">Paste the link here</mark>*

\
🔗 **To get your Birdie link**, go to your [**Birdie Settings > Helpdesk**](https://app.birdie.so/settings/helpdesk), copy *<mark style="color:blue;">**Y**</mark><mark style="color:blue;">our Birdie link to paste in Fin</mark>*, and paste it in place of <mark style="color:purple;">**\[Add Birdie Request Link Here]**</mark> above

You’ll re-use this wording across all training examples (see Step 3). Consistency is key.

## 🔁 Step 2 — Define *When* FIN Should Trigger Birdie&#x20;

{% hint style="info" %}
At this step, you don’t need to add anything to FIN yet. You’ll do that in **Step 3**.\
Right now, the goal is just to define the kinds of messages that should trigger a Birdie prompt.
{% endhint %}

Now that you’ve crafted the message FIN will use (see Step 0), the next step is to decide **when** you want FIN to suggest a screen recording.

While FIN is designed to understand natural language, its performance improves significantly when you **guide it with specific examples**.

You can start with a base list of common issue-related phrases and gradually enriching it with **real examples** from your support conversations.

These are broad expressions users often type when something isn’t working that you can use:

* *<mark style="color:yellow;">I'm facing an issue</mark>*
* *<mark style="color:yellow;">It doesn't work</mark>*
* *<mark style="color:yellow;">There is a bug</mark>*
* *<mark style="color:yellow;">I face a problem</mark>*
* *<mark style="color:yellow;">Something’s broken</mark>*
* *<mark style="color:yellow;">I'm seeing an error</mark>*
* *<mark style="color:yellow;">This page won’t load</mark>*
* *<mark style="color:yellow;">It crashes when I try to use it</mark>*
* *<mark style="color:yellow;">I'm stuck</mark>*
* *<mark style="color:yellow;">It's not doing what it’s supposed to</mark>*
* *<mark style="color:yellow;">Nothing happens when I click</mark>*
* *<mark style="color:yellow;">I keep getting a weird message</mark>*
* *<mark style="color:yellow;">This feature isn’t working properly</mark>*
* *<mark style="color:yellow;">I think there’s a glitch</mark>*

#### &#x20;Then Add More Specific Sentences:

You can use ChatGPT to generate phrasing based on your product, past support chats, or bug patterns. Just describe the kinds of issues users face, and ask for variations of how they might report them.

<details>

<summary>Add extra ones to help FIN better detect trickier edge cases and more nuanced issues:</summary>

* I keep getting an error message
* I'm experiencing strange visual glitches on the platform
* The app is behaving unexpectedly, and it's hard to explain
* I followed all the troubleshooting steps, but the issue is still there
* The website layout looks broken on my screen
* When I click on a button, nothing happens, or something different from expected occurs
* I can't seem to replicate the issue consistently
* The workflow process seems broken; I can't move to the next step
* The software crashes when I perform a specific action
* I'm having difficulty with a multi-step process, and I don't know where it's going wrong
* The custom integration doesn't seem to work
* The product hangs or freezes at certain points
* Certain elements on the screen are not displaying as they should
* ### B — Create a Snippet
* I'm not receiving any error messages, but it's still not working correctly.
* When I scroll down the page, some elements overlap or disappear
* There's an issue with the search functionality; it's not showing the results I expect
* I'm facing an issue with the login process; it's not what I usually experience
* I'm seeing different behaviors between different browsers/operating systems
* I can't customize settings or preferences; the changes don't save
* Certain clickable elements or hyperlinks are unresponsive
* I'm experiencing inconsistent behavior
* It's not working as expected.

</details>

## 🧠 Step 3 — Train FIN with Sample Phrases

{% hint style="info" %}
There doesn’t appear to be a strict order of importance between the different training methods below.\
Some teams rely more on one than the others, but we recommend using **all of them together** for best results.
{% endhint %}

You can train FIN in multiple ways — and **we recommend combining all of them for best results.**

### A — Create a Context Guidance

{% stepper %}
{% step %}
On FIN, go to Train > Guidance, and create a new context guidance using this template:&#x20;

> If <mark style="color:blue;">**\[Describe your use case with natural language]**</mark>, then request a screen recording using Birdie link: <mark style="color:purple;">**\[Add Birdie Request Link Here]**</mark>\
> \
> The phrases below are common ways customers express that something is going wrong. These are just examples to help you recognize when to suggest a screen recording — you don’t need to match them exactly:\ <mark style="color:orange;">**\[Add When FIN should trigger Birdie - See step 2 ]**</mark>\
> \
> Always display this exact message to the customer :\ <mark style="color:green;">**\[Add the Wording FIN will use ]**</mark>

Here is an example of how it should looks like:&#x20;

<figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2F4wqdlUd1NISXZYjEKBba%2FContext%20Guidance%20-%20FIN%20x%20Birdie.png?alt=media&#x26;token=d99e3400-22fe-4e37-b59a-fda106c06a74" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
&#x20;Make sure to append the customer email to the Birdie Request Link by selecting the email property. This will ensure each recording is associated with the correct customer email. For instance <mark style="color:purple;">`https://your-subdomain.birdie.so/urec/intercom`</mark><mark style="color:blue;">`?email=`</mark><mark style="color:green;">`name@company.com`</mark> with <name@company.com> being the email property
{% endstep %}
{% endstepper %}

### B — Create a Custom Answer<br>

{% stepper %}
{% step %}
In FIN, go to **Train > Custom Answers** and click **“New Answer.”**
{% endstep %}

{% step %}
In **Step 2 of Custom Answers**, enter the types of questions your customers commonly ask when experiencing issues or bugs — these are the phrases you defined on Step 2 above

<figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FDxfZ9poI55hudJ91bPrM%2FCustom%20Answer%201%20-%20Fin%20x%20Birdie.png?alt=media&#x26;token=de61e43d-f409-48f3-a110-f59ebc1065ef" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In **Step 3 of Custom Answers**, paste the wording you prepared in Step 1 above — the message FIN should send when offering a screen recording.

> 💡 *No need to include instructions to copy/paste the video link — the Birdie app handles that automatically.*
> {% endstep %}

{% step %}
Still in **Step 3**, click **“+ Add Step”**, search for **“Send an app”**, and select **Birdie**.

<figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FabFCmbd3Gc0GqqtG2GmS%2FCustom%20Answer%202%20-%20Fin%20x%20Birdie.png?alt=media&#x26;token=18280550-db9a-40d4-83e9-36b20c72c04c" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### C — Create a Snippet

{% stepper %}
{% step %}
In FIN, go to **Train > Content** and click **“Create a Snippet”** using this template:&#x20;

> If <mark style="color:blue;">**\[Describe your use case with natural language]**</mark>, then request a screen recording using Birdie link: <mark style="color:purple;">**\[Add Birdie Request Link Here]**</mark>\
> \
> The phrases below are common ways customers express that something is going wrong. These are just examples to help you recognize when to suggest a screen recording — you don’t need to match them exactly:\ <mark style="color:orange;">**\[Add When FIN should trigger Birdie - See step 2 ]**</mark>\
> \
> Always display this exact message to the customer :\ <mark style="color:green;">**\[Add the Wording FIN will use ]**</mark>

Here is an example of how it should looks like:

<figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FYBQXwsvbsR5jULk4oLSP%2FSnippet%20-%20Birdie%20x%20FIN.png?alt=media&#x26;token=5d6f6619-9c29-4db6-a485-04ca08deda0c" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### D — Check Unresolved Questions

Head to your **Unresolved Questions** in Intercom and review the messages where **FIN didn’t respond confidently**.

This is a great way to spot real user messages where FIN wasn’t sure what to do — and where suggesting a Birdie recording could actually make things easier for both sides.

Let’s say one of your unresolved questions is something like:

> *“I’m trying to set up a workflow but it’s not doing what I expect.”*

Instead of back-and-forth guessing, you can train FIN to say something like:

> “To help us understand your setup better, would you mind showing us what you’re trying to do with a quick screen recording? It’ll help us support you faster.”\
> \[Birdie Request Link]

You can also turn these missed questions into new Snippets, Custom Answers, or trigger phrases for Birdie.

***

Each of these four methods captures a different slice of real conversations.\
Use them together to ensure you’re covering both:

* The obvious “I have a bug” moments
* The harder-to-spot “Something feels off” cases