Keep the reference.
We can start there.

Send enough context to investigate

• The app name: HourReserve or RefMatch.
• The approximate time and displayed message.
• The original review ID or allowance request key.
• A brief description of the action and what happened.
• A screenshot with unrelated personal and business information removed, if helpful.

Keep passwords, access tokens, full customer exports and payment information out of the message.

If an approval response was interrupted

Keep its original reference and use the app's saved-result check first. An interrupted response does not establish whether the action saved.

For HourReserve receipts, check the original review ID or allowance request key. For RefMatch recovery, check the original review under the same client and staff identity.

Avoid creating a replacement allowance or approval while the earlier outcome is uncertain.

Access is configured for the pilot

The current builds use explicitly enabled account and staff access. RefMatch updates are disabled after its controlled write test; its preview and saved receipts remain available to enabled test users.

Installing a private app does not automatically enable backend access. Contact us about the intended test account before entering business data. Use agreed synthetic records during private acceptance.

Questions about app data

To ask about access, correction, export or removal, include the app name and business account concerned. Account authority must be established before information is disclosed or changed.

Ledger corrections preserve their linked earlier entries. A saved result, a ServiceM8 source record and a downloaded CSV are separate records; an app-data request does not itself reverse a PO already written in ServiceM8.

Read the current private pilot privacy notice for the publisher, data use and request route. Wider customer terms and verified retention/removal procedures remain release work; no automatic deletion feature or fixed completion time is promised here.