For service business dem
When di product na person wey go reach by ten
Fitter people, installer dem, clinic, studio, workshop, trainer — anybody wey dia sale end with van, chair or room. For you, booking no be step wey come after deal — di booking na di deal itself, and every other thing na admin wey surround am.
Service business dey run on one kain pressure wey no common: di enquiry fit land for time wey no convenient, di answer must fast well well to beat two competitor dem, and once everybody agree, di work na physical event wey no fit change by status update.
Na why di software dey always break for di same place. Di chat widget answer at 23:41; di calendar sabi about Saturday; di payment link dey inside person sent items; di invoice dem raise am on Monday from photograph of notebook. Four system, one customer, and no way at all to answer "Saturday dey confirmed true true?" without asking human being.
- AKChatUna dey install for weekend?
- BOTAssistantSaturday, yes — Marek go confirm slot for morning.
- MWMarekSaturday 10:00 dey free. Make I hold am?
- MWNoteRing di bell, no knock. Dog dey.
- ✓Done, paid, invoice don comot2 400 zł, card, invoice comot from di record.
One recordZero retyping
Di 23:41 problem
Most enquiry for dis work dey land outside working hours, from phone, from person wey dey compare three company at once. Di winner na often just di one wey reply first — na sad thought, until you realise say na something wey fit solve completely.
Di chatbot work here no be to dey clever. Na to establish, at 23:41, say Saturday dey exist, say person go confirm for morning, and say dis person na real contact wey real seller dey own now. Dat one usually enough to still dey inside di race by breakfast time.
Marek come do di part wey bot no fit do: e look real diary and hold real slot.
Di four things wey hang on one record
- Di slot
- E dey hold against di contact, so di calendar entry sabi which conversation e come from — and di conversation sabi say calendar entry dey. Cancellation dey land on di thread, beside di customer explanation.
- Di reminder
- E dey go di evening before, automatic, and e dey show on di thread so di seller fit see say e don go. Dis one line alone dey remove most no-show and all di argument about whether reminder send or e no send.
- Di payment
- Dem charge am to di seller own account, and dem record am back on di contact. Di person wey do di work fit see say payment enter without asking anybody for office.
- Di invoice
- Dem raise am from di record wey already get di customer, di price and wetin dem do. For Polish business, e include KSeF, wey dem configure per company because di obligation date depend on di company.
Di note about di dog no be joke — or make I say na joke wey still dey true every time. Every service business dey run on details like dis one: di gate code, di neighbour wey get key, di customer wey no fit pick call before ten. Software wey no get where to put dose details na software wey your team go quietly work around.
One working week
Wetin really dey change
Di van sabi
Whoever show up get di thread for phone: wetin dem quote, wetin dem promise, di gate code, and say di last visit no go well. To arrive with information na most of to arrive well.
Saturday get answer
"Saturday dey confirmed?" get one place to look and one answer. No need to ring office, no need to cross-check two calendar wey disagree by one hour.
Monday dey shorter
No need to rebuild di week from receipt and memory. Di invoice dem raise am as di job close, from record wey already get di details inside.
From "una dey work Saturday?" to paid invoice, all on one record.
Eleven days, four channel, one customer, and nobody type address pass one time — di customer sef no type am pass one time.
“Saturday don sure like dis?”
One place to check. One answer.
The slot, the reminder, the payment and the invoice all dey hang on the same contact — so anybody wey show go already sabi the gate code, and sabi about the dog.
The pipeline, reach the invoice →