GoHighLevel Scopes & Data Usage
This video demonstrates how EHealthVoice uses GoHighLevel calendar and contact data to power AI-driven appointment scheduling for healthcare practices.
Requested Scopes & How Data Is Used
calendars.readonly & calendars.write
Why: Our AI voice agents need to check real-time calendar availability during live phone calls with patients, and book appointments directly into the practice's GHL calendar.
How data is used: When a patient calls, the AI agent reads available time slots from the GHL calendar to offer scheduling options. Once the patient confirms a time, the agent creates a calendar event with the patient's name, phone number, and reason for visit. No calendar data is stored permanently — it is queried in real-time during the call.
contacts.readonly & contacts.write
Why: To look up existing patient records when a returning patient calls, and to create new contact records for first-time callers who book appointments.
How data is used: During an inbound call, the AI agent searches GHL contacts by phone number to identify returning patients. For new patients, a contact is created with the information collected during the call (name, phone, email, reason for visit). All data handling is HIPAA-compliant with encryption and audit logging.
locations.readonly
Why: To identify which GHL sub-account/location the healthcare practice uses, ensuring appointments and contacts are created in the correct location.
How data is used: During the initial OAuth connection, we read the available locations so the practice can select which sub-account to connect. This is a one-time setup step. Location data is stored only as a reference ID for API calls.
HIPAA & Security Compliance
EHealthVoice is built for healthcare. All patient data is encrypted in transit and at rest. We maintain HIPAA compliance with full audit logging, access controls, and Business Associate Agreement (BAA) support. OAuth tokens are stored encrypted and are never exposed to end users.
© 2026 EHealthMed AI. All rights reserved.