Handle a reseller discount request through the approval path

A reseller discount request often arrives close to a customer meeting. The request deserves a fast, orderly response, yet urgency does not turn a channel manager into a pricing approver. Your job is to move verified facts toward the person who owns a decision and give the reseller useful language for the customer. Start by separating the meeting deadline from the requested commercial outcome. One has a fixed time. The other needs review.

Ask for the customer name, the opportunity record, meeting time, requested services, requested term, and the reason for the request. A message saying, “We need ten percent today,” leaves too much unknown. Reply with a short question set: “Which customer record covers this request? What services and term are under discussion? When does your customer meeting begin? What information supports the comparison?” Those questions turn pressure into a workable intake.

Check registration before discussing any exception. Registration gives internal reviewers a shared place for partner involvement, contact details, stage, and scope. Do not use missing fields as a reason to lecture a reseller. Name the needed facts and an owner. Say, “The record has the customer name. Please add both service locations and the presentation time by 4:00 p.m. Mia owns customer contacts, so ask her for the missing location address.” A named task keeps momentum.

Price without comparable scope tells reviewers little. Ask what each proposal includes, which sites appear, and whether equipment, setup, support, or migration work sit outside a monthly figure. If channel process permits a customer facing quote, request a copy. When only a verbal report exists, label the source. “Reseller reports a lower monthly figure for two sites” differs from “The competing proposal includes two comparable sites.” The first sentence records a report. The second makes a claim without support.

Use a clear request note once facts arrive. Include the reseller, customer, opportunity stage, customer meeting time, requested services, known comparison details, missing information, and requested decision. Avoid a note containing only “urgent.” A reviewer needs to see why a response matters and what remains unresolved. Write, “Please review whether an exception request is ready for consideration before 8:30 a.m. tomorrow. The reseller needs either approved terms or a stated pending status for a 9:00 a.m. customer discussion.”

Here is a fictional practice situation. Elise calls Rafael at 3:15 p.m. and says, “My customer meets us tomorrow morning. Another provider gave them a lower number. Please approve a discount now.” Rafael replies, “I hear your deadline. Pricing owns any exception decision. Let’s complete the request. Is this opportunity registered, and what appears in each proposal?” Elise reports two locations, a monthly service amount, and no detail about setup charges.

Rafael does not fill in missing details. He says, “Add both locations to the opportunity record and send your scope notes by 4:00 p.m. I will route the request at 4:15 p.m. Our sales engineer will prepare a comparison using confirmed material for your meeting.” His promise covers work under his control. His words do not suggest a likely price result. Elise knows what she needs to do before Rafael sends anything onward.

Keep technical comparison separate from commercial approval. A sales engineer might explain differences between supplied documents, yet an engineer does not set an exception price. Ask the engineer to mark every element as confirmed, absent from supplied material, or awaiting customer clarification. This protects the reseller from overstating an offer during a tense customer conversation. The comparison also gives pricing a cleaner record.

Give every next step a time and a sender. “I will look into this” offers no useful commitment. “I will send your completed request to pricing by 4:15 p.m. and call you with review status by 5:30 p.m.” gives Elise a usable schedule. When reviewer availability sits outside your control, say so plainly. “Pricing owns the decision. I asked for a response before 8:30 a.m. I will update you at 5:30 p.m. even if review continues.”

Some resellers will press for a verbal number. Meet pressure with direct language rather than argument. “I do not give unapproved prices. I will help you present confirmed scope and share review status before your meeting.” Do not add conditions from memory. Do not imply a probable outcome. A temporary deadline should not create a commercial commitment nobody approved.

Prepare language for several valid paths without turning every conversation into a formula. An approved exception calls for the approved terms and any stated limits. A request needing more facts calls for a list of missing facts and named owners. A declined request still needs a useful next move, such as presenting standard approved pricing, revising scope, or returning with a supported comparison. The reseller needs a sentence suitable for the customer, not spin.

At 5:20 p.m., Rafael has no pricing decision. In this fictional situation, he calls Elise. “Pricing received your request and needs confirmation about setup scope. No exception has been approved. For tomorrow, present our approved offer. Use this comparison note to ask whether setup sits inside the other proposal. Send me their answer after your meeting, and I will add the answer to the request.” Elise leaves with a precise customer question instead of an unsupported number.

After the meeting, record new facts with their source and time. “Customer said setup appears in a separate document” preserves attribution. “Competitor includes setup” treats an unverified statement as settled fact. Watch for scope changes as well. A request might begin with service for two sites and later add equipment, a third site, or a longer term. When scope changes, say, “This request now includes another location. I will ask pricing whether a fresh review is needed.”

Practice with a fictional deadline of 24 hours. Ask a colleague to play Elise and provide only a requested discount, a rival figure, and a meeting time. You play Rafael. Gather registration status, scope details, evidence source, and requested decision. State an owned action with a time. Then write a request note containing one missing fact. Finish by sending Elise a message at 5:30 p.m. which names setup scope as open and asks her to bring the customer answer back after tomorrow’s meeting.