Loading
Because the evidence is scattered. Support knows about the escalations, delivery knows about the missed dates, finance knows about the slow payment, and the account manager knows about the last phone call.
The review is written from whichever of those is most recent, which is usually the phone call.
The account carries its support history: volume, reopen rate, breaches, satisfaction, all against that account's own baseline rather than a global average.
Beside it sits the renewal date from Flow, delivery performance from Loop and payment behaviour from Books.
It will not predict churn. It assembles what is known; a customer leaving for a reason nobody recorded is invisible.
It also will not produce a health score, because a single number hides which signal moved.
Deterioration is visible while there is time to act — a doubling reopen rate two months before renewal is a different situation from finding out at it.
The discount conversation becomes specific about what actually happened this year, on both sides.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
No — the component signals are shown, with their trends.
Yes, when a signal crosses a threshold you choose.
Yes, which usually changes how an escalation is handled.
Half an hour on your own numbers is usually enough to say whether Desk is the right place to start.