For service businesses
When the product is a person arriving at ten
Fitters, installers, clinics, studios, workshops, trainers, anyone whose sale ends with a van, a chair or a room. For you the booking is not a step after the deal — the booking is the deal, and everything else is admin around it.
Service businesses run on a peculiar kind of pressure: the enquiry arrives at an inconvenient hour, the answer has to be fast enough to beat two competitors, and once it is agreed, the work is a physical event that cannot be rescheduled by a status update.
Which is why the software usually breaks in the same place. The chat widget answered at 23:41; the calendar knows about Saturday; the payment link lives in someone's sent items; the invoice is raised on Monday from a photograph of a notebook. Four systems, one customer, and precisely no way to answer "is Saturday actually confirmed?" without asking a human.
- AKChatDo you install on the weekend?
- BOTAssistantSaturdays, yes — Marek will confirm a slot in the morning.
- MWMarekSaturday 10:00 is free. Shall I hold it?
- MWNoteRing the bell, do not knock. Dog.
- ✓Done, paid, invoiced2 400 zł, card, invoice raised from the record.
One recordZero retypes
The 23:41 problem
Most enquiries in this trade arrive outside working hours, from a phone, from somebody who is comparing three companies in one sitting. The winner is frequently just the one who replied first — which is a depressing thought until you realise it is also an entirely solvable one.
The chatbot's job here is not to be clever. It is to establish, at 23:41, that Saturdays exist, that someone will confirm in the morning, and that this person is now a real contact owned by a real seller. That is usually enough to still be in the running at breakfast.
Marek then does the part a bot cannot: he looks at a real diary and holds a real slot.
The four things that hang off one record
- The slot
- Held against the contact, so the calendar entry knows which conversation it came from — and the conversation knows there is a calendar entry. Cancellations land on the thread, next to the customer's explanation.
- The reminder
- Sent the evening before, automatically, and visible on the thread so the seller can see that it went. This single line removes most no-shows and all of the arguments about whether a reminder was sent.
- The payment
- Charged to the seller's own account, recorded back on the contact. The person who did the work can see that it was paid without asking anyone in an office.
- The invoice
- Raised from the record that already holds the customer, the price and what was done. For Polish businesses that includes KSeF, configured per company because the obligation date depends on the company.
The note about the dog is not a joke, or rather it is a joke that keeps being true. Every service business runs on details like it: the gate code, the neighbour with the key, the customer who cannot take calls before ten. Software that has nowhere to put those details is software your team will quietly work around.
A working week
What actually changes
The van knows
Whoever turns up has the thread on a phone: what was quoted, what was promised, the gate code, and that the last visit went badly. Arriving informed is most of arriving well.
Saturday is answerable
"Is Saturday confirmed?" has one place to look and one answer. No ringing the office, no cross-checking two calendars that disagree by an hour.
Monday is shorter
No reconstructing the week from receipts and memory. The invoices were raised as the jobs closed, from records that already had the details in them.
From "do you work Saturdays?" to a paid invoice, on one record.
Eleven days, four channels, one customer, and nobody typed an address more than once — least of all the customer.
“Is Saturday actually confirmed?”
One place to look. One answer.
The slot, the reminder, the payment and the invoice all hang off the same contact — so whoever turns up already knows about the gate code, and about the dog.
The pipeline, to the invoice →