The calls Fathom already recorded
If you run Fathom you have a transcript of every call you have had this year. Most people use perhaps three of them, for a follow-up email, and never look at the rest again.
That archive is the single best source of material you own, because it is the only written record of how you actually explain things. Connecting Fathom to Inklined turns it into the thing you write from, starting with the calls from this week and working back as far as you want to go.
Fathom will record every call you take, which leaves the question of which ones repay the reading. Roughly 90% of any call is routine, and knowing what the other 10% looks like is most of the skill.
Connecting it
- 1In Fathom, generate a key from the account that owns the recordings. This is the part people get wrong on a team plan.
- 2In Inklined, go to Integrations, choose Fathom, and paste the key.
- 3The first sync runs immediately and picks up your recent calls. After that it runs every 4 hours.
- 4If you want your back catalogue, ask. Backfill is a separate run and it is bounded by your plan limit.
What Inklined takes
- →The transcript of each recording that has finished processing.
- →The meeting title and the date.
- →Speakers, as roles rather than names.
What happens to it
The first thing that happens to a transcript is that the names come out of it. People become role descriptors, so a participant is stored as “Host [GTM Consultant]” rather than by name. Companies become sector descriptors, so a client called Acme Corp is stored as “a B2B SaaS startup”. Email addresses, phone numbers, office addresses and profile links are removed. This runs once, on the way in, before anything else touches the text.
What is left is split into passages and indexed, so that when Inklined asks you something tomorrow it can show you the 40 seconds of the call the question came from rather than asserting that you said it.
Then a second rule applies, and it is the one that matters most if your calls are client work. Only speech attributed to you can become something you publish. On a typical consulting corpus most of the words belong to the other person, and offering those back to you as “something you said” is how somebody ends up publishing a client’s thinking under their own name. Anything that still names an organisation after all that asks you to confirm before it will draft from it.
One limitation worth stating rather than hiding: a client name that opens a sentence is not always caught, because “Sona ran this play” is shaped exactly like “Pricing pages need an owner”. The title check is the reliable one, and the confirmation step exists because no automatic check is enough on its own.
More on this: how Inklined works.
When it does not work
A connection that authenticates and then returns nothing looks exactly like a healthy one, which is why Fathom going quiet is hard to diagnose from the outside.
- It connected, but no calls have arrived.
- Check the key belongs to the account that owns the recordings. On a team plan a key generated from a seat that can view recordings but does not own them will authenticate and return an empty list. Check too that the recordings have finished processing.
- A recent call is missing.
- Fathom processes after the call ends, and a long call can take a while. Inklined only takes recordings with a finished transcript, so a call that ended 20 minutes ago may simply not be ready yet. It will arrive on the next sync.
- It says the meeting limit is reached.
- Starter takes 20 meetings a month and Pro takes 60. Recordings that arrive without a transcript do not count against it, and a call that syncs twice is only counted once.
Questions
Sync runs every 4 hours. Setup steps checked against the product on 24 September 2026. Using something else? See what Inklined connects to.
The calls are already happening.
Start with the strategy session. No card needed for that part.