Integrations

Your customers choose the channel. You get one queue.

Email, chat, WhatsApp, SMS and your own applications all feed the same tickets, the same customer records and the same reports.

✉

Email

The channel your customers already use. Incoming mail becomes a ticket; replies go out from your own address and thread correctly.

·POP3/IMAP fetching into departments

·SMTP sending from your domain

·Email parser rules by subject or sender

·Reply-to-ticket threading

·Auto-acknowledgement templates

💬

A small script on your website opens a chat that becomes a ticket if nobody is available — so conversations are never lost at closing time.

·Knowledge-base answers inside the widget

·Staff takeover at any moment

·Offline messages become tickets

·Full transcript on the customer record

📱

Two-way WhatsApp conversations and SMS status updates, attached to the same ticket as the customer’s emails.

·Inbound WhatsApp becomes a ticket

·Outbound replies from the ticket screen

·SMS notifications on status change

·One thread across all channels

🔗

A documented HTTP API for creating and reading tickets, plus webhooks that fire when something happens.

·Create tickets from your own app

·Sync customers from your CRM

·Webhooks on create, reply, status change

·Token-based authentication

🔐

Let staff sign in with the accounts they already have, and keep administrator access behind a second factor.

·Single sign-on (OAuth)

·Two-factor authentication

·Password policy enforcement

·IP restrictions for admin access

🤖

Bring your own Claude or OpenAI key — every AI feature runs from your account, on your data, on your server.

·Draft the first reply for the agent

·Answer chats from your knowledge base

·Summarise long ticket threads

·Detect intent, sentiment and language

The API and webhooks cover most cases. For billing systems, CRMs and in-house software we build the connector as part of onboarding.