Confirm candidate details before a submission
Maito asks a candidate to confirm current details before submission and updates only what they confirm.
Operations · Recruiting and staffing · When something happens · Updated
Works with
- Slack
- Gmail
- Microsoft 365
- Superhuman Mail
Slack
Gmail
Microsoft 365
Superhuman MailHow do you confirm candidate details before a submission?
To confirm candidate details before a submission, tell Maito who is about to go to a client. It drafts an email to the candidate asking for current contact details, availability and consent, then updates your record from the reply. It leaves unconfirmed fields alone and flags anything unclear for you.
How it's done today
Recruiters submit candidates using availability and contact details that are a year old.
What Maito does
- Email the candidate a short confirmation form
- Read their reply
- Update only the fields they confirmed
- Keep the change history
Example
Loop run: Candidate added to role · Dev Patel
Dev Patel replied about the Wonka Foods Finance Analyst role. I updated these fields: • Phone: new number ending 4417 • Available from: Nov 16 (4 weeks' notice) • Work style: hybrid, previously remote only Not updated: salary. He didn't mention it, and the $78,000 on file was last confirmed 14 months ago. Permission to submit: he wrote "fine to share my CV," which I recorded as a reply, not as consent to this client. Catch: Wonka Foods wants an on-site day each week. Dev only said hybrid. From his email reply. Change history saved on the record.
@Maito Ask him about salary and permission for Wonka by name.
Draft ready: it asks for his current salary expectation and whether he agrees to be submitted to Wonka Foods, and notes the weekly on-site day. I'll send it once you approve.
Maito (9:40 AM):
Dev Patel replied about the Wonka Foods Finance Analyst role. I updated these fields:
• Phone: new number ending 4417
• Available from: Nov 16 (4 weeks' notice)
• Work style: hybrid, previously remote only
Not updated: salary. He didn't mention it, and the $78,000 on file was last confirmed 14 months ago. Permission to submit: he wrote "fine to share my CV," which I recorded as a reply, not as consent to this client.
Catch: Wonka Foods wants an on-site day each week. Dev only said hybrid.
From his email reply. Change history saved on the record.
Hana (9:46 AM):
Ask him about salary and permission for Wonka by name.
Maito (9:47 AM):
Draft ready: it asks for his current salary expectation and whether he agrees to be submitted to Wonka Foods, and notes the weekly on-site day. I'll send it once you approve.
How to set it up
- Ask your agent
“When a candidate last updated over 6 months ago is added to a role, email them to confirm phone, availability, salary and permission to submit. Update only what they confirm and post the changes in #recruiting.”
- Connect email
- Gmail
- Microsoft 365
- Superhuman Mail
- Use applicant tracker
- Greenhouse
- Ashby
- Workable
No MCP server needed. Ask your agent to save a skill with the steps, then add the login or API key in Settings → Vault.
- Use forms
- Typeform
- Tally
No MCP server needed. Ask your agent to save a skill with the steps, then add the login or API key in Settings → Vault.
Not connected yet? Your agent sends you a link to sign in.
What it won't do
It can't confirm what the candidate doesn't say. Salary and consent need a clear answer before you submit.
Questions
No. It updates only what the candidate confirmed and lists the rest as not updated.
No. It records the reply but asks for a specific yes to each client.
Email through Gmail, Microsoft 365 or Superhuman Mail. Greenhouse, Ashby, Workable and forms work through a skill.
