Back

Integrations

Deploy everywhere. In minutes.

Connect your AI agent to the published channels and business tools below. WhatsApp and Instagram use official Meta APIs; availability, plan requirements and operational limits are stated per integration.

Try in 3 minutes
Official Meta APIs

WhatsApp Business and Instagram connect through Meta's official APIs rather than password sharing or a reverse-engineered client.

Keep the WhatsApp Business app with coexistence.

For eligible numbers, Meta's coexistence flow connects the WhatsApp Business app and Cloud API at the same time. Eligibility and message history behaviour depend on Meta's current rules, so verify the number during onboarding.

Messengers & channels

Meta Verified

WhatsApp Business

Official Meta Cloud API. Eligible numbers can keep the WhatsApp Business app through coexistence.

Meta Verified

Instagram

Official Meta integration through our own infrastructure. No third-party DSP dependency. Replies to DMs and story mentions.

Telegram

Connect your bot for automated conversations and lead capture.

Phone / voice

Inbound and outbound calls through the built-in voice agent; billed per connected voice minute.

Website widget

Embed an AI chat widget on your site. Converts visitors into leads.

Online chat

Share a link to your AI agent. Great for testing and quick demos.

CRM systems

amoCRM

amoCRM

Auto-create leads, update deals, sync conversations.

Bitrix24

Manage leads, track sales funnels, sync contact data.

Step by step: connect amoCRM and Bitrix24

Payments

Kaspi Pay

Kaspi Pay

First payment gateway launched. Pleep sends a Kaspi link inside the chat, lead pays in one click, deal closes itself. Card and account methods supported.

Custom gateway

Payment gateways outside the published catalogue are scoped as a separate integration.

Business tools

Google Calendar

Auto-schedule meetings and manage availability.

MoySklad

Check inventory, process orders, sync product data.

Altegio

Auto-book appointments and manage reservations.

Wazzup

Multichannel messaging gateway for unified communications.

Tools & APIs

Integration scope

Define the read and write actions an external system must support before implementation begins.

Custom systems

Connections outside the published catalogue are reviewed and estimated separately.

Webhooks

Use supported events to notify your endpoints; confirm the required events during integration design.

Public API

Programmatic access to conversations, contacts, knowledge base. Available on Pro.

Online booking: the agent runs the calendar itself

Booking is a conversation, not a form. The agent connects to Altegio or Google Calendar, reads the live calendar and carries the customer from "any openings on Saturday?" to a created appointment without handing the chat to an administrator. The steps below are shown on Altegio, because there the schedule is already broken down by staff and service.

01

Reads services and staff

The agent first pulls the salon's services, the staff who perform them, their durations and prices from Altegio. From there it works with the salon's real identifiers rather than a remembered description of the service list.

02

Offers live openings only

Availability comes from the calendar at the moment of the conversation, and the agent offers only the slots Altegio returned. It does not reuse times mentioned earlier in the thread: the calendar changes constantly and yesterday's opening may already be taken.

03

Verifies the slot before booking

The time the customer picks is checked against the live calendar before the appointment is created. If the opening was taken during the conversation, no appointment is created and the agent offers another time.

04

Creates the appointment

The appointment lands in the Altegio calendar with the customer's name and phone, tied to a specific staff member and service. The administrator sees it in the same place as manually created bookings.

05

Reschedules and cancels

A reschedule is done as a move, not as a cancel plus rebook: the appointment keeps its identity and its service, only the time and optionally the staff member change. No duplicate appears for the same customer.

The agent reads a live calendar from Altegio and from Google Calendar. Every step but the first works in both: the catalogue of services and staff exists only in Altegio, so there the appointment is tied to a service and a staff member, while in Google Calendar it is an ordinary meeting in a free slot. Altegio suits salons and clinics whose schedule is kept per staff member, Google Calendar fits better where meetings go into a shared team calendar. Online booking is available from the Business plan up. If the schedule lives in a third system, these steps will not work until we connect it separately.

Clinics, medical centres, salons and barbershops

Online booking matters wherever you sell a specialist's time. The mechanics are the same across these verticals; what differs is what the agent must establish before booking.

Beauty salon and barbershop

Customers usually write "when do you have an opening" rather than naming a service. The agent establishes the service and the staff member first, because duration and availability depend on them, and only then shows slots.

Clinic and medical centre

Here the specialty and the reason for the visit matter more before booking, otherwise the patient lands with the wrong specialist. The honest caveat: the agent works with the schedule in Altegio or Google Calendar, we have no separate integration with medical information systems, and it does not diagnose.

Solo practitioner and small studio

One calendar, one or two services. Setup comes down to connecting Altegio or Google Calendar, because there is no staff member to choose between.

Chain with several locations

Each location keeps its own calendar. The agent works with the identifiers of the salon it is connected to and does not mix openings across locations.

The full walkthrough: booking clients into a beauty salon

What sits on which plan

Channels, booking and CRM sit on different plans, so the honest way to price this is by your own configuration rather than by the smallest number.

Light

The entry plan, around 42,380 tenge a month for 1,500 messages and one messenger. The agent replies, runs the conversation and works from the knowledge base, but online booking is not on it.

Business

The plan online booking lives on: Altegio and Google Calendar connect here. It is also where you move for conversations and deals written into amoCRM or Bitrix24, for broadcasts and for a second and third messenger.

Pro

Adds access to the Pleep API if your own team writes the integrations.

The per-message rate is the same on every plan and billing follows volume rather than headcount. The calculator in the pricing block on the home page prices your configuration.

Published capabilities, explicit boundaries.

Reliability starts with knowing which connection is native, which plan it needs and what must be tested before traffic is switched on. Enterprise SLA terms are agreed in the contract, not implied by a marketing page.

2

Native CRM integrations

2

Booking calendars

Pro

Pleep API access

WhatsApp and Instagram use official Meta APIs
amoCRM, Bitrix24, Altegio and Google Calendar are available from Business
Pleep API access is available on Pro
Test permissions, field mappings, duplicate handling and rollback before launch
FAQ

Frequently Asked Questions

Yes, if the schedule is kept in Altegio or Google Calendar and the Business plan is active. The agent pulls services and staff, offers openings from the live calendar, verifies the chosen time and creates the appointment. The administrator sees it in the same place, next to manually created bookings.

From the connected calendar, Altegio or Google, at the moment of the conversation. Only the slots the integration returned are offered. The agent does not reuse times mentioned earlier in the thread, because the opening may already be taken.

The agent moves the appointment rather than cancelling and rebooking. It keeps its service and only the time, and optionally the staff member, changes, so no duplicate appears for the same customer. Cancelling is available as a separate action. The honest caveat: in Altegio the agent moves and cancels the appointments it created itself, while one the administrator took over the phone is changed by the administrator. In Google Calendar the agent can look an event up in the calendar and works with those too.

It does, provided the doctors' schedule lives in Altegio or Google Calendar: the booking mechanics are the same as in a salon. We have no separate integration with medical information systems, and the agent does not diagnose. It establishes the specialty and the reason for the visit and books with the right specialist.

Telegram and simple account connections can take minutes. CRM and booking launch time also depends on permissions, field mapping and a test record. WhatsApp Business and Instagram use official Meta APIs, and Meta eligibility or verification can add time.

Pleep currently integrates with amoCRM and Bitrix24, automatically creating leads, updating deals, and syncing conversation data. Additional CRM integrations are on the roadmap.

The published self-service path is the Pleep API on Pro. A connection to another HTTP or MCP-based system must be scoped and verified separately; the site does not promise that every external server connects in one click.

Yes. Pleep offers a full API on the Pro plan, allowing you to build custom integrations with any tool or system your team uses. The API supports all core agent functions including conversations, contacts, and knowledge base management.

Stop dependent automation, preserve the failed payload and retry only when the external system confirms recovery. Monitoring and SLA obligations depend on the integration and your contract; this page does not claim a blanket uptime guarantee.

Connect the systems you actually use.

Start with a verified channel, map one real workflow end to end, and test the result before scaling traffic.

Try in 3 minutes