The Default That Charges Money

There is a moment in every arrangement where somebody has to decide what happens if nothing happens.

A trial ends and the guest has not signed up. A deposit is taken and the party never confirms. A card on file expires and the next charge is due.

⚠️ Somebody decided what happens next, and it was probably not you. It was whoever wrote the software, or the contract, or the form. And their default is almost never "do nothing" — because doing nothing is not a thing a system can do.

The short version

• Every arrangement has a "what if nothing happens" branch
• Somebody set that branch. If it was not you, it was a supplier's default
• Defaults that move money are the ones that matter
• The test: "if the guest does nothing at all, what happens on Friday?"
• You usually find these at the moment they fire, which is the wrong moment

Why defaults decide more than policies do

What you think decides	What actually decides
Your policy	What the system does when nobody acts
The conversation at the door	The setting nobody has opened
What you told the guest	What the software was shipped with

⚠️ Most guests do nothing. They do not cancel, confirm, decline, or reply. So the branch that fires most often is the one nobody thought about.

One: a real one, from our own operation

We run free trials. A venue signs up, uses the system for thirty days, and decides.

We believed that a trial ending without a payment method meant nothing happened — no card, no charge. That was the sentence we were ready to put in writing to a customer.

⚠️ It was wrong. The billing system had a setting for exactly this case, and its default was "create an invoice."

Trial ends, no payment method on file
  What we assumed  nothing happens
  What was set     issue an invoice for the first month

⇒ A customer who had simply stopped using the trial would have received a bill. Not through malice, not through a mistake anybody made — through a default nobody had looked at.

How it was found

Not by an audit. By somebody asking a narrow question on the morning it mattered: "what actually happens at 15:23 today?"

⚠️ That question is the whole technique. Pick a real moment, in the near future, and ask what the system will do.

Two: where these live in a venue

You have more of these than you think.

Deposits      what happens to an unclaimed deposit after N days
Card on file  what happens when the card expires or declines
Tabs          what happens to an open tab at close
Bookings      what happens to a booking nobody confirms
Memberships   what happens at renewal if nobody responds
Vouchers      what happens to an unused voucher after its date

⚠️ Each of those has a default. Some were chosen by you. Most came with whatever system you signed up to.

The ones that hurt

Defaults that charge   - a guest gets billed for something they thought had lapsed
Defaults that refund   - money leaves without anybody deciding
Defaults that delete   - a booking or a record vanishes silently

⇒ The first is the worst, because the guest finds out before you do, and they find out in the form of a complaint.

Three: the question that finds them

For each arrangement, ask one thing.

"If the guest does absolutely nothing, what happens - and when exactly?"

⚠️ "And when exactly" matters. A default that fires "eventually" is one you will meet by surprise. A default that fires at 15:23 on the 19th is one you can decide about.

Do it with a date

Abstract questions get abstract answers. Pick a real case.

Bad   "what happens to deposits that aren't claimed?"
Good  "Tanaka-san's deposit from the 3rd - what happens to it, and on what date?"

⇒ Naming a real person and a real date forces somebody to go and look, rather than recite what they believe.

Four: the three answers a default can have

When you find one, there are only three things it can do.

Charge   bill somebody
Cancel   end the arrangement
Hold     pause it and wait

⚠️ Most systems default to charge, because that is the behaviour that makes the vendor whole. That is not sinister — it just means the default is set for somebody else's interest, not yours or your guest's.

Which to pick

Charge   right when the guest has clearly opted in and simply forgot
Cancel   right when silence most likely means "no thanks"
Hold     right when you want a person to look before anything happens

⇒ For anything where silence probably means no, cancel is the honest default. Billing somebody for their silence produces a refund, a complaint, and a review.

What we changed

We moved ours from charge to cancel. If a trial ends with no payment method, the arrangement simply ends.

Before  no payment method at trial end  ->  invoice issued
After   no payment method at trial end  ->  arrangement ends, nothing billed

⚠️ We also deliberately did not cancel it early. Anybody who added a card before the deadline still continued — because the point was to stop billing people who said nothing, not to close the door on people who might still say yes.

⇒ That distinction matters. It is easy to "fix" a default by making it stricter and quietly removing the guest's choice.

Five: the default you set by accident

The other half of this is defaults you created without noticing.

A form field pre-filled with a value nobody reviews
A checkbox that starts ticked
A "standard" rate that everyone gets because nobody asked for another

⚠️ A pre-filled field is a decision made on the guest's behalf, and you will be held to it.

⇒ On the related problem of settings that changed without anybody knowing: the setting nobody remembers changing.

Six: why you find these at the worst moment

Defaults are invisible until they fire, and when they fire they are usually already irreversible.

The deposit is already forfeited
The invoice is already sent
The booking is already gone

⚠️ An invoice that should not have been sent cannot be un-sent. You can credit it, apologise, and explain — but the guest has already read it.

The one habit that helps

Before any deadline that involves money, ask the question the day before, not the day of.

"Anything hitting a deadline this week where a system decides for us?"

⇒ One question at a weekly meeting. It costs a minute and it moves the discovery from after to before.

Seven: the same shape in the other direction

Defaults can also be set to do nothing when you needed them to act.

A reminder that never sends because it was never switched on
A suspension that never happens because the rule matches nobody
A follow-up that waits for a condition that can never be true

⇒ That is the mirror problem, covered in the automatic message that never sent. Both come from the same blind spot: nobody checked what the system does when left alone.

The default that only one person can change

Worth checking alongside: even where the default is correct, ask who can alter it at short notice.

⇒ If the answer is one named person who may be unreachable, that is a second problem on top of the first — who can say stop covers it.

Numbers worth keeping

One   How many arrangements you have where a deadline triggers something
Two   For each: charge / cancel / hold - and who chose it
Three How many of those you have personally confirmed (not assumed)
Four  How many complaints in the last year began "I didn't ask for this"

⚠️ Four is the diagnostic. Complaints that start with "I didn't ask for this" are almost always a default firing.

The card for the office

────────────────────────
  Finding a default that moves money

  1. Name a real guest and a real date
  2. Ask: if they do nothing, what happens - exactly when?
  3. Find out whether it charges, cancels, or holds
  4. Decide whether that is what you want
  5. If you change it, do not also remove the guest's chance to say yes

  Most guests do nothing.
  The "nothing" branch fires most often.
────────────────────────

Common objections

"Our system wouldn't charge without permission"

⚠️ It would charge according to a setting somebody accepted, possibly years ago, possibly by not changing it. That is permission in the legal sense and a surprise in the human sense.

"We've never had this happen"

⇒ You have never had it reported. A guest billed unexpectedly often just pays, resents it, and does not come back.

"We'd notice an invoice going out"

⇒ Would you? Most venues see invoices they issue in a list, not one at a time. The one that should not have gone out looks exactly like the ones that should.

"This sounds like a software problem"

⚠️ It is a decision problem wearing software clothing. The software will do something. The only question is whether you chose it.

"The confirmation said it was fine"

⚠️ A screen confirming a setting is not proof the setting is doing what you read — the shape covered in the edit that said saved. Read the behaviour back, not the label.

"We can just refund it"

⇒ You can, and you should. But the refund does not undo the message the guest received, and it does not undo their decision about whether you are careful.

What to do this week

One   List every arrangement with a deadline that moves money.
Two   For each, name a real case with a real date.
Three Ask what happens if that person does nothing.
Four  Write down: charge / cancel / hold - and who chose it.
Five  Change any where "charge" was never actually your decision.

⇒ If the answer to step three is "I'm not sure", that is the finding. Go and look at that one first — it is the one that will surprise you.

Summary

• Every arrangement has a "nobody did anything" branch, and it fires most often
• If you did not choose it, a supplier chose it, usually in their own interest
• The finding question: "if this person does nothing, what happens and exactly when?"
• Prefer cancel where silence probably means no; charge only where opt-in is clear
• When you fix a default, do not remove the guest's chance to still say yes
• Complaints beginning "I didn't ask for this" are defaults firing

A system cannot do nothing. Somebody decided what "nothing" means, and if it was not you, it is worth an afternoon to find out what they picked.