Something not working, or a number looks wrong? Write to a person. That person is Lou.
Usually answered within a day. Include your repair order number and what you expected to see.
Every scan lands on a Check the scan screen before it saves. Fix any field there and tap save. If a whole estimate reads badly, email the PDF to support and it will get looked at directly, because that usually means a layout the parser has not seen yet.
uFlag moves body-side lines to paint using a keyword list: cover for overspray, mask for primer, remove adhesive, and others. If your shop words an operation differently, the keyword list is editable in Settings. Send the exact wording and it can be added for everyone.
It is removed on purpose, before anything is written to storage. uFlag keeps the repair order number, the vehicle, the labor lines and the totals. Names, addresses, phone numbers, and insurance and claim details are stripped. The Check the scan screen tells you how many items were removed.
Not today. uFlag currently runs on your phone for you. Shared shop features are being scoped, and when they arrive, exactly who can see what will be stated plainly before anything is turned on.
Jobs are stored on the device. Settings has a data recovery option. If that does not bring them back, email support before reinstalling the app, because a reinstall clears local storage.
The more of this you can include, the faster it gets fixed:
Do not send estimates with customer information on them. A photo with the customer block covered is fine.
Wanted. uFlag is built from what techs actually ask for, and most of what is in it came from someone saying it was missing. Same address.