WilboYour three choices
Wilbomail
Wilbo uses your @wilbomail.com address on the application. When an authenticated employer message with one clear code matches an active application challenge, the code can be passed to that same application session. If the challenge finishes successfully, the spent code message is consumed rather than delivered to your inbox. If the challenge expires or is released, the held message forwards normally.
This is the default for existing alias holders. If an employer’s verification step cannot continue automatically, Wilbo will stop and ask you to enter the code instead of guessing or reusing it.
Gmail forwarding
Wilbo uses your verified account email on the application. You create a narrow filter in Gmail that forwards job-site verification messages to a dedicated Wilbomail intake address. Wilbo does not ask for Gmail OAuth permission, use the Gmail API, read the rest of your inbox, or run a general inbox crawl.
Connection has two stages: Gmail first sends a forwarding confirmation, then Wilbo waits to observe one real matching verification message. The method is not shown as ready until both setup and that real forwarding check have completed.
Manual
Wilbo uses your verified account email on the application and waits when the employer sends a code. You read the code in your inbox and enter it into the active application prompt yourself. The code is accepted only for your own current manual challenge.
Set up the Gmail option
- Choose Gmail in your email-code settings and start the connection. Wilbo creates a dedicated intake address for your account.
- In Gmail, open Settings → See all settings → Forwarding and POP/IMAP, add that intake address, and complete Gmail’s confirmation step shown by Wilbo.
- Create a narrow Gmail filter for application verification messages and forward only those matches. Do not enable blanket forwarding of your inbox.
- Use the test or wait for a real job-site verification message. Wilbo marks Gmail ready only after a matching forwarded message has actually arrived.
What is stored
Gmail forwarding confirmation is reduced to the code or link metadata needed by the signed-in owner. The raw confirmation message is removed after it is consumed. Application code handling is scoped to an active owner challenge and uses sender authentication and unambiguous code matching before a code can be delivered to the application.
No Gmail message body is put into Wilbo account records, application logs, or an AI-writing pipeline by this connection. See the Privacy Policy for the formal disclosure.
Troubleshooting
- Gmail says pending confirmation. Return to Wilbo’s email-code settings and use the exact confirmation code or link displayed for your account.
- Gmail is confirmed but Wilbo says not ready. A real message matching the narrow filter has not been observed yet. Check that forwarding is enabled for that filter and that it targets the dedicated intake address.
- The wrong mail is being forwarded. Disable the filter in Gmail, narrow its sender or subject conditions, and reconnect if needed.
- An application is waiting. Keep the same application/browser session open. If automatic handling cannot continue, switch to manual entry or follow the prompt shown for that run.
- You disconnected Gmail. The dedicated intake is disabled. Your Gmail account itself remains under your control; remove the old forwarding rule there too.
