---
title: Markin + Zendesk
url: https://markin.ai/integrations/zendesk
category: Support and contact centre
description: Connect Markin to Zendesk: surface the next best action inside the agent view and read ticket signal as an early churn indicator.
---

# Markin + Zendesk

> Next best action on the agent's screen, with its reason.

**Job:** Prioritise the support queue by revenue at risk.

A Markin and Zendesk setup reads tickets, reasons and satisfaction as early churn signal, and writes back the expected value of each customer so the queue can be prioritised by revenue at risk rather than by ticket age alone.

A service contact is the highest-attention moment a customer gives you all year. Deciding what to do with it deserves the same rigour as a campaign, and it is measurable per agent.

## What can you ask Markin to do in Zendesk?

- How do I prioritise support tickets by customer value?
- Can support tickets predict churn?
- How do I give agents a next best action during a cancellation call?
- How do I measure the revenue impact of support?

## What Markin does in Zendesk

- Read tickets, reasons, tags and resolution times.
- Read satisfaction scores and reopen rates.
- Detect ticket patterns that precede cancellation.
- Score revenue at risk per open ticket.
- Write the score and the suggested action onto the ticket.
- Serve an agent-facing next best action with its reason.
- Keep a randomised holdout so the save offer can be measured.
- Report retained revenue attributable to support actions.

## The growth work behind Zendesk

### Read the estate

- Reconcile the same customer across billing, CRM, product and support identities.
- Read consent, subscription and channel eligibility state before anything else.

### Find where revenue is leaking

- Detect involuntary churn from failed payments, card expiry and retry behaviour.
- Spot onboarding steps where activation falls off and revenue never starts.

### Explain why

- Separate mix effects from real behaviour change.
- Rank drivers by how much of the movement each one accounts for.

### Write hypotheses worth funding

- Attach the evidence and the assumption each one depends on.
- Rank the portfolio by expected value, not by seniority.

### Decide per customer

- Suppress an action rather than send a weak one, and log why.
- Choose the next best action for each customer, for each moment.

### Execute in the tools you already run

- Roll a decision batch back cleanly when something looks wrong.
- Leave the estate exactly as it was if Markin stops writing.

### Prove it caused the revenue

- Refuse to call a result that has not cleared the evidence standard.
- Publish the readout in the same place for every experiment.

### Retire, govern and hand over

- Retire programmes automatically when they stop beating control.
- Re-test assumptions that decay, such as price sensitivity and seasonality.

Full catalogue: [Everything a growth team does, running every day.](https://markin.ai/growth-work)

## Activation patterns

- **Decision API.** The surface asks Markin for a decision at render time and receives one action plus its reason, with a defined fallback.
- **Read only.** Markin reads signal from this system. Nothing is written back and no schema is changed.

## What Markin reads from Zendesk

- Ticket volume, reason codes and CSAT
- Contact history per customer

## What Markin writes back

- One suggested action per contact, shown in the agent view with its reason

## Used together with

- [stripe](https://markin.ai/integrations/stripe)
- [braze](https://markin.ai/integrations/braze)
- [snowflake](https://markin.ai/integrations/snowflake)
- [recurly](https://markin.ai/integrations/recurly)
- [intercom](https://markin.ai/integrations/intercom)
- [salesforce-service-cloud](https://markin.ai/integrations/salesforce-service-cloud)

## Related

- [Solution: churn-prevention](https://markin.ai/solutions/churn-prevention)

## FAQ

**How does Markin connect to Zendesk?**

Decision API, Read only. The surface asks Markin for a decision at render time and receives one action plus its reason, with a defined fallback.

**What does Markin read from Zendesk?**

Ticket volume, reason codes and CSAT; Contact history per customer.

**What does Markin write back into Zendesk?**

One suggested action per contact, shown in the agent view with its reason

**Do we have to move our data to Markin?**

No. Markin reads from your warehouse, product events and operational systems in place, on your compute, under the access rules your data team already set. Nothing is copied into a separate customer base and there is no vendor-side profile store to migrate off later.

**Does Markin replace our engagement platform or CDP?**

No, and it should not. Your engagement platform keeps the channel, the templates, the deliverability and the governance. Your CDP keeps identity and consent. Markin adds the layer neither has: deciding which action deserves to exist for each customer, and proving it against a holdout.

**What if the system we use is not listed?**

The four activation patterns cover almost everything: attribute write-back, triggered event, decision API and direct surface rendering. Any system that exposes an API, accepts a table, or can read a warehouse column can receive decisions. New connectors are built during deployment, typically in days.

Source: https://markin.ai/integrations/zendesk