Support

Email a person who knows the product, or read the docs. Whichever gets you moving faster.

How to reach us

Email us

support@workwing.io reaches the people who build WorkWing. No ticket queue to fight through, and no bot in front of it.

Help centre

Guides for jobs, job types, customers, brands, integrations and settings, written against the real console.

Developers

API reference, webhook events and the error code list. If an API call went wrong, send us the request id from the response.

Security reports

Email support@workwing.io with "Security" in the subject. We'll confirm receipt, and we won't take action against anyone reporting in good faith.

Getting a faster answer

We read every message ourselves. The more of this you can tell us up front, the fewer rounds it takes to sort out.

Worth includingYour organisation name in WorkWingWhat you expected, and what happened insteadThe job number, customer or report you were looking atWhether it was the web console or the mobile appA screenshot, if there was something on screen
Reporting a problem from the app

Open the Me tab, then Profile. The build info block at the bottom says which version of the app is running, and the values are selectable so you can paste them straight into the email. Settings has a Report a problem link that opens a message with the right address already filled in.

Signing in to the mobile app

The WorkWing app is issued by the company you work for, so there's no sign-up inside it. Your office creates your account and assigns you jobs, and you sign in with the details they give you. If you don't have them yet, ask whoever runs scheduling for your team.

If you run the operation and want to set WorkWing up for your team, start on the web instead. You can create an organisation, add your engineers and dispatch the first job from a browser, and the app picks them up from there.