Google CalendarIntegration · Calendar

The agent books into your real calendar, not a form

Alenta reads your live Google Calendar availability mid-conversation and writes the event when the visitor agrees to a time. No double-booking, no callback to confirm.

All integrations

About a minute to a working agent. Nothing goes live on your site until you install the snippet.

Animation: a visitor chats with the agent and the result is written to Google Calendar during the conversation.

One job booked at 2am covers the year. A missed after-hours call covers nothing.

The problem

“Someone will call you back to confirm” is where bookings die

A visitor who is ready now will not wait for a callback tomorrow. Every hour between the request and the confirmation is an hour they can spend booking with somebody who answered immediately.

How it works

What happens, in order

  1. 01

    Connect with OAuth

    One consent screen. Alenta asks for calendar read and write on the calendars you pick, and nothing else.

  2. 02

    Set your rules

    Appointment durations, buffers between jobs, the hours you actually take work, and how far ahead a visitor may book.

  3. 03

    The agent offers real slots

    It reads free/busy at the moment it is asked, so the two times it offers are two times you genuinely have.

  4. 04

    It writes the event

    Confirmed while the visitor is still on the page, with their name, contact and what they asked for in the event body.

What it sounds like

A real exchange, start to finish

Worked example, reading live availability.

Animation of the worked example, reading live availability.
Specifics

Built into the conversation

  • Free/busy read at conversation time, not from a cached copy
  • Per-service durations and buffers, so a survey and a repair do not get the same slot
  • Business hours and holidays respected, including your lunch break
  • The transcript is attached to the event, so you walk in knowing what they asked
  • Cancellations and reschedules flow back without a second tool
  • Scoped to the calendars you select at connect time
Before you ask

Common questions

Can it double-book me?

It reads free/busy at the moment it offers a time and writes the event immediately on acceptance, so the window where two visitors could take the same slot is the length of one exchange. Buffers give you margin on top.

Which calendars can it see?

Only the ones you select during the OAuth consent. It cannot read calendars you did not grant, and you can revoke access from your Google account at any time.

What if I use more than one calendar?

Pick which ones count as busy and which one receives new bookings. A shared team calendar for availability and a personal one that stays private is the common setup.

Point it at your site and watch it read.

About a minute from pasting your URL to talking to a working agent. Nothing appears on your website until you install the snippet yourself.

One job booked at 2am covers the year. A missed after-hours call covers nothing.

See plans and book a demo
The guarantee

If your agent does not capture a single lead in its first 30 days live on your site, that month is free.

A lead means a visitor who left contact details or booked an appointment — a number you can read off your own dashboard, so neither of us has to take the other’s word for it. It has to be installed and your site has to be getting visitors; we cannot conjure traffic that is not there.