Invoice drafts on service calls

Nobody starts an invoice from a blank page in Escape. Here's the flow on a service call.

What happens automatically

When your tech marks a service job On Site, Escape drafts the service invoice in the background — attached to the right customer and the right job, with your standard service charge on it.

By the time the tech is diagnosing the system, the paperwork is already half done.

What happens next — a human sends it

The draft waits for your office. Someone reviews it, adds the parts and work from the visit, and sends it — or the tech collects payment on site and the office reconciles it.

Drafts never go to the customer by themselves. No customer ever gets an invoice your team didn't look at first. The automation does the tedious part (creating it, attaching it, starting it); your people do the judgment part (what the job actually cost).

Why it works this way

• Speed — invoices go out the same day, because they're already started. Same-day invoices get paid dramatically faster than ones sent "when we get to it."
• Accuracy — the invoice is born attached to the job and customer, so nothing gets billed to the wrong person.
• Control — pricing decisions stay with your team, always.

For office staff

Make reviewing drafts part of the daily rhythm — end of day at the latest. A stack of unsent drafts is money sitting on the counter. Once an invoice is sent, Escape watches it: if it goes unpaid, the late-payment reminders take over, and the moment it's paid, the job is marked won.