Something went wrong. Let’s fix it.
Start with the symptom that matches — including the ones where Jobsistant is refusing to do something on purpose.
A real person reads this. Replies usually within two business days, India time.
Stuck part-way through an application right now? Say so in the subject line and it gets looked at first.
Five things that are working correctly even when they look broken.
These are not settings, and no plan changes them. If what you are seeing is one of these, nothing has gone wrong.
It never submits
There is no submit action anywhere in the product. Every application is sent by you, after you have read it.
It never invents
Generated text may only use facts from your profile or the job description. A claim with no source behind it is blocked rather than smoothed over.
It never guesses silently
Anything uncertain is marked for you instead of filled quietly. An empty field is honest; a plausible wrong one is not.
It never touches secrets
Passwords, CAPTCHA responses, payment details and government ID numbers are excluded on the page, before anything is sent.
Your data stays yours
Export it or delete it from settings whenever you like, without asking us first.
Jobsistant did not appear on an application
Almost always the access model working as designed. Jobsistant recognises 21 applicant-tracking domains on its own; everywhere else, an employer’s own careers site included, it stays switched off until you open it for that tab.
Nothing happens on a company’s own careers page
That is expected until you open Jobsistant for that tab. Click the Jobsistant icon in the Chrome toolbar while the application page is in front. That grants access to that one tab, for as long as you are working in it, and the panel opens ready to read the form.
The 21 domains Jobsistant recognises automatically are the large applicant-tracking systems — Greenhouse, Lever, Ashby, Workday, iCIMS, SmartRecruiters, Workable and the rest. A great many applications are hosted on employer-owned domains instead, which is exactly why the toolbar click exists rather than blanket access to every website you visit.
If you would rather not click each time, the panel offers “Allow on all sites” when it cannot read a page. That grants permission; it does not make Jobsistant activate on its own. Automatic detection stays limited to the 21 domains either way, and ordinary browsing pages are still never read.
I accepted the first-run notice and it still will not start
Jobsistant reads nothing until that disclosure is accepted, and the acceptance is stored in extension storage. If the panel showed “Could not save your choice”, storage was unavailable — privacy extensions and managed-browser policies can block it.
Open chrome://extensions, reload Jobsistant, and accept once more. If your browser is managed by an employer or school, extension storage may be restricted by policy, which is not something the extension can work around.
The panel is blank or stuck on “Getting this page ready…”
Reload the application page, then open the panel again from the toolbar icon. Application forms are frequently rendered inside nested frames that the page replaces as you move between steps, and a reload puts the panel and the form back in step.
If it survives a reload, that is worth reporting — include the site and the step of the form you were on.
Jobsistant filled a field incorrectly
The report we most want to receive. An empty field costs you thirty seconds; a wrong one goes out under your name, which is why we treat it as the most serious bug class in the product.
What do I do right now?
Correct the field in the form and carry on. Nothing has been sent: Jobsistant has no code path that submits an application, so whatever is on screen is still entirely yours to change.
Correct it in the Jobsistant panel too. That is what teaches it the right value, so the same field is right on the next application rather than wrong again.
Then tell us, with the report builder below. Name the applicant-tracking system, the label on the field as it appears on screen, and what was filled instead of what you expected.
Why did it get it wrong in the first place?
Usually one of three things: two different questions share a label that looks identical out of context, an employer has customised a standard field to mean something else, or a fact in your profile is out of date and was filled faithfully.
The third is worth checking first, because you can fix it in a minute — open your profile and look at the fact behind the field. Jobsistant also asks you to re-confirm facts that go stale, such as notice period or expected salary, rather than filling an old answer silently forever.
Could it have submitted the application before I saw the mistake?
No. Jobsistant contains no submit action at all — not as a setting, not as a shortcut, not for paying accounts. The check that keeps it that way runs in the build, so a change that introduced one would fail before it could ship.
Every application is submitted by you, on purpose, after you have looked at it.
Jobsistant left fields empty
Three different things look identical on screen: a hard rule, an honest judgement call, and a real gap in coverage. Here is how to tell them apart.
It skipped a password, CAPTCHA, payment or ID field
That is a hard rule. Jobsistant does not read, store or fill passwords, CAPTCHA responses, payment details or government identity numbers such as national insurance, social security or passport numbers. These are filtered out on the page, before anything is sent anywhere.
There is no setting that enables it and no plan that unlocks it. If you need one of those fields completed, type it yourself.
The gender, disability, veteran or race questions were left blank
Voluntary self-identification is left for you by default. Jobsistant never infers these answers from a document or a name, and it only fills them if you have explicitly opted in for that category — each one separately, and reversible with one click at any time.
Leaving them for you is the default because a wrong guess on these questions is not a typo.
A field was marked instead of filled
Jobsistant marks what it is not confident about rather than guessing quietly. An empty field you can see is honest; a plausible wrong answer you did not notice is not.
Fill it in yourself and it is saved for next time, so the same question is answered from your own words on the next application.
It skipped an ordinary field it should have known
If the fact is in your profile and the field is a normal one — a phone number, a start date, a link — then it is a gap in our field coverage, and reporting it is how it gets closed.
The useful details are: which applicant-tracking system, the exact label shown next to the field, and what you would have expected it to fill.
Generated answers
Answers come from two sources and nothing else: your Super Context, and the job description in front of you. Most surprises here are that constraint doing its job.
A draft was blocked, or came back thinner than I expected
A draft is held back when it would state something that is not in your profile or the posting. The missing piece is almost always a fact we simply do not have — the scale of a project, a date, a tool you used, a result you achieved.
Add it to your profile and generate again. Retrying without adding anything produces the same outcome by design: the alternative is a sentence that reads well and is not true, going out under your name.
This is not a quality dial and it does not change with your plan. Paying buys more of the same work, never a looser standard.
The wording does not sound like me
Edit it. The edited version is what gets saved, so the next application starts from your wording rather than ours, and the drafting controls — shorter, longer, regenerate, or a specific instruction — are there to steer it before you commit.
Generation is slow or times out
Reading the posting takes longest the first time you open a given application; afterwards it is reused. If a draft times out, try once more before reporting it.
Repeated failures on the same application are worth a report — send the applicant-tracking system and roughly when it happened, so it can be matched against the logs.
Account, and connecting the extension
The extension and the dashboard are connected by a revocable token issued to your account. Most sign-in trouble is that connection rather than the account itself.
The panel is asking me to connect an account
Open the dashboard and pair from there; the panel picks the connection up without a copy-and-paste. If pairing does not complete — a blocked pop-up, a managed browser — the panel’s “Have a token? Paste it instead” route does the same job by hand.
Connections are listed in your dashboard settings and can be revoked individually, which is also how you disconnect a shared or old computer.
I keep getting signed out of the extension
Revoking a token, signing out of the dashboard, or clearing extension storage all end the connection, and it has to be paired again.
Hitting a daily limit is not one of the causes. Running out of Smart Applies leaves you signed in — if you were signed out at the same moment, they are two separate problems and both are worth mentioning in a report.
I have not received the verification email
Check the spam folder first, and confirm the address you typed is the one you can actually open. If it is still missing after a few minutes, email us from the address you signed up with and we will sort it out directly.
I want to export or delete my data
Both are yours to run from the dashboard, without asking us: export everything Jobsistant holds about you, or delete the account and its contents.
The privacy policy sets out what is held, for how long, and what deletion covers.
Uploads, parsing and documents
Your profile is built from documents you upload. When an upload misbehaves, it is usually the file rather than the account.
My resume upload was rejected
Profile uploads are PDFs of up to 10 MiB. A scanned or photographed resume is an image rather than text, and there is nothing in it to read — if that is what you have, the quickest fix is to export a fresh PDF from the document you wrote it in.
There is also a daily cap on uploads, which exists because parsing is the most expensive thing an account can trigger. A normal day of one or two resumes will never reach it.
My resume was parsed into the wrong details
Correct them in your profile — the corrected version is what Jobsistant fills from, and the original upload stops mattering the moment you do.
Unusual layouts are the usual cause: multi-column designs, text inside images, and tables used for spacing all read differently to a parser than they do to you. If a section came out badly mangled, send us the layout description and we will use it to improve the parser.
A tailored document did not attach to the form
Some application sites will not accept a file placed by anything other than their own picker. Where that happens, download the document from the panel and attach it with the site’s upload button — the document is yours either way.
Limits, plans and payments
Free covers the repetition; Pro adds the writing. What follows is the part people actually write in about — the rest is on the pricing page.
When does my free daily Smart Apply come back?
At midnight in your own timezone, not ours. The reset is calculated against the timezone on your account, so “tomorrow” means your tomorrow.
If the reset time looks wrong, the timezone on the account is probably wrong. It can be changed once every seven days.
Filling fields Jobsistant already knows, and reusing answers you have written before, are not metered at all. The daily grant covers the AI writing on a new application.
I hit a limit and it looked like I was signed out
Reaching a limit never signs you out, and the two are handled separately on purpose. If you genuinely lost the connection at the same time, report it — that combination is a bug, not a policy.
I want a refund, or to cancel
The terms of sale set out what is refundable and how to cancel, including who the seller of record is and where the charge on your statement comes from.
If you do not recognise a charge, write to us before raising a chargeback. It is faster, and we can see what happened.
What happens to my data when Pro ends?
Your profile, your saved answers and the documents you already generated stay yours and stay available. Ending Pro stops new document generation and returns Smart Apply to the daily grant; it does not take away what you have already built.
Privacy and security
The short version is below. The full statements are the authoritative ones, and they are written to be read rather than clicked past.
What does Jobsistant actually read from a page?
While you have it open on an application: the labels, field types and option text of the form, the structure around them, the job description, and the address of the application itself. That is what makes matching a field to one of your facts possible.
It does not read ordinary browsing pages in the background, whatever permissions have been granted. Permission to act and the decision to act are deliberately separate.
Is my information used to train an AI model?
Not by us. Your content is not sold, not used for advertising, and not used to train a Jobsistant-owned model. AI providers process the content needed for a feature you asked for, and nothing beyond that.
I found a security vulnerability
Please report it to us directly rather than publicly, and give us a reasonable window to fix it. The security page sets out how we handle disclosure and what you can expect back.
Send a report worth reading
The difference between a fix today and a fix after four emails is usually three missing facts. Pick what happened and this lays them out.
The most serious bug class in this product. These are read first.
Nothing here is sent from this page. You copy it and send it yourself.
What we cannot do for you
Worth saying plainly rather than two days later by email. Where there is something genuinely useful to read instead, it is linked.
Un-submit or edit an application you have already sent
Once an employer’s site has it, only the employer can change or withdraw it. What you can do depends on the system it was submitted through.
What is possible after submittingTell you why an employer rejected you
We have no visibility into any employer’s decisions, and neither does any other tool that claims otherwise.
Why applications go quietConfirm that an employer received your application
The signals that do mean something — a confirmation page, a portal record, a receipt email — come from the employer’s system, not from us.
How to tell whether it went throughContact an employer or recruiter on your behalf
Jobsistant helps you fill the form. Everything sent to an employer is sent by you, in your name.
Apply to jobs automatically while you sleep
This is not a missing feature, it is the opposite of the product. Applications you have not read are the thing employers are filtering against.
Autofill versus auto-apply
What happens after you write
Your email goes to one inbox, read by the people who build Jobsistant. Nobody looks inside your profile, your documents or your answers to investigate a problem unless you specifically ask us to and say so — if we need something from your account to make progress, we will ask you first and tell you what for.
A wrong fill or a missed field becomes a test case against the real page it happened on, which is what stops it happening to the next person. If your report changes the product, we will tell you when it ships.