Get started

How we follow up with every inbound lead

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.

Written by
The OpenChatly Team
Published
March 18, 2026
Reading time
7 min read
Topics
Sales, Case Study, Growth

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.

Team
Kortix
Connected systems
HubSpot · Email · Google Calendar
Trigger
Scheduled HubSpot sweep (every 15 min)
Mode
Trigger-driven · human-gated

The problem

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.

What we built

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.

How it works

1

Copy the setup prompt into a new session

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.

Setup prompt

Set up a lead follow-up agent in this workspace.

  1. 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.

  2. Create the skill skills/lead-followup/SKILL.md with these rules:

    • A new lead is a contact on lifecycle stage lead without the kortix_followup_drafted property. Skip every contact that has it.
    • Research the company's public site first. Each draft references one specific fact from that research and asks exactly one qualifying question.
    • Check Google Calendar for the next open 30-minute slot and propose that one time. Never create, move or accept an event.
    • Write the research notes back to the HubSpot record. Never change deal stage, pipeline or lifecycle stage.
    • Never send. Hold every draft in the email channel for a rep to review, edit and send, then set kortix_followup_drafted on the contact.
  3. 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."

  4. Tell me which of these connectors are not connected yet.

  5. Open a change request with all of it. Do not merge it.

2

Connect your tools

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.

HubSpot

Reads new leads and logs the follow-up on the record.

Or useSalesforcePipedrive
Required
Google Calendar

Finds open slots to propose for a call.

Or useCalendly
Required
Gmail

Drafts the personalized follow-up email for approval.

Or useMicrosoft Outlook
Required
3

Run it once with this prompt

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.

Prompt

Run one new-lead follow-up sweep on HubSpot.

  1. Find contacts on lifecycle stage lead that do not have the kortix_followup_drafted property.
  2. For each lead, read the company's public site and note one specific fact about what they do.
  3. Draft a follow-up to our sales playbook that uses that fact and asks one qualifying question.
  4. Check Google Calendar for the next open 30-minute slot and propose that one time. Do not create the event.
  5. Write the research notes to the HubSpot record, hold the draft in the email channel, and set kortix_followup_drafted. Do not send anything.
4

Let the 15-minute schedule take over

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.

kortix.yaml
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.
5

Hold every follow-up as a draft

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.

6

Read the drafts

Each sweep ends with drafts in the email channel. This is what a run looks like in the session:

New lead follow-up sweep · 10:15
Load the lead-followup skill and run one new-lead sweep.
Worked for 2m 41s
hubspot · search contactsweb · read company site × 4google calendar · find free slot × 4hubspot · update contact × 4email · save draft × 4

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.

Illustrative example. Your counts depend on how many leads arrive.

The pattern

Connect the CRM via a trigger on new leads, give the agent scoped connectors into HubSpot, email, and the calendar, encode the sales playbook as skills and memory, and gate every send behind a human.

Make it do more

Once it works, paste any of these into the same session.

Follow up on silent leads

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.

Daily unsent-drafts digest

Every weekday at 17:00, post a list of the follow-up drafts that no rep has sent yet to #sales.

Match the lead source

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.

Guardrails

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:

  • Isolation. Each sweep runs in its own isolated sandbox — a fresh session that can cover several new leads at once, each handled as an independent unit so a failure on one never blocks the rest. Only the drafts it produces are written back out.
  • Scoped secrets. The HubSpot, email, and Calendar credentials are encrypted in the secrets manager and injected into the sandbox at runtime, scoped to the agents you grant them to.
  • Human approval gate. No message reaches a lead without a person reviewing the draft and sending it.
  • Everything is code. The agent's persona, skills, and permissions are files in the repo — versioned and changed through a reviewed change request, not a dashboard setting.

The outcome

Researched and followed up, not just the easy ones
Every lead
Personalized follow-up ready while the lead is still warm
Same-day
HubSpot, email, and the calendar in one agent
3 systems

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.

On this page

  • The problem
  • What we built
  • How it works
  • Make it do more
  • Guardrails
  • The outcome

Run this yourself

Install this exact setup — agent, connectors, schedule, and guardrails — in a guided flow.

More use cases.

  • How we handle GDPR data-subject requests on a deadline

    Legal·July 11, 2026

  • OpenChatly

    How we keep our docs in sync with the code

    Documentation·July 5, 2026

  • OpenChatly

    How we QA every pull request automatically

    QA·July 5, 2026

Own your AI.Start today, in our cloud.

Start for free

OpenChatly is the AI workspace for everything. One person directing, agents executing, from goal to finished work.

©2026 OpenChatly AI.沪ICP备2025124785号-5

Resource guide

  • Product overview
  • Skills marketplace

Terms of service

  • User agreement
  • Privacy policy

Contact us