Vol. I · No. 23

Back Office Beat

Mon–Fri, 6:30 a.m. MT · Three to five items · Free

Published by J9 Systems
Subscribe

The daily brief · No. 23

Monday, November 9, 2026

FTC's $49.75M Progress Residential settlement targets hidden fees and review gag clauses

By Carter Josephson · Filed 5:10 AM MST MT

The FTC's $49.75M settlement with Progress Residential punished hidden fees and review gag clauses, and both show up in many trade quotes and service agreements. Start today by spending an hour checking your website, quote and invoice templates for left-out fees and no-bad-review language.

In this brief

  1. 1FTC's $49.75M Progress Residential settlement targets hidden fees and review gag clausesTry it
  2. 2Google Meet now lets admins show a recording and Gemini-notes policy before every callTry it
  3. 3OpenAI API credit top-ups failed on some Brex and business Mastercards on Nov. 6Try it
  1. FTC's $49.75M Progress Residential settlement targets hidden fees and review gag clauses

    The case involves a landlord, but the same two practices regulators punished here, prices that leave out mandatory fees and no-bad-review clauses, appear in plenty of trade quotes and service agreements.

    By Carter Josephson · · Share this item

    What happened

    Progress Residential, which manages over 90,000 single-family rental homes, and its owner Pretium Partners will pay $49.75 million to settle charges from the FTC and Arizona, Colorado, Indiana and Utah that they advertised false rental prices, charged hidden fees, improperly withheld security deposits and used nondisparagement clauses in form contracts. The proposed order, announced Nov. 6, 2026, requires Progress to advertise a "true total monthly rental price" that includes all mandatory recurring fees more prominently than any other price, and bars standardized nondisparagement clauses.

    What it means for a 10-to-50-person business

    The order binds only Progress and Pretium. It still shows how the FTC and four state attorneys general define deceptive pricing: if a fee is mandatory, it belongs in the advertised price. Example: a 14-person plumbing company advertises "Drain cleaning from $89" on its website and Google profile. Every job also carries a mandatory $49 trip charge and a $15 "service admin" fee that customers first see on the invoice. The customer was shown $89 and pays $153, and 42% of the bill was never shown up front. That is the same pattern the FTC called deceptive in this case. The second risk is a service agreement that forbids negative reviews. The FTC alleged these clauses are unlawful, and federal law has generally voided them in consumer form contracts since 2016. Owners who sell to homeowners and advertise prices should care, especially in Arizona, Colorado, Indiana and Utah, whose attorneys general joined this case. Firms that bill only businesses, or that quote every job custom with all fees on the quote, can ignore it.

    What to do
    Try it

    Spend one hour this month comparing every advertised price on your website, ads, Google profile and quote templates against a real invoice, and either fold mandatory fees into the advertised number or show them right next to it, and delete any no-negative-review language from your service agreement.

    What it costs
    What it costs
    Owner review of website, ads, quote and invoice templates
    1 hr (≈ $75 at $75/hr, assumed)
    Web or template edits to show all-in prices
    1–2 hrs (≈ $100–$200 at $100/hr, assumed)
    Removing a no-negative-review clause from service agreement
    30 min (≈ $40)
    Doing nothing
    $0 now; exposure if a customer complaint reaches a state attorney general or the FTC, which says it is monitoring pricing transparency
    Sources
    ftc.gov (primary)
  2. Google Meet now lets admins show a recording and Gemini-notes policy before every call

    If your staff record client calls or let Gemini take notes in Meet, you can now put your house rules on screen before every call they join.

    By Carter Josephson · · Share this item

    What happened

    In its Nov. 6, 2026 weekly recap, Google said Workspace admins can now set custom policy text in the admin console that is shown in the Google Meet green room before users join a call. Google says the feature is meant to help users at your organization know your rules for meeting recordings, transcriptions and notes taken by Gemini.

    What it means for a 10-to-50-person business

    This is a free reminder screen, not a compliance tool. Take an 18-person accounting firm where 10 staff use Gemini to take notes on client calls. The admin can add two lines: "Ask the client before you record or turn on Gemini notes. Save notes to the client folder, not your own Drive." Every staff member then sees that text before every Meet call. Setup takes about an hour, mostly spent agreeing on the wording. There are limits. Google describes the text as shown to users at your organization, and the recap does not say external guests see it. It does not replace asking clients for consent. About a dozen states, including California, require every party's consent to record. The recap also does not say which Workspace editions get the setting or when it reaches every account. Law firms, accounting firms and agencies that record client calls should set it up. Trades shops that do not record Meet calls or use Gemini notes can ignore it.

    What to do
    Try it

    This month, have whoever runs your Google admin console check Meet settings for the custom policy text option, and if it appears, add two or three plain sentences on client consent and where recordings and Gemini notes get saved.

    What it costs
    What it costs
    Feature price
    none stated in Google's recap
    Writing and setting the policy text, 1 admin
    1 hr (≈ $50 at $50/hr)
    Agreeing on the wording with partners or managers
    0.5 hr (≈ $25 at $50/hr)
    Doing nothing
    $0 now; staff keep recording and running Gemini notes with no on-screen reminder of your rules
    Sources
    workspaceupdates.googleblog.com (primary) · Google Workspace release calendar · Google Workspace Admin Help
  3. OpenAI API credit top-ups failed on some Brex and business Mastercards on Nov. 6

    If an automation runs on your own OpenAI API key paid with a business Mastercard, a failed auto-recharge can stop it when the balance hits zero.

    By Carter Josephson · · Share this item

    What happened

    On Friday, Nov. 6, OpenAI's status page reported payment declines on some U.S. business Mastercards, including some Brex cards, with affected card numbers beginning 544015, 546400, 543502, 543799 or 512998, and some beginning 513989. OpenAI said the declines can block API automatic recharges and one-time credit purchases, so API requests may fail once a prepaid balance runs out; later that day it said it had applied a mitigation and was monitoring recovery.

    What it means for a 10-to-50-person business

    This only matters if your business holds its own OpenAI API account on prepaid credits and pays for it with an affected card. Take a 25-person accounting firm with a Make scenario that sends new client emails to the OpenAI API for summaries and tagging. Assume auto-recharge adds $50 when the balance falls below $10, paid on the firm's Brex card. If that recharge is declined, the scenario keeps running until the last $10 is spent, then every call fails. Intake emails stop getting tagged, and an admin sorts them by hand. Assume that takes 2 hours a day at $45 an hour, or $90 for each day nobody notices. OpenAI's notice covers API billing only. It says nothing about ChatGPT seat subscriptions. If your AI features come built into a vendor's product and the vendor pays OpenAI, there is nothing for you to do. If your card starts with a different six digits, you can ignore this.

    What to do
    Try it

    If you pay for an OpenAI API account with a business Mastercard, check the first six digits against OpenAI's list, add a backup card from a different issuer, and retry any credit purchase that failed on or after Nov. 6.

    What it costs
    What it costs
    Check card digits and API billing history
    10 min (≈ $8 at $50/hr)
    Add a backup card from another issuer
    $0
    Retry a failed credit purchase
    5 min (≈ $4 at $50/hr)
    Manual work if an automation stops, 2 hrs/day at $45/hr
    ≈ $90/day
    Doing nothing
    $0 if OpenAI's mitigation holds; if a recharge fails, automations stop once the prepaid balance hits zero
    Sources
    status.openai.com (primary)

Also happened

Corrections and updates

None. How corrections work.

Get the next one at 6:30 a.m.