Qualification fields
- Meeting reason
- Work email
- Company size
- Urgency or priority
Semiora Intake
One link that qualifies, routes, and schedules — with explainability.
Intake is the “front door” to your scheduling system. It collects lead details, enriches context, routes to the right event type and host, then schedules the meeting. Every decision can be audited and simulated.
Slug URLs like /r/sales
Questions → rules
Territory round-robin
Analytics + simulator
The flow
1) Lead details
Name + email + a few qualifying answers.
2) Enrichment
Domain/company/region + CRM context (optional).
3) Assignment
Pick event type + host pool based on rules.
4) Schedule
Show times, book, and trigger workflows.
5) Sync
Write lifecycle updates to CRM (optional).
Direct answer
What is a booking intake form?
A booking intake form asks qualifying questions before someone books a meeting. Semiora uses the answers to choose the right calendar, event type, team queue, or round-robin host, so visitors reach the correct scheduling path without manual triage.
Routing Logic
Built for real teams, not just a single owner.
Semiora Intake routes a lead to the correct destination and keeps routing reliable even when owners are unavailable.
Territory pools + round robin
Assign within a pool for a region/segment. Semiora balances demand while still respecting availability.
Owner-aware fallback
If a CRM owner exists but is unavailable, Semiora can ignore the owner and route to the territory pool.
Multi-destination forms
A single intake URL can route to different event types based on answers (support vs sales vs enterprise).
Routing playbook
Planning the questions and rules before launch?
Start with a lean form, validate each rule in the simulator, and keep a fallback path for leads that do not match perfectly.
Read the routing forms guideBooking intake form examples
Qualify leads before they choose a calendar slot.
A scheduling intake form should ask enough to route the visitor without making booking feel heavy. Use answers such as service type, region, team size, urgency, or budget range to route leads to the right event type, owner, or round-robin pool.
Routing rules
- Route by service type
- Route by region
- Route by team queue
- Fallback when no rule matches
Booking outcome
- Show the right event type
- Assign the right host
- Send confirmation
- Trigger follow-up workflows
Example: a prospect selects “sales demo,” enters their region, and Semiora routes the booking to the correct territory pool. For a field-by-field checklist, read the booking intake form guide.
Enrichment
Enrich your routing with CRM context.
Intake can enrich answers using domain/company inference and CRM lookups so the right rep gets the lead the first time.
Plan tier + lifecycle stage attached to routing session.
Country/region enrichment supports territory assignment.
Salesforce real-time lookup during routing is available on Enterprise.
Compared to basic routing
Cleaner CRM, fewer misroutes.
Semiora is built to be operationally safe: idempotent CRM linking, explainable assignment, and fallbacks when ownership data is missing.
Booking lifecycle sync: created, cancelled, rescheduled (Pro/Enterprise).
Configurable mapping: Lead vs Contact + Event vs Task + field mapping.
Idempotency link keeps Salesforce updates consistent across retries and reschedules.
Plans
Limits and unlocks that match real usage.
Standard includes routing-specific limits. Teams unlocks analytics and version history. Enterprise unlocks real-time CRM lookup and advanced assignment strategies.
Standard
Core intake
Routing forms + rules
Pools + round robin
Slug URLs and publishing
Quotas: max forms, rules, pools
Teams
Ops visibility
Routing analytics
Version history + publish audit
Salesforce booking lifecycle sync
Intake lead sync
Enterprise
CRM-aware routing
Real-time Salesforce lookup during routing
ABM/VIP routing strategies
Territory strategies + owner fallback
Advanced reporting + governance
Want Intake on your site?
Use a single public link like /r/sales and route based on answers.
Related guides
Design better intake and routing flows
These guides explain what to ask, when to route, and how to connect qualified bookings to automation.
Guide
Booking intake form guide
Choose form fields that qualify visitors without adding unnecessary friction.
Read guideGuide
Routing forms that qualify and assign
Map intake answers to routing rules, teams, and fallback paths.
Read guideGuide
Booking webhooks and API automation guide
Send qualified booking events to CRMs, Slack, analytics, or internal tools.
Read guideGlossary
Related intake definitions
Use these definitions to connect intake forms with booking pages and downstream automation.
Compare
Compare intake and routing options
Use these comparisons when intake, lead qualification, routing, and booking handoffs matter more than a basic scheduling link.
Comparison
Calendly vs Semiora
Compare scheduling links with intake forms, team routing, reminders, and operational workflows.
Read comparisonComparison
Cal.com vs Semiora
Compare scheduling infrastructure with booking operations, intake, and workflow automation.
Read comparisonComparison
Acuity vs Semiora
Compare service appointment scheduling with qualification, routing, and webhook handoffs.
Read comparisonFrequently asked questions
What is a booking intake form?
A booking intake form collects visitor details before scheduling. Semiora uses those answers to qualify the visitor and route them to the correct event type, team, territory, or round-robin host pool.
How does Semiora routing qualification work?
Semiora checks form submissions against custom routing rules. Based on answers (like location or team size), it matches the lead to the correct event type and host pool.
What is territory round-robin?
It distributes incoming meetings evenly or weighted among sales or support team members assigned to a specific territory pool.
Can I simulate and audit routing decisions?
Yes. Our simulator tool allows operators to input test answers and verify which host or queue receives the booking before publishing changes.