Skip to content

Last updated:

Helpdesk tickets, an MCP server for Claude and ChatGPT, the REST API and contacts

intoCHAT now connects to the tools around it: hand-offs become helpdesk tickets, AI assistants can work with your agents, and developers get a documented API.

  • NewOpen a Zendesk, Freshdesk, HubSpot, Gorgias or Help Scout ticket for each hand-off by email, with your own ticket fields.
  • NewA remote MCP server lets AI tools read conversations, leads and contacts, chat with your agents and add knowledge.
  • NewConnect intoCHAT to Claude.ai or ChatGPT by signing in, and choose read-only or read and write access and which agents it sees.
  • NewA REST API with account API keys and scopes, described in a public OpenAPI 3.1 spec you can import into Postman.
  • NewContacts on the Leads tab: one record per person, from verified visitors, leads, CSV imports and the API, with custom attributes.
  • NewIdentity verification and a JavaScript SDK tell the agent who a signed-in visitor is and let your site open and control the chat.
  • NewSigned webhooks for new leads, hand-offs, forms, bookings, live chat, returns, order requests, Inbox changes and approvals.

If your team works in a helpdesk, hand-offs can go straight there. In the Helpdesk tickets card on the Setup tab, connect Zendesk, Freshdesk, HubSpot, Gorgias or Help Scout and turn on Open a ticket for each hand-off. With Add ticket fields you fill the helpdesk's own fields from the conversation, the lead or the contact.

AI assistants can now work with intoCHAT directly. The MCP server gives them tools to read your agents, conversations, Inbox, leads, contacts and sources, to chat with an agent and to add text and Q&A knowledge. In Claude.ai or ChatGPT, add intoCHAT as a connector, sign in and choose Read only or Read and write and which agents it may use. You can revoke access under Settings, Account, Connected apps. The MCP server and the REST API are included from Starter.

For developers, the REST API uses keys from Settings, API keys, and its OpenAPI 3.1 spec is published for any tool that reads one. Contacts keep one record per person per agent, with custom attributes that server-side actions can use as {{contact.*}}. Identity verification signs in your logged-in users, and the JavaScript SDK lets your site open the chat, identify the visitor and listen for events.

See it answer from your own website

Paste your website address and chat with an agent built from your pages. It takes about a minute.

Create your agent free

Free plan, no credit card needed.