Resume parse looks wrong

Quick answer: Improve parsing with structure, plain text, and PDF/A.

Tips

Use simple headings, avoid two-column layouts, save as PDF (not image).

Step-by-step checklist

• Confirm you are in the correct CosmoQuick surface: Candidate Dashboard, Recruiter Dashboard, ATS, Tools, or Settings
• Search the command palette for the feature name before browsing menus manually
• Open the relevant object (job post, candidate, application, invoice, or workspace) and check its status
• Make one change at a time, save, refresh, and verify the expected result
• If the issue still appears, capture the page URL, screenshot, browser, account email, and last action before contacting support

Practical example

A common real-world case: a user signs up as a candidate, then realizes they need recruiter features such as posting jobs, Resume Rank, MIRA, or candidate pipelines. First check Settings → Account for account type or dual-mode controls. If switching is not available for your plan or workspace, export any candidate data you need, then either contact support to convert the account safely or create a fresh recruiter account with the correct work email.

Screenshot placeholder

[Screenshot placeholder: show the exact CosmoQuick screen, highlighted button, empty/error state, and the expected success state. Keep sensitive candidate, salary, invoice, and contact information blurred before sharing.]

Troubleshooting guidance

• If a button is missing, check your account type, plan, workspace role, and whether the page is available only on recruiter or candidate mode
• If data looks stale, refresh the page, clear filters, and check whether you are viewing the right workspace or role
• If search returns nothing, try broader terms, remove hard filters, and search by skill, role, company, email, or candidate name
• If a payment, activation, import, or integration fails, retry once and then send the error text plus screenshot to support
• For urgent hiring blockers, use WhatsApp support from the Help Center

Pro tips

• Open a Private/Incognito window first — 60% of 'broken' issues are stale cache or a bad extension.
• Send a HAR file with every support ticket. It cuts resolution time roughly in half.
• Check status.cosmoquick.com before filing a ticket — known incidents are posted within 2 minutes.

Common pitfalls

• Disabling cookies/third-party storage — auth and CSRF protections require them.
• Using outdated browsers (anything older than ~2 years) leads to subtle UI bugs.
• Sharing screenshots without the URL bar — half of support tickets miss critical context.

Frequently asked

Where can I see system status?

status.cosmoquick.com — subscribe for incident emails, RSS, or Slack notifications.

Why am I getting logged out repeatedly?

Usually cookie/localStorage clearing extensions. Allow third-party cookies for cosmoquick.com or disable aggressive privacy extensions on our domain.

Why is the app slow on my network?

We're heavy on streaming/realtime — VPNs and corporate proxies can degrade websockets. Try direct connection to confirm.

Key takeaways

• Most CosmoQuick issues come from account type, workspace context, plan limits, filters, or incomplete setup
• Recruiter tools and candidate tools intentionally live in different dashboards to protect privacy and reduce confusion
• The fastest fix is usually: verify mode → clear filters → inspect status → search docs → escalate with context
• Keep this article open while performing the steps so you can compare the expected and actual state

Next steps

• Browse all categories for related guides
• Open the Help Center home to keep exploring
• Still stuck? Contact our team — average reply under 4 hours on weekdays