Companion & communication
Inquiry router for your business
In the same inbox: a big-project inquiry with potential, a maintenance appointment, a "heating's broken, please come now!" and an applicant. Four completely different concerns – and all waiting for the boss to sort them in the evening.
Inquiry router / offer finder
01Inquiry router
The router sorts on the website, before it reaches the inbox: big project, repair, maintenance, callback request or application – two questions, and every concern is in the right place. The urgent repair gets the service number (with the tip to photograph the type plate – that saves the first call-out), the plannable project starts as an inquiry (with photos if useful), and the applicant lands on the careers page instead of the customer contact form. For you that means: your evenings go back to costing jobs instead of pre-sorting – and no good project sinks because it was stuck among the small stuff.
The router is the guide BEFORE the inquiry – it helps visitors find the right path. Fully preparing a project inquiry for the quote is a building block of its own (the project qualifier); together they're strong, each on its own works too.
02Demo
You're a visitor to the website of the fictional “Sailer Electrical” business. Instead of one contact form for everything: two questions. Try different paths through.
No magic: behind it is a switch – questions with clear branches. That's exactly why Tier 1 is so reliable: no AI that could guess. Only when visitors are meant to phrase things freely (Tier 2) does a language model classify the entry point – the switches stay.
Play a path through in the “try it out” tab – it lights up here.
03How it works
- 01
Sort out your paths
What actually reaches you – projects, repairs, maintenance, applications? Which paths exist today, what lands wrong, what sinks? Out of that comes the map the router guides on.
- 02
Find the questions that really separate
Usually two are enough: what's it about, and how urgent or how concrete? Phrased the way customers speak ("our roof's dripping") – not the way a form thinks.
- 03
Build the flow and embed it
The router becomes part of your website – as a guided flow in the business's presence, not as a foreign widget. Where visitors arrive: home page, services, references.
- 04
Wire up the endings
Every outcome leads somewhere: a project inquiry with photo upload, a service number for the urgent, a maintenance form for route planning, the careers page for applicants.
- 05
Watch and sharpen
After a few weeks it shows where visitors drop out or turn off differently than expected. Then we adjust questions and paths – the router gets better with real inquiries.
04Stages
The router is one of the most rewarding entry points there is: Tier 1 works entirely without AI and relieves the evening inbox right away.
Entry: the guided path
A rule-based flow with fixed questions and clear switches: project, repair, maintenance, application. Reliable, quickly built, immediately measurable.
Extended: it understands free text
Customers can just describe what's up – an AI places the concern and joins the flow at the right point. The switches behind it stay rule-based.
Full build: deeply wired
The router hands straight to your job and route planning, adapts the website to the concern and shows you a read-out of what visitors really look for.
05Technical implementation
- The router lives in your website – no external widget window, no foreign branding.
- Tier 1 is a decision tree: fixed questions, fixed switches. Unspectacular and that's exactly why it's reliable – even when the inquiry comes in at eleven at night.
- From Tier 2 a language model helps at the entry: it places freely worded concerns – the switches behind it stay rule-based and predictable.
- The data model behind it: your services, project types and inquiry paths as a clean structure – the same foundation the project qualifier later builds on.
- Handovers as needed: an inquiry form with photo upload, email, trade software or simply the right phone number.
- Built in your website's stack; Tier 2 adds a small back end.
for context · This shows how something like this usually gets built – not how it has to be built for you. What actually fits is worked out in the project: around your existing setup, your team, and what stays easy to maintain.