Guided intake and routing before the user commits to a long form.
The assistant route exists to classify the issue, clarify urgency, and point the user toward the right service path, quote route, or immediate call.
Task-oriented AI structure
The assistant should classify issues, suggest services, and route people toward quote or upload actions.
Interactive routing
Turn a rough problem into the next best step.
Choose the issue, urgency, and context. The route now checks the backend recommendation layer first, then falls back locally if the API is not available.
Home, condo, apartment, or household comfort issue.
You need direction first, or you are not ready to upload media yet.
AI assistant entry
Guide users toward the right next step.
The assistant is positioned as a practical router for issue review, service selection, and quote direction, not as a generic chatbot.
Start with a short problem statement, then move the visitor into the cleanest next action instead of forcing a full form too early.
Assistant question stack
What the assistant should collect first
Keep the question short, practical, and easy to answer on mobile without turning the route into another long form.
Keep the question short, practical, and easy to answer on mobile without turning the route into another long form.
Keep the question short, practical, and easy to answer on mobile without turning the route into another long form.
Keep the question short, practical, and easy to answer on mobile without turning the route into another long form.
Keep the question short, practical, and easy to answer on mobile without turning the route into another long form.
Keep the question short, practical, and easy to answer on mobile without turning the route into another long form.
Assistant result routing
Three example outcomes the assistant should produce
Route to AC repair, collect photos, and offer urgent call if the issue is active now.
Escalate to business-priority refrigeration intake and encourage immediate human follow-up.
Guide the user into repair-versus-replacement logic and then toward the quote route.
Good for unclear issues. Not for trapping urgent users.
The route should help with classification and routing, while keeping the direct human fallback obvious.
Best fit
- When the visitor is unsure which service route fits best.
- When repair-versus-replacement needs a cleaner starting point.
- When commercial refrigeration issues need structured triage before the full intake.
- When a user wants direction before sending media or committing to a longer quote flow.
Call first instead
- If cooling loss is active now and the situation cannot wait.
- If business downtime is creating immediate product or operations risk.
- If the visitor already knows they need human follow-up now.
- If a quick phone handoff is faster than any guided route.
Urgent users should still have a direct human option.
The assistant should never feel like a wall between the visitor and the next real step.
The routing layer is useful when the issue is unclear, when the user is deciding between repair and replacement, or when a business needs help choosing the right intake path.