AI-Powered Patient Communication
Loquent is an AI communication platform that helps healthcare practices automate patient interactions across voice calls, WhatsApp, and SMS. Our AI agents handle appointment booking, confirmations, reminders, and feedback — reducing front-desk workload while improving patient experience.
How It Works
Inbound Flow
Patient calls or chats → AI Agent answers → Books appointment → Saved in your DMS
Outbound Flow
Your DMS appointments → Loquent syncs → AI calls/messages patients for confirmations, reminders, and feedback
Required API Capabilities
We need your platform to expose the following capabilities via REST API. You can implement these using your existing API structure and authentication methods.
Proactive Patient Communication
Our AI agents proactively reach out to patients via voice calls, WhatsApp, and SMS using synced appointment data from your system.
Appointment Confirmation
Reduce no-shows by confirming patient attendance. Based on response, confirm, reschedule, or cancel.
Fallback: WhatsApp / SMS
Appointment Reminder
Ensure patients remember their appointment and arrive on time. Sent from previously synced data.
Post-Visit Feedback
Collect patient satisfaction feedback through a brief AI conversation after their visit.
Fallback: WhatsApp
What Data We Need for Outbound
For outbound campaigns to work, the appointment data returned by API #8 must include:
Technical Requirements
Authentication
We support multiple auth methods:
- API Key (Bearer token)
- OAuth 2.0 (Client Credentials)
- Basic Authentication
- Custom authentication
API Format
- REST API (preferred)
- JSON request/response format
- Standard HTTP methods (GET, POST, PATCH, DELETE)
- Standard HTTP status codes
- Clear JSON error messages
Performance
- Response time: < 2 seconds (p95)
- Availability: 99.5% uptime or better
- Timeout: 30 seconds minimum
- HTTPS required (TLS 1.2+)
- Rate limit: 100+ requests/min per client
Webhooks (Optional)
If your system supports webhooks, we can receive real-time notifications — reducing polling and enabling instant responses to changes.
appointment.createdNew appointment bookedHighappointment.cancelledAppointment cancelledHighappointment.rescheduledDate/time changedHighappointment.completedAppointment completedMediumappointment.status_changedAny status changeMediumpatient.updatedContact info changedLowExample Webhook Payload
{
"event": "appointment.created",
"timestamp": "2026-03-10T14:30:00Z",
"data": {
"appointmentId": "apt-12345",
"status": "confirmed",
"date": "2026-03-15",
"startTime": "09:00",
"endTime": "09:30",
"type": "cleaning",
"provider": {
"id": "dr-001",
"name": "Dr. Smith"
},
"patient": {
"id": "pat-67890",
"firstName": "Sarah",
"lastName": "Johnson",
"phone": "+14155551234",
"email": "sarah@example.com"
},
"location": {
"id": "loc-001",
"name": "Main Office"
}
}
}Expected Data Volume
Per dental practice, to help you plan capacity.
| Operation | Volume / Day | Notes |
|---|---|---|
| Check availability | 50-200 | Peaks during business hours |
| Book appointment | 10-50 | Depends on practice size |
| List appointments (sync) | 96 | Every 15 minutes |
| Cancel / Reschedule | 5-20 | Lower volume |
| Get appointment details | 20-50 | On-demand lookups |
Security & Compliance
How We Handle Patient Data
- Minimal data access — only appointment & contact info
- Encryption in transit (TLS 1.2+) and at rest (AES-256)
- Each practice's data is fully isolated (multi-tenant)
- Appointment data cached temporarily, not retained long-term
- Patient data is never sold or shared with third parties
- Patients can opt out of communications at any time
Infrastructure & Compliance
- Hosted on AWS (US regions) with industry-standard security
- Per-practice API credentials stored encrypted
- Support for API key rotation without interruption
- Audit logs of all API interactions
- Actively working toward HIPAA compliance
- Happy to discuss BAA timeline
Integration Process
Discovery
1 weekDiscuss your API capabilities and share documentation
Credentials
1 weekProvide sandbox/test environment and API credentials
Development
2-3 weeksWe build and test the integration adapter
Testing
1 weekEnd-to-end testing with sample data
Pilot
2 weeksLaunch with 1-2 mutual dental practice clients
Production
OngoingRoll out to all interested practices
What We Need From You
- API documentation (endpoints, auth, request/response formats)
- Sandbox/test environment with sample data
- Test API credentials
- Technical contact for integration questions
- SLA commitments (uptime, response time, support)
- List of mutual clients interested in the integration
What We Provide
- Dedicated integration team and technical contact
- Co-marketing opportunities
- Practice onboarding support
- Technical documentation for mutual clients
- Integration monitoring and error alerting