Kustomer logo
§ Agent · Kustomer

The Kustomer data agent that acts the way you would.

It watches your Kustomer data alongside your CRM and billing, on a schedule you set or whenever fresh data lands. When something needs attention, it tells you, or handles it the way you'd want.

D
DefiniteAPP9:14 AM · #cx-ops-alerts
⚠️ SLA breach rate jumped to 18% this week; 34 conversations past first-response target

Breach rate was steady at ~7% over the prior four weeks. The spike is concentrated in the Enterprise tier, mostly conversations tagged billing-dispute routed to a team running at 140% capacity.

Review & approve Dismiss
Kustomer Conversations + SLA Policies + Teams · joined to Stripe subscriptions · audit log

How an agent works

An agent watches one thing and acts on it. Not a workflow, just a standing watch that usually does nothing and acts the moment it should.

◄ repeats on the schedule you set ►

You stay in control

An agent does what you'd do, and only what you've authorized.

The same trusted numbers

It acts on the same governed metrics as your dashboards, and every action is logged and traceable.

You approve anything that writes

It alerts and recommends on its own; anything that changes data is yours to approve.

Try it on a test channel first

Point a new agent at a throwaway channel and watch its judgment before it touches anything real.

No false alarms

It remembers what it already flagged and waits before acting again, so it won't alert you about the same thing twice.

What you can put an agent on

Resolution + RevenueACROSS YOUR SOURCES

Tie support resolution to revenue impact across systems

It joins Kustomer conversations and customer records to your billing and CRM data, so you see which open tickets belong to your highest-value accounts, how resolution time correlates with churn, and where the gaps are before leadership asks.

Conversation (Ticket)CustomerCompany
SLA

Catch SLA breaches before they compound

When your breach rate breaks its trend, it tells you which teams and tags are affected, how far past target the conversations have drifted, and what changed (staffing, volume, routing) so you can fix the root cause, not just the symptom.

SLA PolicyConversation (Ticket)Team
Agent Performance

Surface agent workload imbalances with the numbers

It tracks first-response time, resolution count, and message volume per agent and team, flags when someone is carrying twice the load or when a queue is backing up, and gives you the data to rebalance before service quality drops.

Agent (User)MessageConversation (Ticket)Team
Custom

Run any Python it needs to get the job done

Beyond alerts and write-backs, an agent can run arbitrary Python, so it can do whatever the task actually requires: call an API, kick off a job, reshape the data, or wire into your own tooling. The action space is yours to define.

Why not just build it yourself?

You could rig one of these with a cron job and a Slack webhook in an afternoon. The watching is the easy part. Here's what you'd own forever, and don't, here:

  • The cross-source join: not one tool's data, but it reconciled against the rest of your stack
  • A trusted, consistent metric: the same number your dashboards use
  • The investigation into why, when something fires
  • A full audit trail of everything it did
  • The upkeep, when the schema drifts or the script breaks at 2am

The data it works from

Every Kustomer object, modeled and query-ready the moment you connect.

Customer
customermarketing
Company
customersupport
Conversation (Ticket)
supportengagement
Message
marketingsupport
Note
customersales
Custom Object (KObject)
customersupport
Attachment
supportdevelopment
SLA Policy
marketing
Tag
revenue_financecustomer
Team
marketingsupport
Agent (User)
customersupport
Shortcut (Macro)
supportoperations

It runs on your real Kustomer account (re-opened tickets, SLA policy changes, routing overrides and all), not a tidy demo.

Where it acts

Slack

A message in the channel you choose, with the context and a button to act on it.

Email

A summary in the inbox of the people who need to see it.

Webhook

A payload to your own systems, to wire the agent into whatever you already run.

Warehouse write-back

A flag written back to your warehouse for everything downstream to pick up.

Hand off to Fi

Kick the question to Fi to investigate the why and propose the fix.

MCP

Expose it to your own agents and tools over MCP, and drive it from your stack.

Run it in your own VPC or fully self-hosted. Everything it does is pure SQL and Python you can inspect.

Build your agents with Fi

Fi is your AI analyst. It helps you build and customize everything in Definite, including the agents that watch and act.

Fi

Your AI analyst. Ask questions in plain English, and let it help you build and customize everything in Definite, including your agents.

Meet Fi →

Agents

The watchers and actors. Once you've built one, it runs on its own, keeping an eye on what matters and acting the way you would.

Autonomous agents →

Get started

  1. 1Connect Kustomer, and the sources it needs to reconcile against. Synced and modeled in an afternoon.
  2. 2See the numbers tie out to what you already trust.
  3. 3Put an agent on one thing you can't afford to miss. Fi helps you build it.
§ FAQ

Common questions

You set the schedule, and it also re-checks whenever fresh Kustomer data lands. Each agent watches the one thing you point it at, nothing else.
It alerts and recommends on its own. Anything that writes, whether to a tool, your warehouse, or a customer, is yours to approve. You can also point a new agent at a test channel first and watch its judgment before it touches anything real.
When something fires, it can hand off to Fi to investigate, drilling into the data it has across your connected sources to find what's behind the move, and showing its work.
Data Explorer answers questions about Kustomer when you ask. This watches continuously, reasons across Kustomer plus your billing and CRM, and hands off to Fi to investigate why, so you find the SLA spike before the QBR, not during it.

Your answer engine
is one afternoon away.

Book a 30-minute call and watch us build your first dashboard live, with your own data.