Need help with JobSense? Tell us what happened
Do you need help with Quick Match, a free-trial offer, payments, billing, or a result that seems incorrect? To help us assist you more quickly, please tell us your role, your plan, and the last step you took. For a trial eligibility or registration CTA issue, include whether your email is verified, but never send payment-card details—the free trial does not require them. For a Quick Match consistency question, also say whether you edited the base profile, accepted a job-specific CV Tailor suggestion, or changed the job posting. For mobile App Store or Google Play purchases, purchase restoration, or subscription management, include your device model, operating system and version, store platform, product or plan, and the step or error you see. For push notification issues, also include the OS notification status and whether you expected an application result or a daily job digest. To report an outdated comparison fact, include the comparison URL, the disputed statement, and a current official source.
Check the FAQ first
Most answers are already written down
The FAQ covers how the Match Score is calculated, what CV Tailor changes, what happens to your CV and profile photo, how plans, cancellation and refunds work on the web and in the app stores, how to delete your account, and what we do with your data. If your question is answered there you get the answer immediately instead of waiting for a reply.
Check live status first
See if the issue is already known
The status page shows backend, sign-in, AI, crawl, billing, and document export status in one place. Checking it first can save you time when a score is slow, a document export is delayed, or a login flow behaves differently than expected. If the status page looks healthy, send the message here and include what you expected to happen, what happened instead, and whether the same issue appears after refreshing or trying another browser. For mobile sign-in issues, also include the platform, installed app version and build, environment, device model, OS version, exact time, and whether the Apple sheet completed before progress stopped; the timestamp helps distinguish provider/server clock drift from other failures. Never send passwords, identity tokens, authorization codes, or screenshots containing them. That small bit of detail helps us answer with fewer back-and-forth messages.