Fields you define
Add the fields that matter to your funnel and mark which are required. There is no fixed schema to bend your business around.
FeatureQualification
A lead you can act on, not a chat transcript.
You decide what a real lead looks like — a budget, a city, a product, a date. The agent asks for those in the flow of the conversation, records them against the contact, and only then decides whether a human is worth interrupting.
- Custom data fields per agent, in the words your team uses
- Asked conversationally, not as a form the customer abandons
- Routing rules decide which leads reach a person, and when
No credit card requiredIncluded on every plan
Leads · 30d612
Fully qualified71%
Avg. fields captured4.2
Budget rangeRequired fieldOn
CityRequired fieldOn
Product interestRequired fieldOn
Purchase timelineOptional fieldOn
What it does
The part that matters in practice.
Asked, not demanded
Questions arrive when they make sense in the conversation. A customer who volunteers their budget is not asked for it again.
Escalation on your rule
A lead with the required fields and real intent reaches your team. The rest keep being handled without anyone's time.
How it works
Underneath the feature.
Everything here runs on the material you upload and the instructions you write — and stops the moment a conversation needs a person.
Attached to the contact
Captured values live on the contact record, not buried in the transcript, so they can be filtered, exported and pushed onward.
Filled in over time
A lead that gives you two fields today and two more next week ends up complete. The record updates rather than duplicating.
Straight into your CRM
Qualified leads can be pushed to Kylas CRM as the conversation happens, so sales works from one list instead of screenshots.
WhatsApp
Instagram
Messenger
Website chatGetting started
Four steps, no implementation project.
List what you need
Write down the fields a rep asks before they call a lead back.
Add them as data fields
Name each one, mark it required or optional, and describe what a good answer looks like.
Set the handoff rule
Decide which combination of fields and intent is worth paging a person for.
Send them onward
Connect Kylas CRM or the leads API so qualified records leave the inbox automatically.
FAQ
Lead Qualification, in detail.
What if a customer refuses to answer?
The agent keeps helping. Qualification is not a gate — an unanswered field is recorded as missing, and your routing rule decides whether the lead still reaches a person.
Can different agents capture different fields?
Yes. Fields are defined per agent, so a real-estate agent asking for locality and possession date and a clinic agent asking for symptoms and slot preference can run in the same account.
Where do captured leads end up?
On the contact record inside Rush, and wherever you route them — Kylas CRM as the conversation happens, or your own system through the leads API.
Can I export the leads?
Yes. Contacts and their captured fields can be filtered in the workspace and exported, and the leads API exposes the same records programmatically.
More features
It does not work alone.
Get started
Try it on your own conversations.
Connect a channel, upload what you already send customers, and see how much of your inbox this handles before anyone on your team picks up.