How we handle GDPR data-subject requests on a deadline
Legal
The sales agent we run on Kortix — connected to HubSpot, email, and Google Calendar. It researches each new lead, drafts a personalized follow-up, and offers a call slot, with a human approving the send.
Inbound leads have a short half-life. A form filled out on Tuesday is worth far more if the follow-up goes out Tuesday than if it goes out Friday, but a good follow-up takes research — who the company is, what they do, why they might have signed up — and that research is exactly what gets skipped when the pipeline is full.
We handle this by putting an agent on every new lead. It researches the company, drafts a personalized follow-up, and offers a time to talk. This writes up how we run that on Kortix — the connections, the steps, and the guardrails.
The follow-up that converts is the one that shows we read the form and understood the company. That takes a few minutes of research per lead, and a few minutes times every inbound is more time than a growing team has. So follow-ups either go out generic or go out late, and both lose deals.
Templates make the sending fast but not the personalization, which is the part that matters. Booking the call adds another round of back-and-forth on top. The work that moves a lead forward is the work that keeps slipping.
Our lead pipeline in HubSpot is connected to an agent running on Kortix. A scheduled sweep spawns a fresh, isolated session — a cloud sandbox — with scoped access to what a follow-up needs: the lead record, the web for research, our email, and the team calendar. It researches each new lead, drafts a personalized message, and proposes a call slot. A human approves before it sends.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the follow-up 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 lead follow-up agent in this workspace.
Create the agent agents/lead-follow-up.md. Its job is to turn each new HubSpot lead into a researched follow-up draft with one proposed call slot. It may use the HubSpot and Google Calendar connectors.
Create the skill skills/lead-followup/SKILL.md with these rules:
Add a cron trigger new-lead-followup-sweep to kortix.yaml. It runs the lead-follow-up agent every 15 minutes with the prompt "Load the lead-followup skill and run one new-lead sweep."
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 your CRM and your calendar. Connect the email account that holds the drafts under Settings → Channels. Credentials are brokered server-side and never enter the agent's machine.
Reads new leads and logs the follow-up on the record.

Finds open slots to propose for a call.

Drafts the personalized follow-up email for approval.
Merge the change request, then start a session with the lead-follow-up agent and send this prompt. Read the drafts and the proposed slots before you let the schedule take over.
Run one new-lead follow-up sweep on HubSpot.
The change request added this trigger to kortix.yaml. From now on the agent
runs every 15 minutes, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: new-lead-followup-sweep name: New lead follow-up sweep on: cron: "0 */15 * * * *" run: agent: lead-follow-up prompt: Load the lead-followup skill and run one new-lead sweep.The agent researches, drafts and updates HubSpot on its own. It never sends an email and never books the call. Every follow-up waits in the email channel until a rep reviews, edits and sends it. When research fails on one lead, the agent logs it and moves on to the next.
Each sweep ends with drafts in the email channel. This is what a run looks like in the session:
Found 4 new leads and drafted 4 follow-ups, each with one qualifying question and a proposed 30-minute slot. Research notes are on all 4 HubSpot records. The drafts are waiting in the email channel for a rep to send.
Once it works, paste any of these into the same session.
Three business days after a rep sends a follow-up with no reply, draft one short second follow-up on the same thread and hold it for review.
Every weekday at 17:00, post a list of the follow-up drafts that no rep has sent yet to #sales.
Read each lead's source and UTM fields, and open the draft with a line that matches how they found us, such as a webinar or a pricing page visit.
Giving an agent the ability to reach out to leads is a brand question as much as a sales one. The relevant controls on Kortix:
Every inbound lead now arrives with the research done, a personalized draft written, and a call slot offered — waiting for a person to approve rather than sitting untouched. The team spends its time deciding which leads to push instead of doing the same research over and over.
The setup relies on four pieces: sandbox isolation per lead, a secrets manager to broker the HubSpot, email, and Calendar tokens, a human approval gate before anything reaches a lead, and memory that improves as deals move.