How to Talk About a Rebate Before the Money Is Certain

Why this matters

The angry rebate call almost never comes at the proposal. It comes eleven weeks after the install, from a customer who has heard nothing since the truck pulled out, and who has spent those eleven weeks quietly converting your sentence "it looks like this should qualify" into "they told me I would get it." Nobody lied. The hedge simply did not survive the silence. Choosing careful words at the sale is a solved problem and a sibling card covers it. What is not solved in most shops is the two to five months between the sale and the money, which is where the expectation actually forms, hardens, and turns into a complaint. This is a communication schedule, not a script.

The expectation hardens in the silence, not in the sentence

A customer retells your sentence to themselves, then to a spouse, then to a neighbor. Hedges are the first thing to fall out of a retelling because they carry no information the listener wants. "Should qualify, the utility decides" becomes "qualifies" by the second retelling and "they are getting money back" by the third. You cannot stop that with better wording at the proposal. You stop it by putting a message in front of the customer often enough that the current, accurate version of the story is always the most recent one they heard.

So plan five touchpoints, one at each moment where the customer's belief can move: the proposal, the signature, the day you submit, the wait, and the outcome. Skipping any one of them costs you something specific, named below in each step.

Touchpoint 1: the proposal carries the program, not a number

At the proposal, put four things in front of the customer in writing: the name of the program, who administers it (a utility, a manufacturer, a state energy office, the tax code), who files the application, and what your shop's role is. Your role is almost always documentation and nothing else. Say so.

What does not belong on the proposal is a figure in your own handwriting on your own letterhead. Print or link the administrator's own posted terms and staple them to the back, with the date you pulled them. If you put an incentive amount into an advertisement, a quote, or any written claim about what a customer will receive, that is a representation you have to be able to back up under the FTC Act's prohibition on deceptive acts and practices (15 U.S.C. 45), and the administrator's posted terms with a date on them is backing, while your recollection of last spring's payout is not.

What you lose by skipping it: the customer's only record of the program is your voice, so any later dispute is your word against theirs with nothing on paper in between.

Touchpoint 2: the signature has to make the contract independent of the claim

The contract price is due on your terms whether the incentive pays out, pays short, or never pays at all. That sentence belongs in the agreement, in plain language, not buried in fine print, and you should read it aloud before the customer signs. It is not an unfriendly clause. It is the clause that lets you keep helping with the claim later without the help turning into liability.

In the same block, commit to your side of the bargain with a number: your shop submits the complete documentation package within 5 business days of commissioning. That is an operational default worth adopting as written and tuning to whichever program you file with most often. It matters because it is the only part of the timeline you control, and because a customer who knows your commitment can measure you against it instead of against the administrator's schedule.

What you lose by skipping it: the customer treats final payment as contingent on the rebate, and you end up financing a third party's processing queue out of your own receivables.

Touchpoint 3: submission day resets the customer's clock

The same day you submit, send one short message: what was submitted, the confirmation or reference number the administrator issued, the date, and the administrator's own phone number or portal address. Three of those four items are for the customer's benefit; the reference number is for yours, because it lets the customer chase their own claim without routing every question through your office.

The clock reset is the real payoff. Customers start counting from install day because that is the event they remember. Submission is later, sometimes much later if a permit sign-off or a commissioning report was in the way. Handing them the submission date, in writing, moves the start of the count to the correct event and quietly removes the days that were never part of the processing window in the first place.

What you lose by skipping it: every claim feels longer to the customer than it actually is, by exactly the gap between install and submission.

Touchpoint 4: check in on a fixed cadence, especially when there is no news

Message the customer every 3 weeks from the submission date until the claim pays or is denied. Send it when nothing has happened. A no-news message is the entire point: an unanswered stretch is read as a lost claim, and a customer who believes the claim is lost calls your office in a bad mood instead of waiting.

Keep the message to four lines: current status, days elapsed since submission, the next event you expect, and what you will do if nothing has moved by the next check-in. That last line is what separates a status update from an excuse. "If there is still nothing at week 9, I will call the program administrator directly and give you what they tell me" is a commitment the customer can hold you to, and holding you to it is far better than losing faith in you.

What you lose by skipping it: the customer initiates contact instead of you, which converts a routine wait into a complaint before you have said a word.

Touchpoint 5: you make the outcome call, both ways

On approval, close the loop in writing and name the payment mechanism, because the mechanism surprises people. Some programs mail a check, some post a credit to the utility bill over one or more cycles, some load a prepaid card with an expiration on it. A bill credit spread across billing cycles is not what a customer picturing an envelope expects, and finding that out from you is a shrug while finding it out from the utility is a grievance.

On denial, you call the same day you learn it, and you lead with what you are doing rather than with the reason. "Your claim came back denied, here is the reason they gave, here is what I think is fixable, here is what I am filing by Friday" keeps you in the role of the person handling it. Leading with the reason casts you as the person delivering bad news and then standing there. Where the denial is genuinely final, say that plainly in the same call rather than leaving a thread of hope you cannot deliver on.

What you lose by skipping it: the customer learns the outcome from the administrator's form letter, which explains nothing and names you nowhere.

Worked example: one shop's log, and the claim that went long

A shop pulled its own claim log for the last 40 submissions to one utility program. Of those 40, 34 paid as submitted, 4 came back with a documentation defect and paid after correction, and 2 were denied permanently on eligibility. That is 85 percent paid as submitted (34 of 40), 95 percent paid eventually (38 of 40), and 5 percent permanently denied (2 of 40). Median time from submission to payment was 9 weeks; the longest single claim in the log took 21 weeks. Those are this shop's figures from this shop's log, on one program, in one season. Yours will differ, which is exactly why you keep the log.

Now a specific job. The install was commissioned, and the package went in 4 business days later, inside the shop's own 5-business-day commitment. The submission-day message went out with the reference number. Check-ins landed at weeks 3, 6 and 9 after submission, so the customer received three no-news messages before the median payout point arrived with nothing in hand.

Week 9 is where this claim earned its keep. Against a median of 9 weeks, being unpaid at week 9 means nothing at all: half of all claims in the log paid later than that, and the log's own tail runs to 21 weeks. The check-in at week 9 said exactly that, in one line, and included the promised escalation call to the administrator. The administrator's answer was a queue backlog with no defect on the file. The claim paid in week 14. The customer never called the office once, because at every point where they might have wondered, the most recent thing they had heard was from the shop.

Compare that to the same claim run silent. The customer counts from install day, not submission day, so at true week 14 from submission they believe they are at roughly week 15 from install. They have heard nothing. They know from a neighbor that rebates "usually take about two months." Their conclusion is not "the queue is slow," it is "my contractor never filed it," and the call that produces is not a status question.

When the customer brings their own number

Sooner or later a customer arrives with a figure from a search result, a manufacturer flyer, a neighbor, or a competitor's quote. Do not argue with the number and do not adopt it. Ask for the source, then read it with them and look for three things: the effective date on the document, the eligibility gate at the top, and whether the figure is a maximum or a typical payout. Most stale numbers fail on the first check, most inapplicable ones fail on the second, and most inflated ones are program maximums that require conditions the job does not meet.

Then hand the conversation back to the administrator's current posted terms. "That flyer is from last season and the program reset in the spring, here is what their page says today" is a factual correction with a source behind it, and it costs a competitor's inflated quote its credibility without you saying a word about the competitor.

References

• Federal Trade Commission, prohibition on deceptive acts and practices, 15 U.S.C. 45, and FTC guidance on substantiation of advertising claims
• ENERGY STAR (U.S. EPA) rebate finder and program locator, for identifying the administrator of record for a given program
• Program administrator's own current posted terms and application instructions, which are the only authoritative source for eligibility and amounts
• See related: Explaining Rebates and Incentives Without Overpromising; The Promise a Shop Cannot Make About Someone Else's Money