Companion & communication
Inquiry router / service finder
Someone lands on your website and wants something from you. But what – and where should it go? A single contact form for everything can't answer that.
You'll get …
- 1
A clear path for every request
Instead of one contact form for everything, visitors see a clear next step.
- 2
Fewer inquiries via the wrong channel
Fewer phone calls that should have been bookings, and fewer emails with half the details missing.
- 3
Every request ends up in the right place
In the booking tool, the right short form, on a detail page or on the phone – connected to the tools you already use.
01Intro
The router asks the two or three questions that matter: What's it about? How urgent is it? Who is it for? Then the visitor sees one clear next step instead of five menu items. For you, that means fewer phone calls that should have been bookings, and fewer emails with half the details missing.
The router is the signpost BEFORE the inquiry – it helps visitors find the right path. Preparing an inquiry properly for your team is a separate building block (the inquiry qualifier). The two work well together, but each also works on its own.
02How it works
- 01
Map your paths
We look at what comes in: what kinds of request you get, which paths exist for them and where inquiries end up in the wrong place today. That gives us the map the router works from.
- 02
Find the deciding questions
Two or three are usually enough. The skill lies in asking the right thing. We word the questions the way your customers talk, not the way a form thinks.
- 03
Build the flow and embed it
The router becomes part of your website – as a guided flow, a chat or a mix of both. It fits your design instead of popping up like something bolted on.
- 04
Connect the end points
Every outcome leads somewhere: to the booking tool, the right short form, a detail page or the phone.
- 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 visitors.
03Stages
The router is one of the most rewarding places to start. Tier 1 needs no AI at all, yet it takes noticeable pressure off straight away.
Starter: the guided path
A rule-based flow with fixed questions and clear branches. Reliable, quick to build, measurable from day one – no AI involved.
Next step: it understands free text
Visitors can just start typing ("there are 25 of us and we're looking for something for Juli's birthday…") – an AI works out what they want and drops them into the flow at the right point.
Full build: deeply connected
The router passes inquiries straight to your reservation system or CRM, adapts the website to what the visitor is after and shows you what visitors are looking for.
04Try it yourself
You're a visitor to the website of the “Zur Linde” inn. 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. It sounds unexciting, which is why it's reliable.
- From Tier 2, a language model helps at the start: it interprets requests in the visitor's own words – the branching behind it stays rule-based and therefore predictable.
- The underlying data model: your services, inquiry paths and criteria in a clean structure – the same foundation a website companion can build on later.
- Handovers as needed: booking tool, email, Airtable, CRM (e.g. HubSpot, Pipedrive) – or just the right form.
- 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.