Support & Ticketing · Integration
Crisp
Add Crisp to your product for your customers, and give your AI agents governed access to it.
Crisp is a shared inbox that started from live chat, so conversations are real-time first and the object model shows it: a conversation belongs to a website, and a person profile accumulates across sessions rather than being recreated per chat. That profile is the part worth integrating, because it carries the context that makes a reply useful rather than generic. Messages have types, so a note, a file and a text reply are not interchangeable, and sending the wrong one is visible to the customer. Websites are the tenancy unit and each carries its own identifier, which maps cleanly onto per-customer connections. fastn scopes each customer's credentials to their own website.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Crisp website so chat conversations appear inside your product.
Read the person profile behind a conversation, which is what makes a reply specific.
Send a message or add a private note, with the distinction preserved.
React the moment a conversation starts, which for live chat is the only moment that matters.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a conversation and the person's history before drafting a reply.
An agent updates a person profile within governed permissions, with the write audited per tenant.
An agent reacts to a new conversation and routes it using the profile rather than the first message.
Example prompt
Summarise this person's conversations and what they have asked about before.
Set up Crisp in 4 steps
- 01Enable the Crisp connector from your fastn dashboard.
- 02Have each customer authorise their own Crisp account, so calls run under their credentials rather than a shared key.
- 03Decide which conversations, customers and tags your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Crisp integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Crisp integration without building it. Your customers connect their own Crisp account inside your product and work their conversations, customers and tags there, with no per-customer code on your side.
- Handle the part that actually costs time: support volume is spiky, and support teams notice latency immediately. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Crisp update is not your on-call problem.
- One integration serves your product and your agents. The same governed Crisp connection powers in-product features and gives AI agents scoped, audited access, so you let support work your customers' queues without leaving your product without wiring it twice.
Used by these teams
Compare with
Intercom
Help Scout
FrontOften used alongside
Tools the same teams tend to run next to Crisp, across other categories.
Salesforce
HubSpot
Slack
NetSuiteCrisp integration FAQ
How do I add a Crisp integration to my product?
Enable the Crisp connector in your fastn dashboard, then let each customer authenticate their own Crisp account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Crisp client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Crisp account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Crisp account and only ever sees their own conversations, customers and tags. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Crisp integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a conversation and the person's history before drafting a reply.
Who maintains the Crisp integration?
fastn does. When Crisp changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can an agent resolve a Crisp conversation end to end?
An agent can read the full history, post replies, change status and route within the permissions you grant it. Every action is attributed and audited, so you can show exactly what the agent did rather than inferring it.
Do I get notified the moment something changes in Crisp?
Yes, through event triggers rather than polling, so your product reacts to a new or escalated conversation in near real time.
What can I build with the Crisp integration?
A common starting point: let a customer connect their own Crisp website so chat conversations appear inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Crisp integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Crisp does not change your per-connector cost. You can start free with 3 connected accounts.
Add Crisp to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.