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.
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).
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).
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. Pro 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
Pro
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.
Frequently asked questions
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.