Appels
The hub that keeps your sales calls. Each recorded meeting becomes a searchable transcript, linked to the right contact, with a summary. On top of that, a closing layer: scripts by objection, objections pushed to the CRM, follow-up drafts.
Overview
Calls gathers your recorded meetings in one place. The library lists the most recent calls first, with the source, duration, linked contact and a badge when no contact is attached yet. A full-text search queries the summary and transcript so you can find a call by what was said in it.
Ingestion is provider-agnostic. Today the main source is Fathom, wired by webhook and manual sync. Twilio telephony also feeds its calls in, through the Voice module. Adding a source means plugging in an adapter, not rebuilding the hub.
The closing side handles what happens during and after the call. A taxonomy of seven objection types with their trigger phrases, a reply script you write yourself per type, the objections you hit pushed onto the contact page, and a follow-up draft ready to review. Nothing is sent automatically: the follow-up stays a draft until you approve it.
What the module does
Recordings library
All your recorded calls, most recent first. Each row shows the linked contact or the title, the source, duration and date. Search hits a tsvector index over the summary and transcript, so you find a call by a phrase that was said, not only by a name.
- Sorted by start date, newest to oldest
- Badge when no contact is linked yet
- French full-text search over summary and transcript
- Per-call detail: AI summary, transcript, contact, rename, delete
Ingestion sources
The ingestion layer is provider-agnostic. Fathom is wired by webhook and manual sync, restricted to the platform admin. Twilio telephony feeds its calls in through the Voice module. The Sources page shows the connection state and the last sync.
Recording consent
Each recording carries a log of consent decisions: granted, denied, paused. The effective decision is always the most recent one. A recording can only be kept and processed when the latest decision is granted.
Closing scripts by objection
Seven objection types covered: price, budget, timing, authority, need, trust, competitor. Each type has trigger phrases, but the reply text stays written by you, never generated or pre-filled. A deterministic matcher spots the type from the words present in the transcript window and surfaces the right script.
- Default detection taxonomy, seeded with no reply text
- Script written by you, per type, in markdown
- Keyword match as a fallback, or direct lookup by type
Post-call and follow-up queue
After the call, the objections you hit are pushed onto the contact page as unvetted knowledge items, deduplicated. In parallel, a follow-up draft is dropped in draft status. The queue lists the drafts to handle. Marking a draft sent or discarded pulls it out of the queue without sending anything: the real send stays an explicit action in Inbox or Email.
Desktop copilot
The desktop companion reads this hub through a read-only API surface, authenticated by key and scoped to the workspace: recent calls, upcoming meetings agenda, open tasks, the prospect 360 context, objection coaching. The copilot chat shares the same brain as the Kernel chat, but only exposes read tools, with no mutation.
How to use it
- 01
Prepare
Before the call, the copilot reads the upcoming meetings agenda and the prospect 360 context: past objections, transcripts, transactions.
- 02
Consent
You record the consent decision. Without an effective grant, the recording is neither kept nor processed.
- 03
Record
The call is captured by Fathom or by telephony, then ingested: transcript, summary, contact link.
- 04
Answer objections
During the call, a detected objection surfaces the script for the right type, written by you, ready to read.
- 05
Close
Post-call, the objections you hit go to the contact page and a follow-up draft is dropped.
- 06
Follow up
You review the draft in the queue, send it via Inbox or Email, or discard it. The queue clears.