Contacting support and what to include

Most questions are answered in the Help Zone faster than support can reply. Use this article when you've checked the docs and you still need a human.

When the Help Zone is enough

"How do I do X?" — search the Help Zone first. Every shipped feature has a walkthrough.
"Is X possible?" — most "is this supported" answers are explicit in the relevant article's What's not yet or Troubleshooting sections.
"Why is the number off?" — see Money tab overview, Outstanding bucket explained, and Coverage percentage explained.

Anything that needs an actual human on our side:

Billing problems — charges you didn't expect, refunds, App Store receipt issues.
Account access problems — locked out, sign-in failing, recovery emails not arriving.
Data problems — something missing or wrong that you can't explain from the troubleshooting sections.
Bug reports — the app crashed, a button doesn't respond, something looks broken.
Privacy or data deletion requests — even though deletion has a self-serve flow, support can help if it's not working for you.
Anything that asks for a real human's judgement.

Use the support portal at support.corrplus.net. It's a ticket system — submit your question, get a response by email.

There is also a /contact-support page on this site that links to the same destination.

The faster you give support what they need, the faster they reply. A good ticket has:

What happened, in plain English. "I tapped Send on my invoice and the share sheet didn't open."
What you expected to happen. "The iOS share sheet usually opens and lets me pick Mail."
What you actually saw. "Nothing — the button highlighted but no sheet appeared."
What you've already tried. "Force-quit the app and tried again. Same result. Re-installed. Same result."
The app version. Open Settings → scroll to Version at the bottom. Include the full string (e.g. 1.2.3 (45)).
iOS version. Open iOS Settings → General → About → Software Version.
iPhone model. Same place as iOS version — Model Name.
A screenshot or screen recording if the issue is visual.

For billing tickets, also include:

The email address on your FreelancerFlow account.
The last four digits of the card that was charged, or the Apple ID email if it was an App Store charge.
A screenshot of the charge if you have one.

For account-access tickets, include:

Passwords. Support will never ask for your password. If anyone claiming to be support does, it's not us.
Card numbers in full. Last four digits are enough.
Sensitive client data beyond what's needed to reproduce the issue. If your bug is about a specific invoice, anonymise client names where you can.

Acknowledgement within one business day.
A diagnostic question or a fix within two to three business days.
If the issue needs a code change, you'll get a target version for the fix and a workaround if one exists.