Skip to content
Lines open
Map my coverage

Sales Call Handling

Writing a price quote call script without approving discounts

A phone script that gives callers useful pricing information while keeping discount approval with the sales owner.

Two colleagues reviewing printed price sheets at a shared office table
Table of contents

Separate published prices from negotiated prices

A published price is the number the business is willing to stand behind for any qualified caller. A negotiated price depends on volume, timing, or a long-term agreement. The script should make that difference clear without sounding evasive. Start by naming the published price and the conditions that come with it.

When a caller asks for a better number, the handler should not invent a range. Offer to collect the details that the sales owner needs for a real quote. That keeps the conversation useful without giving away authority. The caller leaves with a clear next step instead of a number that may be reversed.

Give the caller a complete starting quote

A good starting quote includes the unit price, the minimum order, any setup fee, and the delivery or service window. Missing one of those items turns a simple call into a second call. Read the full quote back and confirm that the caller understood each part. Ask whether any detail needs clarification before moving on.

Do not shorten the quote to make it sound cheaper. A low number that excludes setup or delivery damages trust when the invoice arrives. If the caller compares the price with a competitor, acknowledge the comparison and ask what the competitor included. The answer often reveals which part of the offer matters most.

Collect the facts a discount decision needs

A sales owner cannot approve a discount without knowing the volume, the timeline, and the payment terms. Build those questions into the script in a fixed order. Ask for the expected quantity, the start date, and whether the caller has bought before. Record the answers in the quote record, not only in a call note.

The handler should also ask what the caller will do if the price does not change. That question separates a serious buyer from a price shopper. If the caller plans to buy elsewhere, say so in the record and stop pushing. A clean loss is better than a discount that sets a bad precedent.

Use approved language for the discount boundary

Write one sentence that explains who can approve a discount and how long it takes. The handler should say it the same way every time so callers hear a policy, not a personal refusal. A sentence such as "I can send this to our sales lead, who reviews volume pricing each morning" is specific and honest. Avoid phrases like "I will see what I can do" because they create false hope.

The script should also give the handler a polite way to end the price negotiation. Offer a scheduled callback with the sales owner instead of an open-ended promise. Tell the caller what information will make the callback productive. The boundary stays firm while the caller still feels heard.

Prepare for the common price objections

Callers usually object on price, timing, or trust. Write a short response for each objection that does not attack a competitor. For price, restate the value included in the quote and ask which part is over budget. For timing, offer the earliest available start and explain what drives it.

For trust, point to a specific process such as a written quote, a sample, or a reference policy. Do not invent a customer testimonial or a discount that does not exist. The handler can read from approved material only. Review the objection responses each month and update them with what actually works.

Keep approval with one named owner

Name the person who can approve a discount and one backup for that person. Put both names in the script and in the quote tool. The handler should route every exception to that owner with the collected facts. A single owner prevents callers from shopping for a yes.

Track how many discount requests arrive and how many are approved. A high request rate may mean the published price is unclear or the quote is incomplete. A high approval rate may mean the boundary is too soft. Review the pattern with the sales owner instead of changing the script alone.

Record the quote in one place

Every quote should have one record that holds the price, the conditions, the caller details, and the approval status. The record should be easy to find by phone number or company name. If the caller rings back, any handler can continue the conversation without starting over. Duplicate records are a common source of conflicting prices.

Set an expiry date on each quote and tell the caller when it ends. An open-ended quote becomes a promise the business may not want to honor later. The handler should note the expiry in the callback and in the record. A clear expiry also gives the caller a reason to decide.

Train with recorded calls and a scorecard

Use a small set of recorded calls to practice the script before a handler takes live pricing questions. Pick examples with a straightforward quote, a discount request, and an objection. Score whether the handler gave the full quote, collected the facts, and stayed inside the boundary. Give feedback on one behavior at a time.

The scorecard should reward accuracy and a clear next step, not a lower price. If handlers are measured on conversion alone, they will improvise discounts to close the call. Keep pricing authority and quality review in the same owner's hands. That alignment makes the script credible.

Review the script when the price list changes

A price change can make every saved quote and every script line wrong overnight. Set a rule that the script owner updates the document before the new price list goes live. Tell handlers where to find the current version and how to report an outdated number. Remove old versions from shared drives.

Run a short check after each change by calling the main line as a customer. Confirm that the published price, the fees, and the discount boundary are all correct. Ask a handler to read the quote back from the live script. A ten-minute check prevents weeks of inconsistent answers.

Map the first queue

GIVE MISSED CALLS A WAY BACK IN.

Share your call types, hours, tools, and escalation rules. We will turn them into a practical coverage plan with a clear first week.

Book a free consultation ↗See the call lanes