Three approvals, in parallel, not in your inbox.
Non-standard pricing and terms routed to Finance, Sales Management and Legal at the same time, with every approval tracked instead of buried in email.
A rep needs Net 90 and a 20% discount to close.
Today that becomes an email to three people, a thread nobody can find later, and a deal that stalls while everyone waits for someone else to reply first.
How it works
submitted in chat, decided in chatThe rep submits it
What they need and why, from the channel they are already working in.
Thresholds pick the approvers
A small discount may need one approver; stacking payment terms and liability may need three.
Each approver gets their own leg
In parallel, in their own channel. Nobody waits on anybody else to start.
The first rejection cancels the rest
No point asking Finance to approve something Legal has already refused.
Everyone can see where it is
Which legs are approved, which are outstanding, and who is holding it, all visible to the rep without asking. That single fact removes most of the follow-up that makes exception approval feel slow even when it is not.
Escalation is capped at two rounds per leg, so a request cannot ping-pong indefinitely.
It is a separate flow, on purpose
A deal exception is not a contract. It is kept apart from the contract register rather than pretended into it.
No document
Nothing to extract terms from; the request itself is the artefact.
No redlines
There is no counterparty draft in play, so nothing to mark up.
Its own lineage
Parallel legs, escalation caps and approvals that belong to the request, not to a file.
Deal exceptions are chat-only, deliberately. They run in Slack and Microsoft Teams; there is no web review surface for them.
Common questions
In Slack or Microsoft Teams. Deal exceptions are deliberately chat-only; there is no web review surface for them.
No. Finance, Sales Management and Legal review in parallel, each on their own leg, so nobody waits on anybody else. The first rejection cancels the remaining legs.