What we would aim for
After a call ends, a record in Workiz with the caller, the address, and the job details. Workiz separates leads from jobs, so which one a phone call becomes is a decision we make with you.
Field service
On requestWorkiz shops tend to buy leads from several places and funnel them into one board. If the phone is one of those feeds, a call that ends as a Workiz record is the obvious next step. It is not built yet.
On request. Not live. There is no Workiz connection to switch on. We scope and quote it for a shop that needs it.
After a call ends, a record in Workiz with the caller, the address, and the job details. Workiz separates leads from jobs, so which one a phone call becomes is a decision we make with you.
API credentials from your Workiz account and a clear idea of which lead sources already land there, so we don’t create the same lead twice.
Assign a technician or edit your schedule. Dispatch stays in Workiz.
A call you pick up yourself never reaches us. For a call the receptionist takes, a build would write after the call ends.
The same write at any hour, so the overnight call is a record waiting in Workiz.
What scoping would cover. Nothing to connect today.
Where Angi, Thumbtack, Google, and the phone feed into Workiz today.
Which Workiz record a phone call should become.
Adapter work is quoted at setup and tested before live calls.
Not yet. It is on request and quoted at setup.
That is the kind of thing we scope. The goal is one record per job, not two.
The phone answering, the booking calendar, and the on-call text. Your office keys the job into Workiz.