The examples below show what a useful message in each category looks like. These are format examples only.
Correction request example:
> Subject: Correction request - /glossary/apr > > The APR glossary page states that APR always includes all fees charged by the lender. I believe this is imprecise - federal disclosure rules excludes certain fee types from the APR calculation. Here is a link to a primary regulatory explanation (URL omitted in this format example). Could you review and clarify?
This message works because it names the specific page, identifies the specific claim, explains why it may be wrong, and includes a source.
Editorial question example:
> Subject: Question about calculator methodology - /calculators/loan-payment > > The loan payment calculator produces an estimate but does not explain what compounding convention it uses. Is this monthly compounding on the outstanding balance? I want to understand whether the estimate matches a standard amortization formula.
This message works because it identifies the page, asks a specific methodology question, and explains why it matters to the person asking.
Technical feedback example:
> Subject: Broken link - /loans/personal > > The link to the origination fee glossary entry on the personal loans page returns a 404 error. I am using Chrome on a desktop. URL: loansplainly.com/loans/personal.
This message works because it identifies the page, describes the issue specifically, and includes the technical context needed to reproduce it.