I am currently working on a project involving an AI voice receptionist for a network of car dealerships operating across the country.
There is one central phone number, and all incoming calls are handled through this main line. The company has multiple dealership locations nationwide, and currently a human customer service team (BOK) answers the calls, identifies the correct location, checks availability in the service calendar, and manually enters appointments into their internal system.
The goal is to automate this process as much as possible.
The AI receptionist would:
answer calls,
identify which location the customer is referring to,
collect necessary information (name, phone number, VIN or registration number, type of service),
and most importantly, book the appointment directly into the service calendar.
The volume is significant — approximately 2,000 calls per day.
The main priority for my client is very clear:
they want the appointment to be entered directly into their existing service calendar system, completely bypassing the human customer service team.
However, the challenge is that their internal service system does not provide an API, and there are no plans to introduce one in the near future. There is no official integration mechanism available.
We discussed a few possible approaches.
Initially, I considered creating an intermediary database (for example, a central scheduling database) where the AI would store bookings and then notify the appropriate location via SMS or email. However, this does not fully eliminate the need for human involvement, and the client strongly prefers a solution where the appointment is written directly into the service calendar.
Another idea discussed was using login credentials to access their system — essentially automating the process by logging into the service platform the same way a human would and entering the appointment automatically.
So the key question becomes:
Is using system logins (UI automation / browser automation) a realistic and stable solution at a scale of 2,000 calls per day?
Would such an approach make sense in a high-volume environment?
Would session limits, timeouts, security policies, or concurrent operations become a major issue?
Is there a more stable way to achieve full calendar insertion without an official API?
The client is primarily focused on completely removing the BOK team from the booking process, and direct calendar entry is their main requirement.
Given the constraints — no API, high call volume, and a strong need for full automation — I would really appreciate insight into what would be the most robust and scalable way to approach this.
Information on your n8n setup
- n8n version: 2.7.4
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app): Railway
- Operating system: Windows 10