Operations · scenario 2 of 5

Calls answered and appointments booked, day and night

I build an AI receptionist that answers your phone, checks your calendar and books the appointment during the call. Confirmations, reminders and changes run without anyone at the desk.

How it works

  1. 01 · Event

    The phone rings

    During a job, after hours or while the line is busy.

  2. 02 · Data

    Need and time

    What, where and when; audio is not stored.

  3. 03 · AI

    Fit and slot

    The AI decides whether the job fits your services and area; free slots come from the calendar, never from memory.

  4. 04 · Action

    Booked and confirmed

    The appointment goes into your calendar, the caller gets an SMS, you get a summary email.

  5. 05 · Check

    Reminders and changes

    Reminders go out; rescheduling and cancellations update the calendar.

  6. 06 · Human

    Escalation, not improvising

    A call it cannot complete safely comes to you, with everything captured.

What you get

  • Calls during a job or after hours still become appointments.
  • Bookings come from the live calendar, not from notes.
  • You read a summary instead of calling back.

Example

This is DienstBot, which I built and run for Austrian service businesses. A business connects its Google account, sets up call forwarding, and the agent is live. Every time the AI states comes from an explicit function call, so it cannot invent a free slot.

Privacy by design

The AI sees the request and the calendar data needed to book. Audio is processed in memory, never written to disk. The appointment and the summary stay.

Typical stack

SIP telephony · real-time speech (STT, LLM, TTS), EU-hosted · Google Calendar · SMS and email

Built into what you already run: your CRM, telephony, n8n instance or cloud stay in place. I can also take over an existing workflow or join a running project.

Describe what slows you down.

You get back what to automate first — and what not to.

Have a defined project already? Send the brief.