Lead qualification & follow-up

Every inbound lead gets a considered answer in minutes - scored against your ICP, written in your voice, and logged where your pipeline already lives.

Talk to us Read the docs

The brief

Written like you’d brief a person.

This is the whole setup - a procedure in plain language, with tools and specialist agents referenced inline. When it runs is not written here: that’s the trigger, configured beside it.

Qualify the lead against the ICP, create the record with #yekar.salesforce.create-record, draft the first reply with #yekar.gmail.create-draft, and notify the owner with #yekar.slack.send-message. Outreach goes out only after review.

How it runs

From trigger to logged outcome.

Trigger

API - Your site's form posts each lead through an API trigger

Score against the ICP
Reads the submission and scores fit against your stated profile.
Create the record
Writes the lead into your CRM with the scoring rationale.
Draft the first touch
Writes the reply that fits the segment, in your voice.
Hand off warm
Notifies the owner with the context, and books the call on a reply.

Where people stay in control

Nothing consequential runs on its own.

First-touch outreach is reviewed before it sends - the agent drafts, a person approves.

Tools it uses

Runs on accounts you already have.

Salesforce
HubSpot
Gmail
Slack
Google Calendar

Connected once, governed per agent - this use case gets only the tools listed here.

Illustrative savings

$1,200–$3,100 / month

Assumes 150–500 inbound leads a month at 10–15 minutes of research and drafting each.

Illustrative monthly savings, estimated from typical handling time at public salary benchmarks, reviewed August 2026. Not a promise or a guarantee - your numbers depend on volume and process.

What makes this dependable

Build the agentBrief an agent in plain language Keep people in controlPut people in front of risky writes Put it to workStart agents through an API trigger

All use cases →