Integrations
Exactly what we read, write and book
Integration claims are only useful if they are specific. Each entry states the read context, the write actions, the booking path, what you must supply, and the test receipt required before anything goes live on your line.
Status vocabulary
- Available
- Built and running in the platform today.
- Configured per customer
- Built, and enabled only once your credentials, mapping and connection test are complete.
- Scoped
- Designed with a defined read and write surface, not yet enabled in a live deployment.
- Planned
- Not built. Listed so the boundary is explicit, with no timeline implied.
We do not publish a Connected status. Connection is a property of your deployment, proven by your own connection test receipt, not of this page.
Platforms
GoHighLevel
Configured per customer- Read context
- Contact record, opportunity and stage, pipeline, calendar availability, owner assignment, tags and consent or do-not-contact flags.
- Write actions
- Create or update contact, create or update opportunity, set stage, add note, create task, apply tag, book appointment.
- Booking path
- Native GHL calendar booking against the calendar you nominate.
- You provide
- Customer owned sub account, API credentials issued by the customer, nominated pipeline, stages, calendar and owner mapping.
- Test receipt
- Connection test writes a test contact and appointment into a staging pipeline and returns a receipt with record ids before launch.
Twilio voice
Configured per customer- Read context
- Inbound call metadata: caller number, called number, timestamps, call status.
- Write actions
- Answer, route, transfer to a human line, end call, write the call record.
- Booking path
- Not a booking surface. Booking happens in the connected calendar or CRM.
- You provide
- Customer owned Twilio number or a ported number, webhook configured to the inbound voice endpoint.
- Test receipt
- Live inbound test call with a recorded transcript and a stored call record.
ElevenLabs conversational voice
Available- Read context
- Turn level audio and transcript for the active session only.
- Write actions
- Synthesised speech for the pinned agent voice. No customer system writes.
- Booking path
- Not a booking surface.
- You provide
- Agent and voice pinned server side. No customer credentials required.
- Test receipt
- Health check on the realtime path plus a completed session transcript.
Google Calendar
Scoped- Read context
- Free and busy windows for the nominated calendar.
- Write actions
- Create, reschedule and cancel events on the nominated calendar.
- Booking path
- Direct calendar booking where the customer does not book through a CRM.
- You provide
- Customer OAuth grant, nominated calendar, working hours and buffer rules.
- Test receipt
- Test event created and removed, with the event id returned in the receipt.
Field service platform (API)
Planned- Read context
- Not implemented.
- Write actions
- Not implemented.
- Booking path
- Not implemented.
- You provide
- Requires customer API access and a scoping session before any commitment is made on timeline.
- Test receipt
- No receipt exists until the integration is built and tested.
Field service platform (partner API)
Planned- Read context
- Not implemented.
- Write actions
- Not implemented.
- Booking path
- Not implemented.
- You provide
- Requires customer API access and a scoping session.
- Test receipt
- No receipt exists until the integration is built and tested.
Webhook and HTTP endpoint
Available- Read context
- Payload your system chooses to send to a signed inbound endpoint.
- Write actions
- Signed outbound POST of call outcome, transcript reference and booking result.
- Booking path
- Booking only if your endpoint performs it and returns a confirmation.
- You provide
- Shared signing secret, endpoint URL, retry and idempotency expectations agreed up front.
- Test receipt
- Signed test payload delivered and acknowledged, with the delivery id recorded.
Voice is inbound only. Nothing on this page enables outbound dialling, and consented follow up messaging runs under the suppression and quiet hours rules described on the trust page.
Keep your system of record
It works alongside your CRM. It never replaces it.
Have the conversation, carry the follow through, then write it back into the platform your team already knows.
01
Conversation
EchoCody answers the inbound call, discloses that it is an AI assistant, qualifies the job and books a real window.
02
Follow-through
EchoCody holds the memory, the owner, the next action and the due time, and runs consented text and email until the record closes.
03
Your CRM
Your platform stays the system of record for scheduling, dispatch and customer history. We read approved context and write the outcome back.
- GoHighLevel
- Your field service platform
- Your CRM
- Your marketing automation
- Zapier / Make
- Webhook / API
We do not describe an integration as connected until it is running on your account.
