See WorkWing at work
Twelve short films, none longer than a minute and a half, with captions on. Every topic is told twice: once for residential work and once for commercial.
Commercial films. Show the residential films
A chiller down, four hours on the clock1:21 A chiller fails at a retail client with four hours on the SLA clock. The job goes from the board to the engineer in the plant room, the client follows it on a tracking link, and jobs at risk of breaching are flagged before they do.
Every feature →An engineer's day1:09 Grace has four client sites to get round. Her jobs are on her phone in order, the client gets a text when she taps On my way, and the form she fills in the plant room sends itself once she's back in range. Back at the office, the board follows her day.
The mobile app →What your client sees1:09 One planned visit as the store manager sees it: the confirmation and reminder emails, the text, the tracking page and the code that proves the engineer at the plant-room door is yours.
Customer tracking →Monday's reactive queue, placed by rule1:08 Seven reactive jobs are waiting on a Monday morning. Choose what auto-assignment weighs and the limits it keeps to, and one click places the whole queue without moving anything already assigned. The urgent chiller goes to the nearest engineer who knows the site, and a job that won't fit says why and is left to you.
Scheduling and dispatch →Save the job, then prove it1:08 Four hours to respond, two if it's urgent, and at month end the client asks how you did. An urgent callout goes at risk while the engineer is still on another site and is handed to someone free in the same slot. A webhook can tell the client's helpdesk if a job does breach, and the compliance figure is in your reports.
Reporting →Eight sites, one project1:11 Emergency lighting at eight client sites, two weeks and three engineers, run as one project. Every visit waits in a shared pool, the crew claim the next one from their phones, and the out-of-hours visit is pinned to its own window. Progress is on one card, and the project closes on its sign-off form.
Projects →What WorkWing is made of1:10 Will it fit the way you work? Jobs, reactive or planned, the sites you look after for each client, engineers with their skills and certificates, a job type per kind of work and projects for the bigger jobs. Then make it yours, down to a contract reference field, your own words (a job becomes a work order) and a wallboard over the helpdesk.
Job types and forms →A second brand for a white-label contract1:00 Ashdown runs one contract under another name. That name is a brand with its own logo, colours, job numbers, wording, emails and tracking page, so its customers see that name and not yours, and behind it the same engineers work both on one board. Every brand is on the same account and the same bill.
Running several brands →Sign-off from IT1:03 Before anyone signs, IT has questions, and the film answers them in the product. Staff sign in through your own identity provider with SAML, two-factor can be required for everyone, roles are built from individual permissions, the audit log records before and after, and API keys get only the permissions they need. Your data is hosted in the EU.
Security →WorkWing and the systems around it1:14 Finance wants to invoice the job, the CRM wants the new customer, and a client's helpdesk wants to raise work orders of its own. Each system gets a signed message the moment something changes, the helpdesk raises jobs straight in through the API with a key that opens only what it needs, and Zapier, Make and n8n join up the rest without code.
The API and webhooks →Checking a purchase order before work starts1:09 Before an engineer goes out, the client's purchase order has to be approved, and the answer is in your finance system. Keep its token in Secrets, set up the call, try it in the test console, and put the button on the job type's form. On a new job, one click tells you the order's approved before anyone sets off.
Integration buttons →Booking a job from Claude1:06 Between meetings, an ops lead asks Claude or ChatGPT to find an engineer and book a lighting fault at a medical centre. Connect it once and it works as you, with your permissions. The job lands on the board like any other, and the audit log names the person who asked.
AI assistants →