Companion & communication
Inquiry router for your business
All in the same inbox: a promising inquiry for a big project, a maintenance appointment, a "heating's broken, please come now!" and a job application. Four different requests – all waiting for the boss to sort them out in the evening.
You'll get …
- 1
A pre-sorted inbox
Project, repair, maintenance or application: every request is sorted before it reaches the inbox.
- 2
Project inquiries you can quote from
Projects that can be planned arrive with the key facts and photos – good jobs no longer get lost among the small stuff.
- 3
Emergencies by phone, applicants on the right page
Breakdowns get the service number, applicants the careers page instead of the customer contact form.
01Intro
The router sorts them on the website, before anything reaches the inbox: big project, repair, maintenance, callback request or application – two questions, and every request is in the right place. Urgent repairs get the service number, projects that can be planned start as an inquiry with photos, and applicants go to the careers page. For you, that means your evenings go back to pricing jobs instead of pre-sorting emails.
The router is the signpost BEFORE the inquiry – it helps visitors find the right path. Preparing a project inquiry properly for the quote is a separate building block (the project qualifier). The two work well together, but each also works on its own.
02How it works
- 01
Map your paths
What comes in – projects, repairs, maintenance, applications? Which paths exist today, what ends up in the wrong place, what gets lost? That gives us the map the router works from.
- 02
Find the deciding questions
Two are usually enough: what's it about, and how urgent or how far along is it? Worded the way customers talk ("our roof's leaking") – not the way a form thinks.
- 03
Build the flow and embed it
The router becomes part of your website – a guided flow in your company's look, not a third-party widget. It sits where visitors arrive: home page, services, past projects.
- 04
Connect the end points
Every outcome leads somewhere: a project inquiry with photo upload, a service number for emergencies, a maintenance form for route planning, the careers page for applicants.
- 05
Observe and refine
After a few weeks you can see where visitors drop out or take a different turn than expected. We then adjust the questions and paths – the router improves with real inquiries.
03Stages
The router is one of the most rewarding places to start. Tier 1 needs no AI at all and takes pressure off your evening inbox straight away.
Starter: the guided path
A rule-based flow with fixed questions and clear branches: project, repair, maintenance, application. Reliable, quick to build, measurable from day one.
Next step: it understands free text
Customers can just describe the problem – an AI works out what they need and drops them into the flow at the right point. The branching behind it stays rule-based.
Full build: deeply connected
The router passes inquiries straight to your job and route planning, adapts the website to what the visitor needs and shows you in a report what visitors are looking for.
04Try it yourself
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.
05Technical implementation
- The router lives on your website – no external widget window, no third-party branding.
- Tier 1 is a decision tree: fixed questions, fixed branches. Unexciting, which is why it's reliable – even when the inquiry comes in at eleven at night.
- From Tier 2, a language model helps at the start: it interprets requests in the customer's own words – the branching behind it stays rule-based and predictable.
- The underlying data model: your services, project types and inquiry paths in a clean structure – the same foundation the project qualifier can build on later.
- Handovers as needed: an inquiry form with photo upload, email, trade software or just the right phone number.
- Built on your website's existing 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.