Zonara works alongside Workiz.
Workiz stays the system of record. Zonara answers the calls, books and reschedules the jobs, and follows up on the ones that fell through — writing everything back into Workiz.
Nothing gets ripped out.
Your team keeps working where it already works. Zonara answers what the office can’t get to and writes the result back.
The job is on the board before the call ends
Zonara creates the client if they’re new and books the job in Workiz, so your dispatcher sees a normal job rather than a message to process.
Availability comes from your real schedule
Zonara reads what is already booked before it offers a time, so it never promises a window you can’t staff.
Quiet customers get a reason to come back
Zonara reads which clients have gone dormant and can run reactivation against them, inside the approval settings you choose.
What Zonara reads and writes.
This list is exhaustive. Zonara asks for the access its shipped features actually use, and nothing beyond it.
Reads from Workiz
- Clients — name, phone, email, service address
- Jobs — schedule, status, assigned tech, value, job type
- Busy time, so a slot is never offered twice
Writes back to Workiz
- Create a client when an unknown caller books
- Create a job
- Reschedule a job
- Cancel a job with a reason
Zonara runs an incremental sync every 15 minutes using the vendor’s own "modified since" cursor. Where a push webhook is available it acts purely as a doorbell: it tells Zonara to re-poll, and its payload is never trusted as data.
Not read: Payroll, pricebook cost data, employee compensation, and accounting ledgers are never read.
A write that fails goes to a durable retry queue rather than being dropped, and if it keeps failing it is escalated to a person instead of retrying forever. A problem writing to Workiz never voids the customer’s booking — Zonara keeps its own record of every contact and appointment, so no integration is a single point of failure. Read the security detail →
Connect with the API credentials on your own Workiz account.
Workiz issues per-account API credentials, so you can connect Zonara directly without waiting on anyone.
- 1A Workiz admin retrieves your account’s API token and auth secret.
- 2Both go into your Zonara location settings, stored server-side and never exposed to a browser.
- 3Zonara verifies the connection, then begins its 15-minute incremental sync.
Zonara is a layer on top, not a replacement underneath.
Your phone number stays where it is — calls forward, they are never ported. Your team keeps working in Workiz. Every job Zonara books appears there like any other job, so the schedule your dispatcher trusts is still the schedule that runs the day.
Credentials are stored server-side per location, never exposed to a browser and never written to a log. You can revoke Zonara’s access from inside Workiz at any time.
Keep Workiz. Add the front office.
No migration, no porting, no replatforming. Zonara augments the system you already run.