Forms that turn into work.
One builder for website leads, applicant screening, signatures and onboarding. Every submission lands as work in the same system, and the Recruiter reads the screening answers.
What comes in
Two people fill in a form while you're asleep.
A family looking for care and a caregiver looking for work. Both land in the system your office already works in.
The family who found you at 3 a.m.
A Nestaid form embedded on your own website. The submission becomes a lead on the same record the phone call would have made, so the morning starts with a lead, not an inbox.
- Embed on the site you already have
- Honeypot and rate limiting on every public form
- Lands as a lead, not an attachment
The caregiver who applied on a Saturday
The Recruiter sends your application form, analyzes the answers against your screening questions, and moves the candidate along the pipeline before Monday.
- Your screening questions, your wording
- Answers analyzed, not filed
- applied → screened → interview → offer → onboarding
Why it isn't a form
In Nestaid, a form is an intake, not an email.
In Nestaid
A form that only emails you
The submission becomes a lead, on the same record as the call
An email in an inbox somebody opens on Monday
Screening answers read against your questions before anyone opens them
An attachment nobody parses
The Recruiter screens the applicant and moves the pipeline
A spreadsheet of applicants you sort by hand
E-sign flows and onboarding steps from the same builder
A separate e-signature subscription
Six field types and a wide layout, built by you
A developer ticket and a two-week wait
Honeypot and rate limiting on anything public
Spam landing beside the families
Built into the engine, the same for people and agents
Public forms are protected · Honeypot and rate limiting, always on.
Never makes the decision · It screens and ranks. You hire.
One audit log · Submissions and reads land on the same trail.
Uploads stay behind auth · No signed URLs for uploaded documents.
Who reads what comes in
A submission nobody had to open.
The Recruiter sends and analyzes screening forms.
The Recruiter never makes an offer, and never hires. It screens, it books, and the decision stays with you.
- Application submittedAnswers analyzed
- Against your questionsScreened, pipeline moved
- InterviewBooked inside your hours
How do website forms work in Nestaid?
A form built in Nestaid can be embedded on your website; each submission becomes a lead in Nestaid, protected by a honeypot and rate limiting. The same builder produces applicant screening forms, e-sign flows and onboarding steps, so a family inquiry and a caregiver application land in one system.
Frequently asked questions
Can I use forms on my existing website?
Yes. Website-enabled forms can be embedded on any site; submissions become leads in Nestaid.
Is this just a form builder?
No. A form in Nestaid is an intake. A submission becomes a lead, a screened applicant, a signature or an onboarding task in the same system your office already works in, and the Recruiter analyzes screening answers rather than filing them.
What can I build with it?
Website lead forms, applicant screening forms, e-sign flows and onboarding steps, from one builder with six field types and a wide layout.
