k
Kustomer integration

Kustomer in Polar: support load, read against revenue.

Connect Kustomer over its API and tickets volume flows into Polar, by agent, channel and tag, next to your Shopify orders, returns and refunds. Support stops being a number in a helpdesk and becomes a metric you can read against revenue, as tickets per thousand orders.

/ ⏎
Connect Kustomer See the setup
Google Sheets → Polar

What you can bring in

Tickets volume
"How many tickets, really?"
Tickets created, opened and closed, refreshed on every sync.
created · opened · closed
By agent
"Who's carrying the load?"
Volume by agent, so you see where support effort concentrates.
by agent
By channel & tag
"What are people writing in about?"
Volume by channel and tag, so the drivers are visible.
by channel · tag
Per 1k orders
"Is load rising with growth?"
Tickets volume against Shopify orders as tickets per thousand orders, with the trend.
per 1,000 orders
Against returns
"Is support tied to returns?"
Tickets volume next to returns and refunds, so operational issues show up.
vs returns
In the P&L view
"Where does support sit?"
Support load next to the revenue it should track against, on one view.
support + revenue

Kustomer measures support. Polar measures support against the business.

Your helpdesk reports tickets in isolation, and it cannot see orders, returns or revenue. So you never really know whether support load is healthy for the size of the business. Polar reads Kustomer against the numbers that give it meaning.

Kustomer on its own

  • Tickets live in the helpdesk, revenue lives elsewhere.
  • No sense of whether load is high or low for your order volume.
  • Support and revenue trends never share a chart.
  • Nothing ties support to returns or refunds.

Kustomer with Polar

  • Tickets read against orders as tickets per thousand orders.
  • Load in context: rising, flat or falling relative to growth.
  • Support and revenue on one view, one timeline.
  • Volume sits next to returns and refunds.
Setup Guide

Connect Kustomer.

01 · What you need
Polar

A Polar account with Shopify

A Polar account with Shopify connected. This connector plugs in right next to your stack.

Connect your data →
k

A Kustomer account

API access to your tickets. Your account needs to already hold data before you connect.

Open Kustomer →

Shopify already connected

Support only means something against orders, so Polar reads Kustomer next to Shopify orders, returns and refunds.

02 · Connect Kustomer
1

Connect over the API talk to Polar

Ingest your tickets.
Connect over its API and Polar ingests your tickets volume, created, opened and closed, sliced by agent, channel and tag.
2

Blend with orders automatic

Support meets revenue.
Polar sits tickets volume next to Shopify orders, returns and refunds, so load reads as tickets per thousand orders.
Scope, honestly: this is a support-volume connector focused on tickets, not a full helpdesk mirror. Need more? Ask and Polar can request it.
3

Read it in context the payoff

Load in proportion.
Support load is finally in proportion to the business, trending against growth instead of sitting alone in the helpdesk.
Get started

Turn support load into a business metric.

Ingest Kustomer tickets over its API and read it against orders, returns and refunds.

Book a demo Connect your data ↗
The Gap

The connector is only half of it.

Once your Kustomer tickets are clean and attributed inside Polar, you can use them wherever you already work. Ask Polar in plain language, pull them live through the Polar MCP, or schedule a snapshot into the report your team reads every morning.
k

Kustomer

tickets created, opened, closed
Polar

Polar

support load vs revenue

Ask Polar

Polar MCP

Scheduled reports

Featured Use Case

Support, finally in proportion.

Support, in proportion

A thousand tickets is a crisis for one brand and a quiet week for another, the number only means something against how many orders you shipped. In Kustomer, that context does not exist: you see volume, agents and tags, but not the orders, returns and refunds that make the load meaningful. Polar ingests tickets volume over its API and sits it next to your Shopify orders, so support becomes tickets per thousand orders, a metric you can trend and reason about. When it spikes, you can look at returns and refunds on the same view and tell whether it is an operational issue, not just a busy inbox. It puts support where it belongs: next to the business.

What makes it real

Per 1,000 orders. Volume read against Shopify orders, so load is in proportion, not an absolute number.

Sliced where it matters. Created, opened and closed by agent, channel and tag, next to returns and refunds.

Ask Polar, in plain language. “Show tickets per thousand orders this week and how it tracks with returns.” No SQL, no export.

See how support reads against revenue
Other Use Cases

Other use cases

Use case 01

Placeholder

Placeholder. The use case skill fills this. (rung: see it)

See the use case › Use case 02

Placeholder

Placeholder. The use case skill fills this. (rung: report it)

See the use case › Use case 03

Placeholder

Placeholder. The use case skill fills this. (rung: analyze it)

See the use case › Use case 04

Placeholder

Placeholder. The use case skill fills this. (rung: decide from it)

See the use case › Use case 05

Placeholder

Placeholder. The use case skill fills this. (rung: act on it)

See the use case ›
Your Prompt Library

Kustomer in plain language

A scannable wall of sample prompts for your Kustomer data inside Polar. Ask Polar, or Claude with the Polar MCP connected.
See it
Show tickets created, opened and closed this week.
Break down tickets by agent and channel.
Show tickets volume by tag this month.
Analyze it
Show tickets per 1,000 orders and the week-over-week trend.
Compare support load to returns and refunds.
Which tags drive the most tickets relative to orders?
Decide from it
Is support load healthy for our current order volume?
Where should we invest in self-serve based on drivers?
Summarize how support load changed since last month and why.
Get started · connect once · support in context

Support load, against the business.

Ingest Kustomer tickets over its API and read it against orders, returns and refunds, so support finally has context.

Get started by booking a demo Connect your data in Polar
Phase 1 talk to PolarConnect KustomerGrant access to your tickets data.
Phase 2 automaticVolume inCreated, opened, closed, by agent, channel and tag.
Phase 3 the payoffRead against revenueTickets per thousand orders, next to returns and refunds.