Autofill vs auto-apply
Two different things with similar names: one fills forms and leaves them for you, the other submits. Which plan has which, and the limits on both.
The two words look like one feature and are two, with different plans behind them and different promises.
| Autofill | Auto-apply | |
|---|---|---|
| What runs | The queue opens each job, prepares it and fills the form | The same, and then submits |
| Who presses send | You, once per job | Nobody. You find out afterwards |
| Plan | The apply tier and above | Pro Max only |
| Consent | Starting the run | A separate tick for the sending mode |
| Where it can run | Boards with a form adapter | Boards that accept a direct submission |
A third thing shares the name and is neither: the extension's fill button, which works on the one page you are looking at.
Why they are separate
Because collapsing them is how somebody who paid for forms to be filled discovers the product also sent them. Filling is a robot that opens twenty tabs and types in them, and you are still the one pressing send twenty times. Sending is a robot that presses send.
The difference is priced, and it is also a separate permission internally, so a refusal can name which of the two was refused.
The limits
Counted per day and per calendar month, per kind, on the server rather than in your browser.
| Tier | Sent for you | Filled for you |
|---|---|---|
| Pro Max | 20 a day, 250 a month | 25 a day, 300 a month |
| Scan, Build and Apply | Not included | 15 a day, 200 a month |
| Everything below | Not included | Not included |
The daily number is the one that binds in practice. It is set by what a board plausibly tolerates rather than by what the margin allows.
What a run actually does
- You paste job addresses, or let the ranking pick the best by match score up to what today allows.
- Each job gets a route and a reason, printed before anything opens.
- A resume is built per kind of role rather than one per job.
- Each job is opened in a real tab and prepared.
- In sending mode, submittable boards are submitted. Everywhere else, the form is filled and the tab is left open.
- Twenty to forty-five seconds pass, and the next one starts.
- Everything lands on the tracker, including the ones that did not go.
The honest parts
- A bot check stops the run on any board. That is reported as not sent, with the tab left open for you to finish.
- The application allowance is spent when the application is customised, not at submit. So you cannot get a tailored application without being counted, and you cannot be counted and get nothing.
- Nothing is skipped silently. A job that quietly did not get applied to is indistinguishable, from your side, from one that did.
What it will never reach
Roughly three quarters of the index cannot be submitted to by anybody, because the employer does not accept applications that way. LinkedIn is refused outright, since automating it risks your own account, and boards that need employer-issued credentials are excluded as well.
Which board falls where is in which boards support which route.
Questions about this
Which one does the toolbar button use?
Neither. The button on a job page fills the page you are on and stops. The queue is the thing with two modes.
Can I run the sending mode on my apply tier plan?
No. Filling a queue comes with the apply tier; sending without you present is Pro Max only, and a campus licence excludes it as well.
What happens if a board challenges the run?
It stops on that job, the tab is left open for you to finish by hand, and the run is recorded as not sent rather than as sent.
Why are jobs worked so slowly?
Twenty to forty-five seconds apart, randomised. Forty submissions from one address inside an hour is the fastest way to get a board to start quietly binning everything from that candidate.
Pick the mode before you pick the jobs
The queue screen prints the route and the reason for each job before anything opens. Read that list once and the difference stops being abstract.
Open Involve Resume