Compliance
Every Curbmark review ties back to a verified record.
The 2024 FTC rule on fake reviews and false endorsements is enforceable. Curbmark is built so the audit trail is a byproduct of the workflow, not an afterthought.
The 2024 FTC rule, in plain language.
The FTC’s 2024 rule on fake reviews and false endorsements prohibits practices like purchasing reviews, conditioning a gift or discount on the content of a review, manufacturing praise from people who did not actually transact with the business, and running anonymous incentive programs that ask customers for reviews without telling them they are being compensated. Penalties are civil and per-violation.
Curbmark stays on the right side of that rule by construction. Every review invitation the platform generates is tied to a verified closing record the dealership actually has — a deal jacket for a sale, a service RO for a repair visit, a CRM milestone for any other documented event. There is no anonymous incentive program, no paid review-solicitation channel, and no path to fabricate an invitation that does not trace back to a real record.
Every invitation is also logged with its source record — which dealership, which send channel, which deal or RO — so the dealership can hand an auditor a paper trail instead of a promise. The next two sections spell out exactly what we record and what the dealership keeps.
What we record
Four fields, every time.
Each intake row carries the same four pieces of information. Together they are the minimum needed to defend a review request in an audit.
The franchised rooftop on whose behalf the request is sent. Structured on every Intake row.
The channel the BDC chose to send the request from. Captured in the request log at send-time and surfaced in the audit trail.
Captured by dealership staff as free text at intake — deal jacket number, RO number, or CRM milestone reference that proves a real closing event.
UUID minted at intake (Intake.token). The same token rides in the review-ask message and the review-landing URL, so the eventual review ties back to the row.
Audit defence
What you keep for an audit.
If a regulator, OEM, or plaintiff’s counsel asks how a particular review was solicited, the dealership should be able to produce the following documentation from its own systems and from Curbmark’s intake log.
- Request-token log — every Intake row with its minted UUID, keyed to the deal or RO it was generated from.
- Source record reference — the deal jacket, service RO, or CRM milestone captured at intake (in Intake.notes).
- Send channel — email or text, recorded at send-time so the message that asked for the review is traceable.
- Timestamps — when the record was logged (Intake.createdAt) and when the request was delivered.
- Corresponding review outcome — the platform review that returned through the token, if any.
Methodology FAQ
The questions an auditor is most likely to ask.
Short answers, in plain language, on the questions we hear from dealer principals, general counsels, and OEM compliance teams.
Talk to us
Want a sample audit packet for your group?
Bring one or two stores; we map a real pilot shape against your CRM, DMS, and current reputation vendor. No checkout, no sales-bot loop.