Open A3.Tickets

Channels and integrations

Where tickets come from, where their data goes and how A3.Tickets connects with other A3 products.

Ticket channels

Each channel is connected in company settings without a developer. The operator’s reply goes back to the customer wherever they wrote from.

  • Email

    Your mailboxes via IMAP and SMTP, replies in the same email thread.

    In every plan

  • Website online chat

    A widget added with one line of code, in your site’s colors.

    In every plan

  • External form and portal

    A request form for any page and a “My tickets” page.

    In every plan

  • Telegram

    A bot receives messages and greets the customer with buttons.

    “Business” plan and above

  • VK

    Community messages become tickets.

    “Business” plan and above

  • MAX

    A MAX bot in private chats with customers.

    “Business” plan and above

CRM

A ticket creates a lead or a deal, and a comment appears in the CRM when it is closed. The sync log shows every transfer and lets you retry a failed one.

“Pro” plan and above
  • Bitrix24Contact lookup, lead or deal, closing comment.
  • amoCRMContact lookup, deal, closing comment.

A3 products

A3.Tickets works within the A3 ecosystem: one sign-in, shared billing and shared file storage.

For developers

If the integration you need is not here, connect your own system via the API and webhooks.

  • REST API

    API keys, request log, public documentation.

  • Webhooks

    Seven ticket events, HMAC-SHA256 signature, retries and delivery history.

  • Portal sign-in

    A customer already signed in on your side opens “My tickets” without a second sign-in.

More about the API

Planned

  • WhatsApp and Viber
  • Instagram Direct after Meta review
  • Deal status sync back from the CRM
Product roadmap

Need an integration that is not listed?

Tell us which system your support works with. We will suggest how to connect it via the API and webhooks.

Discuss implementation