Meetings and notes

Balt works inside Fathom.

You change nothing about Fathom. Balt connects to it, reads what it needs and hands back finished work.

ConnectionYour existing account, read and write

What you can ask it

What Balt does in Fathom

Reads the transcript

Reads the Fathom recording and pulls out what was decided and what comes next.

Files it on the record

Writes the summary onto the right candidate or client, so nobody retypes it.

Surfaces the signals

Flags an availability or a next step mentioned in the call.

Keeps you in control

Writes only where you allow it and shares nothing without your approval.

How it works

Step 1
Connect once
You connect your Fathom account once, with the permissions you choose.
Step 2
Write your request
You write your request in Slack or Teams, in plain language, as you would to a colleague.
Step 3
Balt does the work
Balt does the work in Fathom and shows you anything outbound before it leaves.

Security and permissions

Balt reaches only what you open to it, and access is withdrawn in one move. None of your data trains a model, ours or a supplier’s. Every action is logged: you can say who did what, when, and on whose request.

Frequently asked questions

Does Balt replace Fathom?

No. Balt works inside Fathom with your existing account: nothing to migrate, nothing to relearn, and your teams keep using the tool as before.

What permissions does Balt need on Fathom?

Only the ones you grant. Read and write are set separately, and an access is withdrawn in one move without going through our support.

Does Balt act on its own in Fathom?

It acts alone on what stays internal and reversible. Anything leaving the company is shown to you before it goes, and a decision that closes a door stays human.

Is my Fathom data used to train a model?

No, contractually, including at downstream model providers. Your data stays yours and is hosted in the European Union.