Jazyk / Language

EN
RegisterGet first meetings
Back to Leeeds
AI sales agent16 August 2026

Between “yes, let's talk” and a meeting in the diary sit four emails. Here, none.

The contact gets three concrete times that are genuinely free. They are held until the contact answers, and once confirmed the event is created with an invitation - only after the reply has gone out.

Sequence editor in Leeeds with an AI agent node set to book a meeting
Three genuinely free timesHeld until they answerEvent only after sendingNo OAuth needed via link

The short verdict

“Sounds interesting, let's talk.” At that moment most companies start sending times by hand: offer three slots, the contact answers a day later, one is gone by then, offer again. Four messages and two days - exactly where interest dies.

Leeeds closes that stretch. With the booking goal the agent looks at the calendar, picks three genuinely free times, holds them and offers them. When the contact takes one, the event with its invitation is created once the reply has gone out, and the lead flips to “meeting booked”.

Why a time cannot be offered by guesswork

Offering a slot somebody has taken in the meantime is worse than offering none. So times are not derived from an assumption about your working hours but from real availability - and offered slots are held, so another contact in the same campaign does not get them ten minutes later.

The second trap is time itself. An hour's error across a daylight-saving change means two people turning up at different moments. Times are therefore computed against real timezone rules, and the contact sees the time in their own zone when it differs from yours.

The third is order. The event is created only after the reply confirming the time has actually gone out. Any earlier and a rejected draft would fill the diary with meetings nobody knows about.

What happens between the reply and the event

A reply arrived → compute free times → hold them → offer → on confirmation and send, create the event.

Times are computed, not estimated

Availability is read from the calendar - busy spans only, never the contents of your meetings. From that, your working hours, active days, meeting length and buffer, a list of possible times is built.

Three are offered, each on a different day

Three consecutive half hours on one morning is a single question wearing three hats. Times are spread across days; when only one day is free, the slots furthest apart are chosen.

Offered times are held

Every offered slot is reserved until the contact answers or the hold expires. Two contacts in the same campaign can never be offered the same Tuesday at ten.

An invented time is flagged

If the reply would state a time we never offered, that is flagged as a risk and the conversation goes to a human - exactly like an invented price. It is the mistake that ends with the contact sitting alone on a call.

The event follows the send

Only once the confirming reply has actually gone out is the event created with an invitation, the other slots released, and the lead flipped to “meeting booked” and marked hot.

Two ways to connect a calendar

Google or Microsoft. The agent sees real availability and creates the event and invitation directly in the calendar. It needs an OAuth app; for Google these are sensitive scopes, so expect a verification that takes weeks.

A subscription link, no OAuth. The client adds a private link to their own calendar app as a subscribed calendar and meetings arrive there on their own. Usable the same day. The limits are stated up front: in this mode Leeeds cannot see meetings agreed elsewhere, so it computes from working hours and its own bookings, and calendar apps fetch the link with a delay.

What you configure. Meeting length, buffer between events, how soon a slot may be, how far ahead to look, how many to offer and how long to hold them. Working hours and days belong to the calendar, not to a campaign.

Cancelling. A meeting can be cancelled from the company card in two clicks. The provider event is deleted first, so the contact gets the cancellation, and only then does Leeeds record it - in that order, so there is never a state of “cancelled here, still in the diary there”.

How it plays out in a real thread

The contact replies “let's talk”: the agent offers three times on different days and names the zone when it differs from theirs.
The contact picks Tuesday at ten: once the confirmation goes out the event is created and the other two slots are released.
The contact proposes a time of their own: the agent does not confirm it alone, it flags it and hands the conversation to you.
The calendar cannot be read: the agent offers no time at all, asks for one in words, and the draft shows why.
You cancel from the company card: the event disappears from the contact's calendar, the slot returns to the pool, and the company goes back from “meeting” to “interested”.

Why it is built this way

A shorter path

01

Reply straight to a slot

Four messages and two days of cooling interest simply disappear.

No double booking

02

Offered means held

Two contacts in one campaign are never given the same time.

No waiting on Google

03

Link works today

The second route starts the same day while OAuth verification runs.

What to take from this

A meeting is the one number a business owner watches. The difference between “the agent replied” and “the meeting is in the diary” is a few hundred lines of calendar code - and four emails nobody has to write.

If you would rather not wait for OAuth approval, start with the subscription link. You know the limits up front and you can switch over whenever you like.

Want meetings out of replies, not more emails?

Connect a calendar and the agent offers only times that are genuinely free.

I want the AI agent

Leeeds · acquisition automation with an AI sales agent