Ready before you open the door.
An enquiry comes in while you are closed. Kogsy checks it against your rules, drafts a reply from what you have told it about the business, and holds it. In the morning you read it, change it if you want, and approve it. Nothing is sent until you do.
What ran overnight: one enquiry
You read the draft with your coffee, change a line if you want, and approve. Only then is it sent.
Sample data. The enquiry is not answered overnight. A reply is ready for you to check.
One automation you can ask for today. Five more we have built as samples.
We say which is which, so nobody buys something that is not ready.
On offer now, as a pilot
Enquiry replies
Reads each enquiry from your website form, drafts a reply from what you have told it about the business, and holds it for you to approve.
In pilot. Checked on our staging site with real mail and a real model. Not yet proven on a client's own enquiries.
Working samples, not on offer yet
Intake
Takes a request from a form or an inbox, pulls out who it is from and what they want, logs it and routes it to the right person.
Working sample. It runs on invented data in our own tests and has never been set up for a client. Not on offer yet.
Quotes
Prices a job in code from your own rate card, saves the quote as a PDF and drafts the cover email for you to check.
Working sample. It runs on invented data in our own tests and has never been set up for a client. Not on offer yet.
Booking
Offers the open slots in your calendar, books the one the customer picks, confirms it and reminds them.
Working sample. It runs on invented data in our own tests and has never been set up for a client. Not on offer yet.
Job tickets and invoices
Turns the tickets your team fills in on a phone into draft invoices and a weekly report for the owner. Code does every sum.
Working sample. It runs on invented data in our own tests and has never been set up for a client. Not on offer yet.
Chasers
Follows up quotes, deposits and overdue invoices on the schedule you set, and stops at a yes, a no or paid.
Working sample. It runs on invented data in our own tests and has never been set up for a client. Not on offer yet.
If one of the samples is the work you want off your desk, tell us. It decides what we get ready next. Enquiry replies have their own page: how they work, and the limits.
Audit, map, build, monitor.
The four stages we work through when we set an automation up for a business.
01
Audit
We sit with you and list where the hours go: what arrives, who touches it, and where it waits.
02
Map
We draw the route each piece of work should take, name who owns it, and say what happens to the odd ones.
03
Build
We set it up in the accounts and tools you already have, with your rules written down where you can read them.
04
Monitor
It runs, every step is recorded, and anything unusual is held for a person to look at.
Rules in code, wording from a model, the decision with you.
The three are kept apart on purpose, and the screen says which is which.
Decided by code
- Who the reply goes to: always the person who wrote in.
- The subject line and the sender.
- Whether a blocked phrase is present.
- Whether a reply goes out twice. It cannot.
Suggested by the model
- The wording of the draft.
- What kind of enquiry it is and how urgent it reads.
- Whether it thinks a person should handle it, and why.
- The model has no tools. It cannot send, change a setting or read another enquiry.
Decided by you
- What the business profile and the rules say.
- Whether each reply is sent, changed or held.
- Whether sending is switched on at all.
- How long enquiries are kept before they are deleted.
Enquiry replies are in pilot, and we say which parts.
The queue, the rule checks and the record are built and tested. Drafting by the model and live email delivery are being verified with pilot businesses before we call them done. No customer results are published here because there are none to publish yet.
Built and tested
- The enquiry form, as a link or embedded in your own page, with limits on repeat and automated submissions.
- A set-up checklist worked out from what exists, and a test mode for the form.
- The business profile and the rule checks on enquiries and replies.
- The approval queue, including the overdue list and the human attention state.
Still being verified in pilot
- Drafting by the language model on real enquiries, measured rather than assumed.
- Live email delivery and delivery reports through a real mail account.
- The daily clean-up running on its own schedule.
Try the sample, then your own form.
The sample needs no account and sends nothing. A pilot runs on one of your enquiry forms, with every reply held for you to approve.