Do not compare bare numbers
A unit could represent a message segment, a minute, a resource or another product-specific event. Two small-looking prices are not comparable until the units match. Start from the current documentation and the actual billing record for the relevant service. Avoid publishing a universal per-message price when the charge can depend on how the message or destination is classified.
Build a unit dictionary
Create a small private table with service name, unit definition, source, observation date and example quantity. Include currency and any minimum or separate recurring resource charge you have actually verified. This dictionary is an operational explanation, not a copy of client communications. It should let another team member understand why a quantity was used without reading private message content.
Work a synthetic mismatch
Suppose one fictional report counts 100 customer interactions while another counts 140 billable units. That difference alone does not prove overcharging. The units may represent different things or cover different dates. Before calculating a markup, align the periods and definitions. If the explanation remains unknown, keep the discrepancy open and collect the narrow relevant record rather than forcing the totals to agree.
Carry the unit into the plan
A client-facing explanation can be brief but should still identify what varies and where the applicable rate is available. Use the same vocabulary in estimates, invoices and support responses. Recheck the unit definition when changing providers or enabling an add-on. A historical rate may remain useful for reconciling an old period, while being unsuitable for a new quote. Preserve that distinction instead of overwriting the original assumption. The next record should show one quantity multiplied by one matching rate, with its period and currency. Keep an unexplained discrepancy separate rather than burying it inside a blended average.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- HighLevel billing and wallets — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27