What Segmentation Intelligence Does with a Submission
Why the questions you ask decide how well everything after works
What It Is
Filing answers into fields is the mechanical part of a submission. The more consequential part is that Zyntro reads the submission as a whole and works out what it means.
Segmentation Intelligence — SI — is the part of Zyntro that decides what should happen next with a relationship. It can only decide well on somebody it understands, and a form submission is one of the richest things it ever gets: somebody voluntarily telling you about their situation, in their own words.
How It Works
A written profile
From the answers, Zyntro produces a profile record on the contact containing a summary of who this person appears to be, the problems they seem to have, what they appear to want, and angles likely to resonate with them.
This is not a copy of the answers. It is an interpretation of them, written so that later decisions — what to say in an email, what a voice agent should raise on a call — have something to work from beyond a name and a job title.
A readable note
Answers you mapped to Contact Notes or Profile Data are gathered into a note on the contact, in readable prose rather than as raw field values. This is what a person reads before picking up the phone.
Signals
Where the answers indicate something meaningful about intent or readiness, Zyntro records a signal against the contact. Signals accumulate across every channel, not just forms.
Pipeline movement
A strong enough signal can move the contact to a later pipeline stage, and that movement itself fires a trigger, so workflows watching for stage changes pick it up.
Visibility to SI depends on publishing
A form must be Published for SI to see it. While a form is Draft, SI cannot reference it, and nor can connected AI agents or intelligence-generated email, SMS and broadcasts. The form still works and still collects submissions — it is simply invisible to the intelligence layer.
Why It Matters
Your form design sets the ceiling. SI cannot infer from what was never asked. Three questions produce a thin profile; eight well-chosen ones produce something genuinely useful. This is the argument for asking one or two open questions even on a short form — free text is where people tell you things you did not think to ask about.
Where you map an answer changes what it is good for, not whether SI sees it. SI reads the whole submission regardless. Mapping decides whether you can filter on an answer. Both matter, for different reasons.
Zyntro fills gaps by inference. Where a field exists but was not asked about, it will work out a plausible value from the rest of the answers. That makes records more complete and means a field can hold an inference rather than a statement. For anything you will act on commercially, ask the question.
Examples
A form asking only for name and email
SI gets identity and nothing else. Follow-up can be timely and correctly addressed, but it cannot be relevant, because nothing has been said about what this person needs.
The same form plus "What are you trying to solve?"
One open question changes the picture. SI now has the problem in the person's own words, which is what makes a follow-up email read as a reply rather than a broadcast.
A consultative form with scales and open questions
Structured answers you can segment on, plus free text to reason over. The profile is detailed enough that an outbound call can open by referencing the specific thing they said, which is the difference between a conversation and a cold call.
A Draft form collecting real submissions
Contacts are created and answers are filed, but SI cannot see the form. Nothing SI drives will reference it. Publishing is what connects it to the intelligence layer.
Tip: If you only add one thing to a short form, add a single open question. What are you hoping to solve? costs you very little in completions and gives SI more than any number of dropdowns.