1 approved packet
Use a normal heat-pump rebate packet from a standard office flow so we can see the baseline paperwork shape.
Free first step
Keep the ask narrow enough that a busy office can actually say yes.
What to send for a fast RebateOps packet triage.
The goal is not a perfect file dump. The goal is enough paperwork shape to show the first blockers, likely correction loops, and the next office action.
Send these first
The shortest useful packet bundle is two examples.
1 rejected or corrected packet
If possible, send a packet that triggered a correction loop so we can identify where the process started to break.
Related pages
Include invoice, equipment, utility-bill, proof-of-payment, or correction pages if they are tied to the example packets.
Redactions are okay
We only need the paperwork shape and blocker pattern. Screenshots, scans, and partial exports are acceptable.
What comes back
The triage return is narrow and practical.
Output 1
First missing-item checkpoints
The earliest places where the packet is likely to stall or fail internal review.
Output 2
Likely correction loops
The parts of the packet that most likely create back-and-forth with the utility or internal reviewer.
Output 3
One clear next action per packet
A single recommended office move instead of a long generic checklist.
Send files
Email the packet examples directly and keep the office lift low.
Send the files to hello@rebateops.co. Redacted PDFs, screenshots, or exports are all acceptable.