Integrations

One brain. Multiple systems.

Mako connects to what you already run. Nothing here is a migration, and nothing here asks you to change where your customer record lives.

Everything on this page is labelled. Available means it is running in production today. Anything else says so plainly.

Ask about your system How connections work

CRM

Where your record lives.

Mako reads context from your CRM and hands intelligence back to it. The CRM stays the system of record in every case.

GoHighLevel

Available

The first adapter, running in production. Inbound conversations route to Mako and replies come back into the GHL conversation on the location's own number.

ForgeConnect

In development

Connects through the gateway with per-organisation credentials, draft or auto reply, and a full audit trail of every turn inside the CRM itself.

Direct API

Available

Any system that can make an authenticated HTTPS call can connect without waiting for a named adapter. This is how a platform integrates on its own timeline.

Other dealership platforms

Planned

Additional automotive CRM and DMS adapters are on the roadmap. We will not name one as available until it is running for a real customer.

Channels

Mako is not an SMS bot.

The brain is channel-independent; a channel is an adapter with its own rules. What may be said on a public listing is not what may be said on a consented thread.

Text messaging

Available

Two-way SMS through your existing numbers. Consent, opt-out and quiet hours stay enforced by the system that owns the customer relationship.

CRM messenger

Available

Replies land in the conversation thread your team already works from, rather than a second inbox nobody watches.

Public marketplace listings

Available

Public, unconsented threads run under deliberately narrower rules — the listing states the price, the agent does not.

Website chat

Available

An embeddable widget for conversations that start on your own site.

Email

Planned

A different rhythm and a different length than messaging. Treated as its own adapter rather than SMS with a subject line.

Other messaging platforms

Planned

The engine does not care which channel a conversation arrives on. New ones are adapter work, and we will label them when they ship.

Your services

Events out, in a shape you can verify.

Mako pushes what happened to endpoints you register, signed so you can confirm it came from us.

What you receive

A reply was produced. A deal moved stage. A conversation was escalated to a human. An integrity alert was raised. Enough to drive your own workflows without polling us.

How you trust it

Every event is signed with a secret only your endpoint and the gateway hold, over a payload that includes a timestamp — so a captured request cannot be replayed at you later. Delivery attempts are logged, failures included.

Not on the list?

The honest answer about your system.

If your CRM is not named above, one of two things is true, and we will tell you which on the first call.

It can call out

Then you can connect today through the direct API without waiting for us to build anything named after your platform.

It needs an adapter

Then it is scoped work with a timeline, and we will say so rather than describing it as a configuration option.

Tell us what you run.

We will tell you whether it connects today, or what it would take.