FinThe question stays with Fin.
Your existing support conversation.
FIN + CANDU
Keep Fin talking.
Give it your product context.
Keep Fin in the conversation. Connect the approved product reads it needs to answer questions about your customers’ accounts.
No credit card required
YOUR CONVERSATION, CONNECTED
Give Fin the information behind the question.
Start with an approved read. Fin uses the returned product data in the conversation your customer already has.
A customer asks
“Is the SDK installed on my site?”
FinCanduRead SDK status.
Product information, supplied through the action you make available.
Read onlyFinA more specific answer.
Fin explains the returned status.
Connection overview. The response depends on your product and enabled actions.
UNDER THE HOOD
Product facts, where Fin needs them.
Choose the information your support team needs most.
Account details
The customer’s current subscription plan.
Installation status
Whether the SDK is installed on their site.
Product access
Which segments a customer belongs to.
Check the actual call. In Fin’s conversation, look for the Candu action under Private sources.
Verify the Candu action in Fin (opens in a new tab)DIFFERENT JOBS, BETTER TOGETHER
Who does what.
| Capability |  |  |
|---|---|---|
| Support conversation | FinAnswers the customer | CanduSupplies approved product information |
| Product context | FinUses the returned result | CanduRuns the read you enable |
| Action availability | FinUses its connected actions | CanduSets access per action |
| Product changes | FinDepend on your configured action | CanduRequire separate review and testing |
| In-product help | FinKeeps the conversation | CanduOffers the browser bot as a separate capability |
Fin capabilities vary by setup. This page shows a read connection, not a write or Fin launching the browser bot.
KEEP YOUR SUPPORT SETUP
Choose where Candu enters the conversation.
Start alongside the support setup that works.
- Fin
- Candu
- Fin
Fin first.
Fin stays customer-facing. A connected Candu read supplies the product context for its answer.
- Candu
- Fin
Candu first.
In-product help starts on the page. Agree the route to Fin as part of your support setup.
Handoff behavior depends on your setup.
YOUR PRODUCT, YOUR RULES
Start with one approved read.
Connect, choose and verify before expanding the setup.
- 1
Connect Intercom.
Use your Candu workspace’s Intercom connection.
- 2
Choose the action.
Enable Fin access for a read you have reviewed.
- 3
Test the real answer.
Ask a relevant question, then verify the action in Private sources.
BEFORE YOU CONNECT
Questions worth asking.
When is Fin alone enough?
When the answer is in your help content and nothing in the product needs to change. Add Candu when the customer needs their account checked or something done.
Do I need to replace Fin?
Keep Fin and your current support setup. Connect one reviewed Candu action first, then test it with a real customer question.
What can Fin do with Candu?
Fin can use the Candu actions you make available to it, including approved reads for live product context. Writes require separate setup, policy review and testing. Fin access is set per action.
What needs confirmation?
Set confirmation per action. A consequential write should present the proposed change and wait for the customer to confirm. Verify that behavior in your actual Fin setup before enabling the write.
Does it work with other chatbots?
The MCP action channel is in early access. Availability depends on workspace enablement, signed product identity, the supported client and a live product tab. Talk through your setup with us.
How long to set up?
Start by connecting Intercom, choosing a read-only action and testing its answer and Private sources in Fin. Timing depends on the actions and product setup you already have.
YOUR FIRST FIN CONNECTION
Start with one support question.
Choose a useful read. Review the setup, then check the result in Fin.
No credit card required