← use cases

Prepare sales enquiries for a person

Collect the need and the missing details before your team starts a sales conversation.

The template gallery includes a sales lead starting point.
The template gallery includes a sales lead starting point.

Product screen with sample data. Intake is the previous working name.

The incoming request

“We need a system for three service teams and want to host it ourselves.”

A useful intake process helps a salesperson understand the need. It should ask for relevant details and keep unusual enquiries available for review.

Define a good fit

Start from the Sales lead template. Replace its criteria with the service your company provides.

Describe the request types your team can help with. Do not use a vague “good lead” criterion without clear examples of what it means.

Ask for missing context

Choose follow-up questions that help a person continue the conversation. These can cover the intended use, the deployment needs, or a target date.

Use a written question when the person needs room to explain. Use a choice when the options are clear and complete.

Keep review available

Use a human handoff for an unclear fit or a request outside the listed options. A person can recognize an opportunity your examples do not cover.

ClientStack records the decision and summary. Sending an email or creating a CRM record needs your team’s process or an integration.

Test with varied enquiries

Include short, detailed, vague, and out-of-scope examples. Compare the actual outcomes with what the sales team expected.

Read Jev questions and examples and replay.

Put this into practice. Build your first request type →

Give every request
a clear next step.

Start with one request type. Make it yours.

Find an answer

Try “publish”, “API”, or “human handoff”.