---
title: Customer action arbitration: choosing one action per customer
url: https://markin.ai/guides/customer-action-arbitration
author: Romà Llambés, Co-founder, Markin
published: 2026-08-07
updated: 2026-08-07
keywords: customer action arbitration, next best action arbitration, contact policy, action prioritisation
---

# Customer action arbitration: choosing one action per customer

> Customer action arbitration is the step that decides which single action a customer receives when several are eligible at once. It compares candidate actions on expected value, applies eligibility and contact policy, resolves conflicts between teams and campaigns, and is allowed to choose no action at all when nothing clears the bar.

**Customer action arbitration**, The process of selecting one action per customer from all eligible candidates, using expected value, eligibility rules, contact policy and conflict resolution, including the option of sending nothing.

## Every team is optimising the same inbox

Retention has a win-back offer. Growth has an upsell. Product has an onboarding nudge. Finance has a dunning sequence. Each is defensible on its own, and each was prioritised inside its own tool. Without arbitration the customer gets whichever one happened to run first, and the business never learns which of the four was worth sending.

- Contact frequency is capped per channel, not per customer, so pressure accumulates invisibly.
- Conflicts are resolved by campaign start date rather than by value.
- The cost of the action that was not sent is never measured.

## How an arbitration decision is made

Arbitration is not a priority number in a spreadsheet. It is an ordered set of filters applied per customer, at decision time.

1. **Assemble candidates.** Every action the customer is technically eligible for, from every programme, is placed in one pool. An action that never enters the pool can never be compared.
2. **Apply eligibility.** Consent, channel availability, regulatory constraints, exclusion lists and product state remove candidates outright. These are hard filters, never trade-offs.
3. **Score expected value.** Each surviving candidate carries an expected incremental value on this customer, net of margin, discount depth and contact cost.
4. **Apply contact policy.** Per-customer frequency, channel fatigue and quiet periods are enforced across all programmes at once, rather than inside each tool separately.
5. **Resolve conflicts.** Two actions that cannot coexist, a retention discount and a price increase on the same week, are resolved by value and by the constraints the business set in advance.
6. **Choose, or choose nothing.** If no candidate clears the value threshold, the correct decision is no contact. Preserving attention is a real outcome and is measured as one.
7. **Hold out.** A share of eligible customers receives nothing by design, so the value of the arbitration itself can be read rather than assumed.

_Prioritisation versus arbitration_

|  | Campaign prioritisation | Customer action arbitration |
| --- | --- | --- |
| Unit of decision | The campaign. One audience, one treatment. | The customer. One decision per person, per moment. |
| Conflict handling | Resolved by schedule and by whoever owns the calendar. | Resolved by expected value under stated constraints. |
| Contact pressure | Capped per channel, per programme. | Capped per customer, across every programme at once. |
| Doing nothing | Rarely modelled. Silence is a gap in the calendar. | A first-class option with a measurable value. |
| Learning | Which campaign performed. | Which action was worth choosing for whom, against a holdout. |

## Test whether you have arbitration or just prioritisation

Pick one customer who received a message last week and answer these.

- Can you list every action that customer was eligible for that day?
- Can you state why the one they received beat the others?
- Is contact pressure capped per customer, or per channel?
- Who resolves a conflict between two teams today, and how long does it take?
- Is 'send nothing' a possible output of your current setup?
- Is there a population that received nothing by design, so you can measure the arbitration itself?

## When arbitration is not the bottleneck

- Businesses running a small number of programmes that rarely overlap. The conflicts are visible and a human resolves them well enough.
- Bases too small for per-customer decisions to reach statistical power.
- Environments where regulation fixes the sequence of communications, leaving nothing meaningful to arbitrate.
- Organisations without shared eligibility data, where the candidate pool cannot be assembled in the first place. Fix the data layer first.

## FAQ

**What is customer action arbitration?**

It is the step that decides which single action a customer receives when several are eligible at once. Candidates from every programme are pooled, filtered by eligibility and consent, scored on expected incremental value, checked against per-customer contact policy, and resolved against each other. Sending nothing is a valid outcome.

**How is arbitration different from campaign prioritisation?**

Prioritisation ranks campaigns before they run and resolves clashes by schedule. Arbitration ranks candidate actions per customer at decision time and resolves clashes by expected value under stated constraints. One optimises the calendar; the other optimises the customer.

**Why does 'no action' need to be an option?**

Because contact has a cost that rarely appears in a campaign report: fatigue, unsubscribes and reduced response to the message that actually mattered. If a system cannot choose silence, it will always find a reason to send something, and that reason is never measured against the alternative.

## Related

- [Customer decisioning, explained](https://markin.ai/guides/customer-decisioning), The category this step sits inside.
- [Controlled growth experiments](https://markin.ai/guides/controlled-growth-experiments), How the arbitration itself is measured.
- [Decision layer reference architecture](https://markin.ai/architecture/decision-layer-reference-architecture), Where arbitration sits between context and activation.
- [Activation and integrations](https://markin.ai/architecture/activation-and-integrations), How the chosen action reaches your stack.

Source: https://markin.ai/guides/customer-action-arbitration