Set 4 deal desk timing rules with your reps: a submission cutoff, coverage hours, a response target, and an escalation point.
Key takeaways
- Write the cutoff with its time zone.
- Publish the days and hours the desk covers.
- Define which hours count toward the response target.
- Name who handles stalled requests and when to escalate.
A rep sends a complex quote late in the afternoon, assumes someone will look at it first thing the next morning, and then wonders why nothing has moved by lunch. Nobody in that story did anything unreasonable. The gap is that no one wrote down when a request counts as received, when the deal desk will look at it, or when it moves up the list.
Timing rules close that gap. They are simple to state and easy to forget, so they belong in a written process your reps can check.
This is written for front-line managers who send non-standard deals and quotes to a deal desk. You do not need a new system to use these rules. A written page and a short conversation with your reps will do.
The examples in this post come from one public source, the Deal Desk Handbook published by GitLab. Its cutoffs, hours, and targets are GitLab's own. Use them as a list of decisions to make, not as numbers to copy into your own process.
The handbook also shows what a non-standard request can look like. Its example is an 18-month deal, with 6 months billed up front and the final 12 months billed at the 6-month mark ( GitLab Deal Desk Handbook). Requests like that are the kind your timing rules should cover, so keep them in mind as you read the 4 rules below.
Rule 1: Set one submission cutoff
Set one time of day after which a request is prioritized for the next business day, and say which time zone it uses.
GitLab's handbook uses 4:00PM as its cutoff. It says that if a complex case or non standard deal request is submitted after 4:00PM (Local Time), the case will be prioritized the following business day ( GitLab Deal Desk Handbook). Treat this as a prioritization rule, rather than a promise that earlier requests receive a same-day response.
A cutoff gives a rep something to plan around. Without one, a rep who sends a request late in the day has no way to know whether it counts as today's work or tomorrow's, so the rep will guess. With a published cutoff, the question becomes a matter of checking a timestamp instead of a judgment call.
Your version of this rule needs a definition your reps can apply to their own deals. Write down two or three examples of what your desk calls complex, two or three of what it calls non-standard, and a couple that do not count. That list gives reps something to check their deals against, so the cutoff is not argued case by case.
The GitLab rule is written in local time, and you should decide whether yours is too. If your reps work in more than one time zone, a single clock time with no zone attached leaves room for a rep in one region to assume a different cutoff from a rep in another. Name the zone every time you state the cutoff. Here is how the confusion happens: suppose your cutoff uses one time zone, but a rep checks it against a clock in another zone. Without the zone written down, the rep and the desk can read the same timestamp two different ways.
Before you announce it, pull a few recent non-standard requests and check which side of the line each one landed on. If the result surprises you, change the time before reps start planning around it.
When you explain the cutoff, lead with what reps control. A rep cannot move the clock, but can send requests early in the day, put the full terms in one message, and avoid sending a late revision that changes what the desk is reviewing. Those habits do not depend on the exact time you choose, and they make any cutoff easier to follow in practice.
Rule 2: Publish coverage hours and do not assume round-the-clock review
Publish the hours your deal desk covers, and tell reps not to assume anyone reviews requests outside them.
GitLab's handbook is direct about this: "Our regional teams do not operate on a 24/7 support model" ( GitLab Deal Desk Handbook). That sentence is about GitLab's regional teams. For your own process, it is a reason to confirm your coverage hours rather than assume them.
The same handbook gives a second time: "If your request is submitted after 4:30PM local time, or outside of standard support hours, it may not be reviewed until the following business day" ( GitLab Deal Desk Handbook). The word to notice is "may." The quote describes a possibility for requests sent late in the day or outside standard support hours.
The two times do different jobs. The 4:00PM line in Rule 1 is about prioritization. The 4:30PM line is about whether a review can happen before the next business day. A rep who reads both may reasonably ask which one applies to their own request. Pick one time for your team, use it everywhere, and state your coverage hours on the same page as the cutoff.
Coverage hours should include days as well as times. Write down which days the desk works, and say what happens to a request sent on a day it does not. Do the same for holidays, if your company observes them. A rep who finds a clear answer for a Saturday or a holiday does not have to guess when a customer deadline is close.
Coverage also shapes how a rep plans a customer date. If a customer needs an answer by a certain morning, the rep needs to know which send time leaves the desk enough time to review first. Put that answer next to the hours, not in a separate document, so the rep can work out the timing from one page.
Rule 3: Set a response target measured in business hours
Set a response target measured in business hours, and describe it as something the team works toward.
GitLab's handbook says: "The Deal Desk team will do their best to respond to each request to SFDC Case within 6 business hours" ( GitLab Deal Desk Handbook). Use this effort-based framing unless your team is ready to commit to a firmer number. A target written as a promise leaves less room to explain a miss, so choose wording your team can keep.
The target is measured in business hours, and that term needs a definition for your team. Decide which days count, which hours count, and whether a request that arrives outside them starts the clock at the next opening. Write that definition next to the target, so reps and managers count the same way.
Illustrative example: Count only covered hours
Starting the clock at arrival or at the next opening produces the same deadline if no hours accrue while the desk is closed. Decide which days count before calculating the deadline.
Check the target against real requests before you hold anyone to it. Count the business hours on a sample of recent requests and see how many would have met the target. A target you have not tested may be easier or harder to meet than you expect, and either result is worth knowing before reps start to rely on it.
A target also helps reps plan customer dates. Reps can count back from the customer's date using your agreed target and coverage hours. Share the target with a worked example that uses one of your own deals, so the rep can see the count rather than take it on trust.
Look at each miss separately: possible causes include an unrealistic target, an incomplete request, a missed escalation, staffing gaps, or unexpected complexity; investigate other causes too.
Rule 4: Set an escalation point for requests that stall
Set a point at which a request that has not moved is escalated, and name who takes the escalation.
GitLab's handbook says: "If a task is not resolved within 24 hours it will be escalated (if necessary)" ( GitLab Deal Desk Handbook). Two details in that sentence matter. The first is the 24-hour figure, which belongs to GitLab's process. The second is the phrase "if necessary," which makes escalation depend on a judgment. Decide who makes that judgment for your team.
Define when your escalation clock starts: from submission, from the first reply, or from the last time someone asked the rep for something. Whatever you choose, write it down next to the escalation point.
The response target and the escalation point do different work. The first sets an expectation for a response to a request. The second applies to a task that is still not resolved. Keep them separate in your write-up so that a rep does not read one as the other.
Give reps a simple way to ask for escalation. A short message that names the deal, the blocker, and the date the deal needs an answer gives whoever takes the escalation something to act on. Without those details, the escalation starts with a round of questions, and the deal waits while they are answered.
Frame escalation as a normal step in the process, not as a sign that a rep has failed. That framing is your choice, so make it on purpose and say it out loud to your reps.
Put the 4 rules in writing
Write the 4 rules down with your own numbers, and walk your reps through them before the next non-standard deal comes in.
Each rule needs these parts written out:
- Cutoff: the time, the time zone, and the kinds of requests it covers.
- Coverage: the days and hours the desk reviews requests, and what happens to requests sent outside them.
- Response target: the number of business hours, and your definition of a business hour.
- Escalation: the point at which a stalled request moves up, who takes it, and what the rep sends.
Keep the list on one page, so reps can find any of the 4 without searching a longer process document.
Name one owner for each rule
Name one owner for each rule, so every question about it has a clear place to go.
The owner does not need to make every decision. The owner keeps the written rule current, answers questions about it, and brings proposed changes to the team. On a small team, one person may own all 4 rules. On a larger one, you might split them between a front-line manager and a deal desk lead. Either way, the owner should check the written rule against what the desk is actually doing, and say so when they differ.
Give reps a checklist for complete requests
Give reps a checklist for what a complete non-standard request contains, so the desk has the details it needs at the first review.
A checklist helps in two ways. It helps the rep notice missing details before sending, and it gives the desk a consistent starting point. Consider including the customer and the deal stage, the term and the billing schedule, the reason the terms are non-standard, the date the customer needs an answer, and any approvals the rep already has.
Use the deal field checks when reviewing request details, and check quote expiration rules alongside the customer's deadline.
Agree on exceptions before they come up
Agree on how exceptions are handled before they come up, rather than deciding each one as it arrives.
Some requests will land just after a cutoff, or arrive on a day the desk does not cover. Reps will ask for a favor in those cases, and the answer you give to the first one is what reps will expect next time. Decide in advance who can approve an exception, what the rep must show to ask for one, and whether an exception changes the due time or only the order of the queue.
Keep the list of exceptions short. Every exception a process allows is something a rep has to know to use it correctly. A few clear exceptions are easier to follow than a long list of special cases.
When a rep disagrees with a rule, hear the disagreement out, then check it against the data. If a rule is causing real problems, change it on purpose and tell the team what changed and why. Do not let it drift by making one-off exceptions that nobody writes down.
Review the rules after one month
Review the 4 rules with your reps after one month of real requests, and change only what the data shows needs changing.
One month of real requests gives you something to check the rules against. Pull the requests that came in near the cutoff, the ones sent outside coverage hours, the ones that missed the response target, and the ones that were escalated. Look for where each rule helped and where it got in the way.
Change one rule at a time, and tell reps what changed and why. If you change all 4 at once, it becomes hard to tell which change made a difference. Write the date of the review on the rule page, so the next person to read it knows when it was last checked.
The goal of all 4 rules is simple: reps and managers should read the same deadline the same way.
Today, take one recent non-standard request and walk its timestamps through your written rules with a rep; clarify any deadline you calculate differently.
Questions about deal desk timing
Does a response target promise resolution?
A response target sets an expectation for a reply, while the escalation point addresses a task that remains unresolved.
Should every late request be an exception?
Use your agreed exception process rather than changing the rule for each late request.