INTEGRATION
Elily and Google Calendar
Elily checks live availability in your Google Calendar before offering a time, then creates the appointment with the service, staff member and duration already correct. Your team sees it immediately in the calendar they already use, and nobody has to open another system.
What does Elily actually write into the calendar?
A real event, not a note to follow up. It carries the client's name and contact number, the service booked, the staff member performing it, and a start and end time derived from that service's own duration rather than a default hour.
That last part matters more than it sounds. A cut and a full colour are not the same length, and a service with processing time in the middle is not one continuous block. Getting the duration wrong is how automated booking quietly ruins a day's schedule.
How is availability checked?
At the moment the slot is offered, against the live calendar. Elily reads free/busy times on the calendar you selected and applies your own rules on top: how much notice you need, which staff perform which services, buffers between appointments, breaks and split shifts.
Because the check happens when the offer is made rather than when the conversation started, two clients messaging in the same minute cannot be given the same slot.
What happens when a client reschedules or cancels?
The original event is released and the new one created, as a single change. Cancellations free the slot outright. This is the case most home-built integrations get wrong: adding the new appointment is easy, remembering to release the old one is what gets forgotten, and the result is a calendar that looks full while the chair sits empty.
Which permissions does it use, and what does it do with them?
Elily accesses the list of calendars on the connected account, the free/busy times on the calendar you select, and the ability to create, update and delete the booking events it makes. Google user data is encrypted in transit, OAuth tokens are encrypted at rest, and the data is retained only while it is needed to provide the calendar connection or to meet legal obligations.
It is never sold, never used for advertising, and never used to create, train or improve AI or machine-learning models. Full detail is in our privacy policy.
Would you rather build this yourself?
That is a reasonable choice, and we have written an honest description of what it involves — the automation tools people use, what works within an afternoon, and the parts that break afterwards. See how to connect WhatsApp to Google Calendar.
Common questions
Which Google Calendar does Elily book into?
The calendar you choose during setup, including a shared Google Workspace calendar. Appointments appear immediately for anyone with access to it, on any signed-in device.
What calendar permissions does Elily need?
Read access to see the calendars on the account and the free/busy times on the one you select, and write access to create, update and delete the booking events it makes. It does not read the contents of unrelated events.
What happens if two clients ask for the same slot?
Availability is checked at the moment a slot is offered, not when the conversation started, so the second client is offered alternatives instead of being double-booked.
Does rescheduling free the original slot?
Yes. A reschedule releases the old time and holds the new one. A booking system that adds the new appointment without freeing the old one leaves an invisible gap, which is worse than no automation.
Can I still edit appointments in Google Calendar directly?
Yes. Your team can move, edit or cancel events in Google Calendar as usual, and Elily reads the calendar as it is rather than assuming it owns it.
Can I disconnect the calendar later?
Yes. You can ask us to disconnect your calendar and delete the Google user data we retain, or request deletion when you close your account, by emailing contact@srileo.com.
PRIVACY
Google API Services Limited Use
Elily's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs adheres to these Limited Use restrictions: such data is not used to create, train, or improve any machine learning or artificial intelligence models.
THE NEXT MESSAGE CAN BE HERS
Watch a booking land in your calendar.
Send Elily your website link. She reads your services and hours, answers as your business, and books into the calendar your team already opens every morning.
Last updated