Zum Inhalt springen
NeuSo funktioniert es
Fehlerbehebung

Meetings are only confirmed once a real calendar event exists

Fixed a case where an AI Autopilot conversation could mark a meeting as booked without an actual calendar event being created — meaning no invite reached the prospect. A meeting is now confirmed only when a real calendar event has genuinely been created.

When a prospect agrees to a time, the moment that follows is the one that matters most in the whole conversation: the meeting has to actually land on the calendar, and the invite has to reach their inbox. We fixed a case where that final step could be reported as done when it hadn't fully happened.

What was happening

In AI Autopilot campaigns, when a prospect accepts a slot, the AI books the meeting on your connected calendar and then continues the conversation — confirming the time and moving on. In rare cases, the AI could treat a booking as successful and mark the meeting as set even though a calendar event had not actually been created. When that happened, the prospect was told a meeting was confirmed, but:

  • no event appeared on the calendar,
  • no invite was delivered to the prospect, and
  • the conversation advanced past the booking step as though everything was complete.

The result was a confirmation that pointed to nothing — a meeting that existed in the email thread but not on anyone's calendar. For a cold outreach campaign, that's one of the most damaging places to drop the ball: you did the hard part, earned the yes, and then the prospect showed up to an invite that never came.

What changed

A meeting is now treated as confirmed only when a real calendar event has genuinely been created and verified — not on the AI's say-so alone. The system now requires concrete proof that the event exists on your calendar before it will:

  • mark the meeting as booked,
  • send the prospect a confirmation, or
  • move the conversation forward as a completed booking.

If that proof isn't there — if the booking didn't fully go through for any reason — the conversation no longer pretends it did. Instead of sending a false confirmation, the AI safely retries or re-offers a time on the prospect's next reply, so the booking actually completes rather than silently failing. Nothing is marked done until it really is.

Why it matters

The entire point of running outreach is to turn replies into booked meetings. A phantom confirmation undoes that at the last possible moment: the prospect believes a meeting is set, you believe a meeting is set, and neither calendar reflects it. Worse, it erodes trust precisely with the prospects who were most engaged — the ones who said yes.

With this fix, every confirmed meeting in your campaigns is backed by a real calendar event. When the AI tells a prospect their time is locked in, the invite is genuinely on its way. And on the rare occasion a booking can't complete on the first try, the conversation recovers on its own instead of going quiet.

What you need to do

Nothing. The fix is live, and affected campaigns will book correctly going forward. If a prospect recently agreed to a time but never received an invite, the conversation will pick that back up automatically on their next reply.

Alle Neuigkeiten

Akquise, die weiterläuft, wenn du offline bist.Leads, E-Mails, Follow-ups und Antworten, erledigt.

Verbinde unbegrenzte Postfächer und lass KI-Agenten Leads finden, jede E-Mail schreiben und nachfassen. Oder sende deine eigenen Vorlagen im manuellen Modus. Ab $29/Monat.

$1 für 3 Tage · Jederzeit kündbar · Kein Vertrag

Mit KI installieren

Dein Coding-Agent richtet die FirstSales CLI und Skills für dich ein.

Prompt für Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.