You automate candidate screening by putting a conversational agent in front of the job application. It asks what your intake form already asks, one question at a time, types the answers into a structured candidate record, and posts that record to your ATS the moment it is complete, with no score or decision attached.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone who just found your posting, usually at night or on a break, filling in a form between other things.
What it costs today
A static application form with no follow-up logic, or an ATS knockout question that forces a blunt yes or no where the real answer is "it depends."
What it has to produce
A typed candidate record: the role, what they do now, their relevant experience in their own words, and whether the must-have basics are there.
35%
of recruiters say back-and-forth scheduling coordination is the most time consuming part of their day
The Interview Guys
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the candidate record |
| phone | phone | Yes | How the recruiter calls back |
email | Yes | Where the follow-up lands | |
| role_applied_for | text | Yes | Which opening this is about |
| current_employer_or_status | text | Yes | Context for the recruiter |
| relevant_experience_summary | text | Yes | The pitch, in their own words |
| work_authorized_in_country | boolean | Yes | The one legal question, asked plainly and once |
| referral_source | text | — | Where the posting reached them |
| earliest_start_date | text | — | Timing a recruiter will confirm, never promised here |
And what it will not do
Collected data
287 collected24 this week5 need attention
Export CSVRenee Okafor
Captured 1h ago · Candidate Intake · joina.chat
Captured data 7 of 8 fields
From the conversation
“I’m at a logistics company right now, three years in, ready for something with more ownership , saw the ops coordinator role and it looked right.”
Every value keeps the sentence it came from, and a value the visitor never said is never stored. The chatbot cannot quote itself into your data.
From here a record can go straight on to Slack, a sheet, a Zap or your own API. The inbox is where you read them, not where they get stuck.
Signed headers
Body
{
"type": "data.collected",
"event_id": "1b6f9c02-4d1a-4f7e-9b3c-2a5e8d0f1c44",
"created_at": "2026-08-11T09:14:22Z",
"payload_version": "v1",
"data_kind": "New candidate",
"record_id": 1234,
"attributes": {
"full_name": "Renee Okafor",
"phone": "+1 415 555 0133",
"email": "renee.okafor@example.com",
"role_applied_for": "Operations Coordinator",
"current_employer_or_status": "Logistics company, 3 years",
"relevant_experience_summary": "Process background, led a team of four"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when someone corrects something.
Signed, so you can trust it
Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before it writes to a candidate record.
Quotes are opt-in
The provenance block, the candidate’s verbatim words, is absent unless you turn it on for that destination.
Zapier or Make
Paste a Catch Hook URL into your Gnosari destination, then point the Zap at your ATS or HRIS.
Free tier, no app to install, and it fires the moment the candidate record is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The recruiter sees the application before the ATS syncs.
Your own endpoint
Give us an https address, verify the signature, write the candidate record yourself.
A few lines of code, and the delivery log tells you when something did not land.
And you can see every attempt
| When | Event | Outcome | Detail |
|---|---|---|---|
| 08:14:02 | data.collected | Delivered | 200 OK |
| 08:13:58 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 17:41 | data.updated | Delivered | 200 OK |
| Yesterday 09:03 | data.collected | Delivered | 200 OK |
Every attempt is kept, newest first, with the reason when there is one. Failures retry on their own, and the signing secret lives in your dashboard so you can rotate it without calling anybody.
These are examples, not a partner list. Greenhouse, Lever, Workday, BambooHR and ADP are all reachable the same way: through a Zap, or straight to an endpoint you control. If it takes an HTTP request, it takes the candidate record.
A button in the corner that opens into a conversation. Your logo, your colours, sitting on the pages you already have.
No chat window and no widget. Your headline leads, the thread sits under it, and it reads like you asked rather than like software collecting.
Every screen on this page is a published Gnosari, embedded from the app. Type into any of them.
display_mode="bubble" A floating button in the corner. Opens over your page and closes again. The default, and the one nobody has to be taught.
Four corners to choose from
display_mode="sidebar" A fixed panel down one side, always open. For pages where the conversation is the point rather than an aside.
Left or right, any width
display_mode="sidebar-push" The same panel, but your content moves over to make room instead of being covered. Nothing on the page is ever hidden.
Left or right, any width
display_mode="drawer" Slides in over the page when it is called, then slides away. The middle ground between a bubble and a sidebar.
Left or right
01 · A link you send
Put it in an email, a text, a booking confirmation or a signature. Each link carries its own opening line and headline, and counts its own visits, so you can tell which channel actually worked.
02 · A code they scan
Every link comes with a QR. On a table card, a receipt, a delivery note, a door. Someone points a phone at it and the conversation starts, with no app and no typing.
03 · A flyer you hand over
A builder for the printed thing itself. Pick a template, restyle it, edit the words on the page and export a print-ready poster or card with the QR already placed.
Twelve curated looks, each a colour and a background pattern chosen to go together. Pick one and you are done.
22 colour themes and 44 background patterns, each drawn in code at four intensities. That is 3,872 combinations before you touch a single token.
22 colour themes
44 background patterns
Every pattern, four intensities
Exact hex values, fourteen fonts, bubble shape per side, corner radius, density, header and input. Explicit tokens always win over the preset. Two chats can share every line of markup and still wear two different brands: only the tokens differ.
A boutique hotel
A developer tool
fontFamily accepts fourteen faces
Set with one call, or one click in the designer. Changing it later takes the same one call, and every published surface updates at once.
| What changes | Static application form | ATS knockout questions | Gnosari |
|---|---|---|---|
| At 11pm on a Sunday | Saved half-done, if that | Same three yes or no questions | Answered, typed, delivered |
| What you get back | Whatever fit in the boxes | A pass or fail flag | The pitch, in their own words |
| Half-told story | Recruiter calls to ask | No follow-up possible | It asks the follow-up |
| Work authorization | Buried in a long form | One blunt yes or no, no context | Asked once, plainly, nothing more |
| Gets into your ATS | Re-typed by hand | CSV export, eventually | Signed webhook, the moment it is complete |
| The compliance line | Depends who wrote the form | Whatever the vendor built in | Never crossed, and stated at the start |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Name the fields your application already has, point the agent at your careers page and postings, and put the link or widget on your site. The agent runs the conversation, produces a typed candidate record, and posts it to your ATS through a webhook, Zapier or Make. Setup is minutes, not an implementation project.