When someone fills out your sales form, you need to decide what happens next. Should they get a setup guide? Should you reply yourself? Should you ask one more question? Or are they not a good fit?
Here's how to build a simple lead-routing system to help with that decision.
The system will save each lead, suggest the best next step, and create a draft reply for you to review before sending.
You’re building a lead router. The first version is very small:
If a tool does not help with one of those steps, leave it out. Don’t add extra tools until leads are routed correctly.
Note: You should manually review and track conversions yourself until you know the system is accurate
This form is how new leads enter your triage system. They fill it out first. Later, you’ll send their answers to your Google Sheet.
You can share the form link anywhere you collect sales questions, such as your pricing page, contact page, help docs, onboarding emails, etc.
Add these fields:
Use dropdowns for fields that should be easy to sort.
For Role, use:
For Company size, use:
For Plan interest, use:
For Timeline, use:
For the main open question, use something like:
You now have a short form that gives you enough information to route the lead.
Next, create the Sheet that will hold your leads.
Add these columns:
Set these status options:
This is your lead board. Each row is one lead.
Most leads should get the short form. If someone is asking about a team plan or a larger team, add one more field. Something like: What team process are you trying to fix?
In Jotform, go to:
Show this field when:
Small leads get the short form. Bigger leads give you one more detail before they are routed.
Next, save each Jotform submission in Google Sheets. In Zapier, after the Jotform trigger, add:
Next, connect Jotform to Zapier.
Go to:
Zapier pulls in your test submission.
Now, add the AI step. This step reviews the lead details and selects the next step.
Paste this prompt (or similar):
You are routing inbound product leads for a solo founder.
Choose one route:
1. Self-serve guide
2. Founder reply
3. One qualifying question
4. Polite decline
Choose Self-serve guide when:
* The lead is simple and can likely start with a guide, docs, or a template.
Choose Founder reply when:
* The lead looks like a real business lead. For example: a team, agency, client work, operations, onboarding, support, reporting, sales, or Team/Enterprise interest.
Choose One qualifying question when:
* The lead is unclear.
Choose Polite decline when:
* The request is not a good fit.
Return only:
* Route:
* Reason:
Lead details:
* Role: [Role]
* Company size: [Company size]
* Use case: [Use case]
* Plan interest: [Plan interest]
* Timeline: [Timeline]
* Question: [Question]
Replace the bracketed items with the Jotform fields.
Click: Test action
Next, send the AI result back to Google Sheets. Use the same row that Zapier created in Step 4.
You can now see the suggested route inside your Sheet.
After the route is saved, ask AI to write the draft email.
Use this prompt (or similar):
Write a short email draft for this lead. Make sure the draft:
* Uses simple language
* Is under 100 words
* Makes no feature promises
* Does not offer discounts
* Does not make up product details
* Does not mention AI
Route: [Route]
Lead details:
* Name: [Name]
* Use case: [Use case]
* Team process: [Team process]
* Question: [Question]
Links:
* Setup guide: [link]
* Docs: [link]
* Calendar: [link]
Write the email based on the route:
* If the route is Self-serve guide, thank them and send the guide. Invite them to reply if they get stuck.
* If the route is Founder reply, mention what they want to do. Ask what they use now. Only add the calendar link if this is for a business.
* If the route is One qualifying question, ask if this is for a business workflow, client project, or personal project.
* If the route is Polite decline, say this is probably not the right fit. Share docs or another helpful link if you have one.
AI will now create a short email draft.
In the same Zap, add: Action → Gmail → Create Draft
Subject: Use one of these:
Set body: AI draft reply
Note: The Zap should create a draft, not send the email. At least for the first few weeks, you should review every draft before sending it.
Only follow up when it is worth your time. Here's an example setup:
If you have Zapier Paths in your plan, use them here.
Path 1: If Route contains Founder reply
Add this note:
Path 2: If Route contains One qualifying question
If you do not have Zapier Paths: Use separate Zaps or do this part manually.
Now, only the leads that need attention get follow-up tasks.
Do this part manually. Open Gmail drafts each morning. Before you send a draft:
Check the route
If there is a calendar link, review the draft twice.
This should also be done manually at first. When something happens, update the Sheet.
For Conversion result, use:
You can now see which routes are working.
The first version will not be perfect. Every Friday, open the Sheet and review the last 20 leads. Find one routing problem.
Maybe students are getting too much attention. Maybe agencies are not getting enough. Maybe some unclear leads need a better question.
Fix that one rule in the prompt. Leave the rest alone until the next week. You don't want to overhaul the whole system every week.
Do this every week. The router will get better over time.
solid, genuinely usable framework. two additions from running the outbound side of this:
dedup/suppression at intake — key your sheet on email (or domain) and, before the AI routes anything, check whether that person/company already exists (open lead, existing customer, or previously declined). otherwise you'll draft a fresh "nice to meet you" to someone your co-founder emailed last week, which is worse than staying quiet. a single QUERY/VLOOKUP against past rows handles it.
verify the email at intake — a chunk of form fills are typos or throwaway addresses, and catching those before the Gmail draft saves you writing careful replies that bounce.
the "update the same row" step is the one people skip, and it's the whole ballgame — the value only compounds if every touch writes back to one row so status and suppression stay true. what are you using to stop the same company coming in twice under different emails?
Great build. Lead routing is one of those operational problems that looks simple at first but becomes increasingly complex as teams, channels, and qualification rules grow. A simple no-code system can already create a huge improvement by making sure the right lead reaches the right person at the right time.
The next interesting layer is adding intelligence around prioritization — lead scoring, enrichment, response-time tracking, and automated follow-ups. The goal isn’t just moving leads around; it’s helping teams focus their energy on the opportunities most likely to convert.
This is a great example of how no-code automation can turn messy manual processes into repeatable systems. Excited to see how this evolves!
suggesting the next step is such a time saver - no more fretting over how to handle a new lead. thank you!