Every email your customer can get

“What did you send my customer?” Sooner or later every office fields it. The full answer is short: your customers can receive exactly four emails, each caused by something concrete, each in your company’s name. Here is the map — what triggers each one, what it contains, and where its switch lives.

The four, at a glance

Email	What causes it	Default
Completion email	A job completes	On — can be switched off
Receipt	A payment clears	Automatic
Statement	You send one, or a reminder schedule you turned on does	Only when sent
Card declined	A saved card fails when a completed job is charged	Automatic, and only for cards on file

The completion email

Sent the moment a job completes: what was done at their property, item by item, with a link to their own page for the job. If they owe and LakeOps Payments is on, there’s a button to pay; a customer whose card on file was already charged sees a settled bill instead — nobody is offered a way to pay twice. It goes once per job, and it has a switch in your account settings for shops that prefer to bill entirely on their own rhythm. The full story is in charge on completion.

The receipt

Sent when money clears — an online payment, a charged card on file, or a cheque you recorded by hand. One per payment, frozen as of the day the money moved, and the office can send it again — to the customer, or to their bookkeeper at a different address.

The statement, and the reminders that reuse it

A statement lists everything a customer still owes, oldest first, with one link to pay the lot. It goes only when caused: you send it from their page, or — once you’ve turned reminders on — the schedule sends it when a debt ages past your steps. It’s the same document either way, a customer only ever moves forward through the schedule, and nothing is ever sent to someone who owes nothing. A customer whose saved card is about to be charged isn’t reminded either — a note asking for money that’s already mid-flight is a note you’d have to apologize for. If you charge late fees, there is no separate late-fee email: the fee policy prints on the statement, and the fee itself appears as its own line.

The card-declined note

Only possible for customers who chose to keep a card on file. If the charge for a completed job fails — expired card, bank said no — they get a short note saying so, with a link to pay another way. Nothing nags them again; the balance simply remains, visible in who owes you money.

What your customers never get

Your customers have no logins, so there are no sign-in codes, password emails or account notices — the six-digit code email is only ever sent to people you’ve invited onto your team. There are no marketing emails, and nothing sent on LakeOps’ own behalf. Every email above happens because of work you completed, money that moved, or a schedule you switched on — and each one’s subject line carries your company’s name, because to your customer, it’s you talking.