How we handle GDPR data-subject requests on a deadline
Legal
An agent connected to our call transcripts, HubSpot, and Linear that drafts the recap, updates the deal, and files the follow-up tasks, then holds the email for the rep to send.

After a sales call ends, someone has to write the recap email, answer the questions that came up, update the CRM, and file whatever the team committed to. It's an hour of work that usually happens late, half-remembered, or not at all. The deal stalls not because the call went badly but because the follow-up slipped.
We run an agent on Kortix that does the follow-up the moment a call ends. It reads the transcript, writes the recap, updates the HubSpot deal, and files the tasks in Linear, then holds the outbound email at an approval gate so the rep reviews and sends it. This is how we handle our own post-call follow-up.
The follow-up after a call is where deals leak. The rep just ran the meeting, so the context is in their head, but the writing-up is manual: recap the discussion, answer the open questions, restate the next steps, log it in the CRM, and file the tasks. Done well it takes an hour; done late it's vague; skipped, the deal goes quiet.
The usual fixes don't close the gap. A CRM reminder tells you to follow up but doesn't do any of it. A note-taker that dumps a transcript into the deal leaves the recap, the CRM update, and the tasks for the rep to write by hand. A template email is fast but generic, and it still needs the account context filled in.
On Kortix, the end of a call triggers an agent. When the recording finishes, the transcript spawns an isolated session (a cloud sandbox) with scoped access to HubSpot and Linear. The agent reads the transcript, drafts the recap email with the answers and next steps, updates the deal stage, notes, and contacts, and files the follow-up tasks. The recap email waits at an approval gate for the rep to review and send.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the recap skill and the 15-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a sales call follow-up agent in this workspace.
Create the agent agents/sales-call-followup.md. Its job is to turn each finished sales call into an updated deal, follow-up tasks and a drafted recap email. It may use the Google Drive, HubSpot and Linear connectors.
Create the skill skills/call-recap/SKILL.md with these rules:
Add a cron trigger call-ended-check to kortix.yaml. It runs the sales-call-followup agent every 15 minutes with the prompt "Load the call-recap skill and process every new call transcript in the Call Transcripts folder since the last run."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect the Drive folder your call recorder writes to, your CRM and your task tracker. Credentials are brokered server-side and never enter the agent's machine.

Finds each new call transcript in the connected folder.
Updates the matching deal with the call outcome.
Files one follow-up task per commitment made on the call.
Merge the change request, then start a session with the sales-call-followup agent and send this prompt. Check the deal update, the tasks and the draft before you let the schedule take over.
Process the most recent call transcript in the Call Transcripts folder in Google Drive.
The change request added this trigger to kortix.yaml. From now on the agent
checks for new transcripts every 15 minutes, and each call runs in a new
session on its own cloud computer. To change the interval, edit the cron line,
or open Triggers in the workspace.
triggers:- slug: call-ended-check name: Call-ended check on: cron: "0 */15 * * * *" run: agent: sales-call-followup prompt: Load the call-recap skill and process every new call transcript in the Call Transcripts folder since the last run.The deal update and the Linear tasks are written on their own. The recap email is always a draft, held in the approval channel for the rep to read, edit and send. A call that matches no deal, or more than one, skips the CRM update and is flagged so a person links it to the right deal.
Each run ends with an updated deal, filed tasks and one held draft. This is what a run looks like in the session:
Found 1 new transcript and matched it to one HubSpot deal. Moved the deal to Contract sent, added 2 new contacts and filed 3 Linear tasks. The recap email is drafted and waiting for the rep to review and send.
Once it works, paste any of these into the same session.
Before each scheduled call on an open deal, draft a one-paragraph brief for the rep: the last call's summary, open commitments and unanswered questions.
Every Friday, list the Linear tasks from call commitments that are past due, and name the deal each one belongs to.
When I paste a recap the rep sent, compare it to your draft and write the difference into the recap playbook in memory.
The agent reads customer conversations and writes to the CRM, so the access is scoped and the outbound step stays with a person:
The follow-up now happens while the call is still fresh: the deal is updated, the tasks are filed, and a recap email is drafted and waiting. The rep spends a minute reviewing instead of an hour writing, and no email goes out without a person sending it.