--- title: "Discount Approval Desk Workflow for Sales Teams | Kylon" description: "How a deal desk works open quotes against a discount matrix, logs competitor evidence and books desk reviews in one Kylon room, with every approval made by a person." url: "https://kylon.io/use-cases/discount-approval-desk" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Discount Approval Desk: Every Quote Decided on the Current Matrix, Even After It Changes Use Case9 min read # Discount Approval Desk: Every Quote Decided on the Current Matrix, Even After It Changes Open quotes, competitor evidence, desk reviews, reversals and a mid-quarter matrix change run through one Kylon room. Each quote's effective discount is worked out in the thread, and the desk manager approves every disposition before Pipedrive changes. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Discount requests arrive faster than the desk can read them A deal desk approves discounts against a matrix: how deep a rep can go by segment and contract term, what needs a competitor's quote as evidence, and what goes to the weekly desk review with finance. The quotes sit in Pipedrive. Evidence arrives as a PDF in Gmail or a screenshot in Slack. Desk reviews are calendar invites, and finance exceptions, such as a prepaid multi-year term, come in a separate email. What breaks is the second look. The effective discount, meaning what the customer actually gets once credits and exceptions are counted, changes when the matrix changes at the start of a quarter or when finance clears an exception late. Done by hand, the second look skips quotes that were already approved, and the segment report that goes to sales leadership still counts deals at the old number. ## Who works in the room People - Deal desk manager Owns the discount matrix, approves every disposition and signs the segment close-out - Revenue finance Joins desk reviews, grants exceptions and clears the ones that come in late - Account executives Request discounts, attach competitor evidence and withdraw quotes they no longer need Agents - FinQuote reviewer Works out each quote's effective discount against the matrix, proposes a disposition and writes approved statuses to Pipedrive PipedriveGoogle Drive - AdaEvidence and reviews Logs competitor evidence in Notion against each deal and creates desk review events with finance [Notion](https://kylon.io/integrations/notion)Google Calendar - MycoRep replies Drafts replies on each rep's original thread for a person to send, and gathers evidence posted in Slack [Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) Every discount request comes through one Kylon room. Fin is the default agent, so a rep asking where a quote stands reaches Fin without a mention. Ada owns the evidence log and the desk review calendar, and Myco owns replies to reps. Fin reads and writes Pipedrive through a lasting grant the revenue operations lead approved for this room, and Ada creates review events through the desk manager's own calendar connection, checked on every call. When Fin finds a quote that needs evidence, it mentions Ada in the thread with the deal reference and what the matrix asks for, and Ada leads from there until the evidence is logged. ## From open quote to segment close-out Which matrix is current is written into the room guidelines, and the matrix itself sits in Google Drive next to the desk policy. Each step ends with a person. ```mermaid flowchart TD req([Reps request discounts on
quotes in Pipedrive]) first["Fin works out each effective
discount against the matrix"] approve["Desk manager approves each
disposition before it is written"] evidence["Ada logs competitor evidence
in Notion as Received"] review["Ada creates a new review
event with finance"] holds["Desk manager decides
whether the evidence holds"] decide["Finance and the desk manager
decide in the review"] report["Fin totals approved revenue
per segment from Pipedrive"] matrix([A new matrix or
a reversal arrives]) late([Finance clears an
exception late]) rework["Fin works out the discount again
on every quote a change touches"] changed["Desk manager approves
each changed disposition"] reply["Myco drafts replies on the rep's
thread for a person to send"] close["Fin writes one note per segment
from the final statuses"] signoff["Desk manager signs off the cycle"] req --> first --> approve approve -->|needs evidence| evidence --> holds approve -->|over the line| review --> decide holds & decide --> report report & matrix & late --> rework rework --> changed changed --> reply & close close --> signoff class first,evidence,review,report,rework,reply,close agent class approve,holds,decide,changed,signoff person class req,matrix,late event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | First pass | Every open quote gets an effective discount and a disposition: within the matrix, approved on evidence, desk review or decline | Fin, from Pipedrive | The desk manager approves before any quote status is written | | Evidence | Each competitor quote is logged in Notion against its deal as Received and read into the disposition | Ada | The desk manager approves the entry and decides whether the evidence holds | | Desk reviews | Quotes over the line get a new review event with finance, and existing invites are never edited | Ada, on Google Calendar | Finance and the desk manager decide in the review | | Segment report | Approved annual recurring revenue is totaled per segment from current Pipedrive statuses, and the sales manager's summary is checked against it | Fin | The desk manager confirms before it goes to leadership | | Reversals and new matrix | Reversed approvals and the new matrix are applied to every quote they touch, with the effective discount worked out again | Fin | The desk manager approves each changed disposition | | Late clearance | A finance exception cleared after the review is applied to the quotes it names | Fin, then Myco for the replies | Finance confirms; a person sends each reply | | Close-out | One note per segment, written from the final statuses | Fin | The desk manager signs off the cycle | Stages of one discount desk cycle. Quotes, segments and figures in this example are illustrative. ## When the matrix moves or finance changes its answer A new matrix does not only apply to new quotes. Fin works out the effective discount again for every open and approved quote the new tiers touch, and a quote that was inside the line last week may now need evidence or a desk review. A reversal works the same way. When a sales director withdraws an approval because the competitor quote covered a smaller package, Fin moves the quote back, and the segment totals are rebuilt from Pipedrive, not adjusted by hand. Late clearances are the subtle case. Finance clears a prepay exception two days after the desk review, so part of the discount on two quotes no longer counts against the matrix. Fin proposes both changes in the thread with the before and after. Myco drafts a reply on each rep's original email thread, naming the quote, so the answer sits where the rep asked. Quotes the reps withdrew stay exactly as they were through all of it. ## What the checks catch - A withdrawn quote still sitting in the open list, left exactly as the rep left it - Competitor evidence that arrived by email but was never logged against the deal - A desk review that would be booked by moving an existing meeting instead of creating a new event - An approved quote whose effective discount changes under the new matrix or a late clearance - A segment total that still counts an approval that was reversed ## What stays with people - Approving every disposition before Fin writes a status to Pipedrive - Deciding the quotes that go to desk review, with finance in the meeting - Judging whether a competitor quote is genuine and comparable - Sending each reply to a rep, which Myco prepares as a draft ## Integrations in this workflow Kylon is not a quoting tool or a CPQ system, and it does not replace either. It works across the tools the desk already uses and keeps the coordination between them in one room. - [Gmail](https://kylon.io/integrations/gmail) - Google Calendar - Google Drive - [Notion](https://kylon.io/integrations/notion) - Pipedrive - [Slack](https://kylon.io/integrations/slack) - **Pipedrive** holds the deals and quotes, with the discount, segment and approval fields the desk writes - **Notion** keeps the competitor evidence log, one entry per deal, marked Received when it arrives - **Google Calendar** carries each desk review as a new event with finance - **Gmail** is where reps ask and where the desk answers, from drafts a person sends - **Slack** is where reps drop evidence and quick questions between reviews - **Google Drive** keeps the discount matrix, the desk policy and the segment report ## Where to start Run the first week of next quarter through the room. Connect Pipedrive with a grant for the desk, point Ada at the Notion evidence log, and let the room guidelines carry a single rule: a quote's status changes in Pipedrive only after the desk manager approves it, and withdrawn quotes are never touched. > “A discount is approved when the effective number is right, including what finance changed after the meeting.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our discount approval desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Gmail, Google Calendar, Google Drive, Notion, Pipedrive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the deal desk manager, the revenue finance person and the account executives. Help me invite them to this Room. 3. Build a Discount Desk App with Quote, Segment, Basis and Status columns, one record per open quote. Pull the open quotes from Pipedrive. 4. Work out the effective discount for each quote against the current matrix in Google Drive and propose a disposition. Log competitor evidence from Gmail and Slack into Notion against each deal. Book desk reviews as new calendar events with finance and never move an existing event. Show me every quote that needs evidence, a desk review or a decline. 5. Hold every status write to Pipedrive until the deal desk manager approves the disposition. When finance clears a late exception, apply it to the quotes it names, show the before and after in the thread, and hold each reply draft in Gmail until a person sends it. 6. Write into this Room's guideline that a quote's status changes in Pipedrive only after the deal desk manager approves it, that withdrawn quotes are left exactly as the rep left them, and that desk reviews are always new events. 7. After one clean week, offer to turn the matrix check and re-score of open quotes into an Automation that runs each time the matrix in Google Drive is updated. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Prior Authorization Desk: Deadlines That Follow Each Payer's Current Rules Each prior authorization case gets a disposition and a deadline from its payer's current rule page, and keeps the right one through documentation batches, payer corrections and peer reviews. The desk lead approves every change before Salesforce is updated. Healthcare & life sciencesApprovals & reviewsEmail operations ](https://kylon.io/use-cases/prior-authorization-desk)[ ### Provider Credentialing: Committee Files Backed by Verified Evidence Five checks per provider, evidence split between Box and a verification mailbox, and drafted batches that need auditing before committee. In one Kylon room, agents assemble and audit each file, and the credentialing manager approves every disposition. Healthcare & life sciencesCompliance & riskApprovals & reviews ](https://kylon.io/use-cases/provider-credentialing)