Support & Ticketing · Integration
Kustomer
Add Kustomer to your product for your customers, and give your AI agents governed access to it.
Kustomer is built around the customer record rather than the ticket, which is a genuine architectural difference and not marketing. Conversations hang off a customer timeline, so the same person contacting you by email and by chat is one thread of history rather than two unrelated tickets. For an integration that means the customer object is the right entry point and the conversation is the child, which is the reverse of most help desks. Custom attributes on the customer are where teams put the fields that matter to them, so mapping them is the difference between a useful panel and a generic one. fastn scopes each connection per tenant and keeps the field mapping out of your code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Kustomer org so support history appears inside your product.
Read the customer timeline rather than a single ticket, which is what makes the context useful.
Send a message or add a note from your product, on the right conversation.
React when a conversation is created or changes status, rather than polling.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a customer's timeline across channels before drafting a reply.
An agent updates a custom attribute within governed permissions, with the change audited per tenant.
An agent triages a new conversation using the customer's own history rather than the message alone.
Example prompt
Show this customer's conversations across every channel and summarise what they have been asking about.
Set up Kustomer in 4 steps
- 01Enable the Kustomer connector from your fastn dashboard.
- 02Have each customer authorise their own Kustomer 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 Kustomer integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Kustomer integration without building it. Your customers connect their own Kustomer 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 Kustomer update is not your on-call problem.
- One integration serves your product and your agents. The same governed Kustomer 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
Zendesk
Intercom
FrontOften used alongside
Tools the same teams tend to run next to Kustomer, across other categories.
Salesforce
HubSpot
Slack
NetSuiteKustomer integration FAQ
How do I add a Kustomer integration to my product?
Enable the Kustomer connector in your fastn dashboard, then let each customer authenticate their own Kustomer account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Kustomer client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Kustomer account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Kustomer 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 Kustomer 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 customer's timeline across channels before drafting a reply.
Who maintains the Kustomer integration?
fastn does. When Kustomer 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 Kustomer 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 Kustomer?
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 Kustomer integration?
A common starting point: let a customer connect their own Kustomer org so support history appears 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 Kustomer integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Kustomer does not change your per-connector cost. You can start free with 3 connected accounts.
Add Kustomer to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.