The agent proposes; Graft decides. Everything a service advisor on the front desk can do, and nothing an owner can.
What the agent does
- Look up a customer by phone. If more than one matches, it asks rather than guesses.
- Look up a job, and create one.
- Make a booking. Graft checks capacity, so it can't double-book a day.
- Add a vehicle. A plate Graft already knows returns the car on file.
- Customers, bookings, quotes and invoicing — the service advisor's job, as Graft defines it for your workshop.
What's on the list is set by Graft, not by a switch in the portal: the agent holds the service advisor role, and Graft enforces it on every call.
How it works with Graft
Graft runs its own connection and holds the rules, which is the opposite of every other integration here. The agent asks Graft for things and Graft answers on the workshop's behalf: a full day means offer another day, not an error, and the edge of a service advisor's authority means hand over to a person. Some workshops review agent changes before they take effect. When that's on, the agent tells the customer the booking is being confirmed — never that it's booked.
What your team sees
Graft feeds the app's contact directory through the same connection, with whatever facts your workshop chooses to show on the card.
It’s the same lookup the agent uses, so the card on the ring screen and the customer the agent found are one and the same. More about H3llo Phone.
How it's connected
Hosted by Graft. Graft issues one agent key per workshop and can revoke it; we hold the key and point the agent at it. The agent proposes and Graft validates, server-side. Nothing in Graft depends on H3llo — every screen works with the agent switched off.
Run Graft? Get the agent on your number.
Tell us what you run and we’ll set it up with you. No self-serve sign-up, on purpose: a person connects it and checks it before the first call.