Most screening calls begin with questions the form was supposed to answer. Then a candidate writes “6” under CTC, and the call starts with a translation.
A job application asks for the facts a recruiter needs before a conversation: the role, years of experience, current and expected pay, notice period, location, and somewhere to see the candidate’s work. The fields are not complicated. The answers are.
A plain form stores what was typed. A form with scripted logic routes on it. ConvoForm’s job-application use case takes a third approach: when an answer is too thin for the field’s description, it can ask a follow-up written for that answer. CTC is the cleanest place to see the difference, because “6” is an entirely normal thing for a candidate to type.
This is a product example, not a customer story. It uses the same six fields and the same scenario that render the job-application use-case page, and the data on both pages is illustrative.
At a glance
- A branch selects a path you wrote before the form was shared.
- A follow-up is generated for the answer that just arrived, scoped to a field you configured.
- The saved CTC answer goes from “6” to ₹6 LPA current and ₹8 LPA expected.
A branch is a decision made without the answer
Screening logic is usually a script. If the candidate needs visa sponsorship, show these questions. If they cannot relocate, stop. If the role is sales, ask about quota. Every condition is written before the first application arrives, because whoever builds the form has to decide what every possible answer means.
That is the right shape for closed questions. Work authorization, shift availability, a required licence, or a fixed salary band can all be exact. A branch can prove that every candidate who answered “no” saw the same follow-up. For consistency and compliance, that is a real advantage.
Free-text answers break the assumption that the options are known. CTC is the obvious one: a number without a unit, a period, or a distinction between current and expected pay. Notice period is close behind. “Soon” could mean two weeks, a month, or already serving notice. “3-4” years of experience is a range, not a figure.
You can write branches for all of these. But each branch needs a condition, and each condition needs an answer format you predicted. The long tail — “6 fixed, 8 variable”, “₹6.5L”, “current 6, expecting 8-9”, “negotiable for the right role” — is where branches get expensive and the answers get flattened.
A branch can choose a question. It cannot ask what the answer meant.
A follow-up starts from the field’s description
In ConvoForm, a field is more than a label. The CTC field in the job-application form is described as “Current and expected CTC, in LPA”. That description is what the follow-up works from, together with the answer and the conversation so far.
For the answer “6”, the follow-up can ask whether 6 is the current CTC or the expected one. The candidate replies “current. expecting 8”, and the answer saved for the recruiter becomes ₹6 LPA current and ₹8 LPA expected. The follow-up did not invent a salary. It asked the candidate to be precise about the one they had already given.
The same mechanism applies to experience ranges and vague notice periods. “3-4” can produce a question about which end is closer. “Soon” can produce a question about whether notice is being served and when the last working day is. Each follow-up is composed for that answer, not selected from a list of pre-approved sentences.
This is also the part that takes getting used to. You no longer know the exact wording every candidate will see. You do know which fields they will be asked about, and you can read the transcript afterward to see what was asked and what was saved.
The mechanics are covered in the form-creation docs.
The field stays fixed. The question in the middle can change.
The same six fields, and the answer “6”
The example below imports the fields and the scenario from the job-application use-case content, so the article and the product page cannot drift into two different stories.
Each field carries the detail a recruiter needs, and the example column shows what a usable answer looks like once the detail is there.
The opening they're applying for
Which role are you applying for?
e.g. Frontend Developer
Total and relevant experience, in years
How many years of experience do you have, and in what?
e.g. 3-4 → "Closer to 3 or 4?" → 4 yrs (React)
Current and expected CTC, in LPA
What's your current CTC, and what are you expecting?
e.g. 6 → "Is ₹6 LPA your current CTC, or what you're expecting?" → ₹6 LPA → ₹8 LPA
Days, "Immediate", or last working day if already serving notice
What's your notice period?
e.g. soon → "Are you serving notice now? If so, what's your last working day?" → Immediate
Current city, and whether they can relocate or come on-site
Where are you based, and can you work from Bengaluru?
e.g. Pune, open to Bengaluru
LinkedIn, portfolio or GitHub
Share your LinkedIn or a link to your work.
e.g. LinkedIn + GitHub
Illustrative example
The static form saves the answer exactly as typed: “6”. The conversational form asks whether that is current or expected CTC. The candidate answers “current. expecting 8”, and the recruiter sees ₹6 LPA current and ₹8 LPA expected before the call.
No branch was written for the answer “6”. The follow-up was generated against the CTC field’s description and the conversation so far.
What a follow-up is not
A follow-up makes an answer clearer. It does not turn a job application into an assessment. These boundaries matter before you put a form in front of candidates.
It is not a shortlisting tool
ConvoForm does not score, rank, compare, shortlist, or reject candidates. It collects and clarifies the fields you configured; a person still decides who moves forward.
It is not a background check
A clarified CTC, notice period, or experience figure is still what the candidate said. Nothing is verified against payslips, offer letters, or references.
It is not an interview
The follow-up is scoped to the current field. It does not assess motivation, culture fit, or communication style, and it does not hold an open conversation.
It is not a CV reader
Candidates can attach a CV for a recruiter to open, but ConvoForm does not parse or read it. The answer you review comes from the conversation you configured.
It is not your ATS
Answers can be exported to CSV or sent to Google Sheets. There is no direct ATS integration today, and ConvoForm does not schedule interviews or message candidates.
It is not deterministic
The same unclear answer can produce different follow-up wording on different runs. Read the conversation before acting on an important detail.
Limitations, stated plainly
The point of a follow-up is a clearer answer, not a more impressive demo. These are the limits a hiring team should know before using one in a live application.
Follow-ups are not verification
Salary, notice period, experience, and work authorization are claims until you check them. A clarified answer is easier to discuss, not proof that it is true.
The AI can misread a candidate
A follow-up may accept an answer that is still vague, or ask for a detail that misses the point. Reviewing the conversation is part of the workflow, not an optional extra.
Wording varies between runs
Two candidates can get different sentences for the same kind of answer. If a question must be identical for every applicant, use a fixed question or a scripted branch.
Field descriptions set the ceiling
The model works inside what you describe. “Current and expected CTC, in LPA” gives it something to check; “CTC” does not. The quality of the field definition still matters.
Hiring rules still apply
A generated follow-up does not replace your policies on equal opportunity, candidate consent, data retention, or anything else your process requires. You remain responsible for the questions you ask.
A recruiter still decides
ConvoForm gives the first call a better starting point. Your team reviews the answers, verifies what matters, and makes every hiring decision.
When a scripted branch is still the right tool
Branching and follow-ups are not competing answers to the same question. They are different answers to different questions.
Keep a scripted branch when…
- The answers are a closed set: authorization, shifts, licences, fixed salary bands.
- Every candidate must see the same question in the same order.
- The routing affects eligibility, consent, or a legal requirement.
- You need to audit every path before the form goes live.
Use a generated follow-up when…
- The answer is free text with many partial, informal versions.
- The missing detail depends on what the candidate already said.
- You want clarification, not a detour to another question.
- A recruiter reads the conversation before deciding the next step.
A screening form can use both. Branch where the answer must be exact. Follow up where the answer needs to be understood. The mistake is expecting a generated follow-up to behave like a branch — it will not ask the same question every time, and it will not make the decision for you.
See the screening form this article describes
The job-application use-case page walks through the same six fields, the same CTC follow-up, and what ConvoForm does not do today. The demo lets you try a conversational form before you create one.
Read the docs for form creation and field descriptions, or try the live demo on the homepage. Prefer to build? Create a screening form, share it with the role, and test a few unclear answers before candidates arrive.
The one-line version
“A branch routes the answer. A follow-up asks what it means.”