The problem
A client says yes. Somebody has to turn that into a job the team can start. The deposit, the site details, the access, the contact, the order number, the drawings at the right revision. Then the handover itself, so the engineer knows what was actually agreed. Most of that is a checklist, and the checklist lives in one person's head.
When that person is busy, the job waits at "accepted" with nothing raised, and the first anyone hears of the gap is the engineer ringing from the site.
What it does
Once terms are accepted and payment is in, the gate reads the job record against your handover checklist, field by field. It writes a handover summary into the job system from what is there: what was quoted, what was excluded, where, when, who the contact is. Anything missing goes back to the client in an email drafted in your wording, for a person to send. If it still has not arrived, a chase is drafted on the schedule you set, for a person to send, until it does.
A complete job is marked ready and handed to the person who schedules it, with the summary attached.
What it needs from you
Your handover checklist, written down, which usually means writing it down for the first time. Where "accepted" and "paid" are recorded, and whether they are recorded reliably. Your wording for a chase email, so the client hears from you and not from a machine.
Two people will disagree about what has to be in place before a job can start. The gate needs one answer.
What it does not do
It does not accept the quote, take the payment or schedule the job. It does not send anything to a client: the first email and every chase after it are drafted for a person to send, and the chasing stops at the point you set. It does not know that a particular client always sends the order number late and is allowed to. A person still reads the ready list. Nothing that costs money or affects safety goes through without someone checking it.
This is one stage of the pipeline. If several stages have the same problem, the route page covers the whole thing.
Nearest route: Pipeline automation. Back to Services.