Companion & communication

Inquiry router / offer finder

Someone lands on your website and wants something from you. Only what exactly – and where does it go? One contact form for everything doesn't answer that.

Inquiry router / offer finder

01Intro

The router asks the two or three questions that make the difference: what's it about? How urgent? For whom? After that the visitor isn't facing five menu items but exactly one next step. A table reservation goes straight into the booking tool, an event inquiry brings the date and party size along right away, and whoever has just a quick question gets a quick answer. For you that means: fewer calls that are really a booking, and fewer emails missing half the information.

The router is the guide BEFORE the inquiry – it helps visitors find the right path. Fully preparing an inquiry for the team is a building block of its own (the inquiry qualifier); together they're strong, each on its own works too.

02Demo

simulation · fictional inn

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.

03How it works

  1. 01

    Sort out your paths

    We look at what actually reaches you: which concerns there are, which paths exist for them, where inquiries land wrong today. Out of that comes the map the router guides on.

  2. 02

    Find the questions that really separate

    Usually two or three are enough. The art isn't asking a lot – it's asking the right thing. We phrase the questions the way your customers speak, not the way a form thinks.

  3. 03

    Build the flow and embed it

    The router becomes part of your website – as a guided flow, a chat or a mix. It fits into the design instead of popping up as a foreign body.

  4. 04

    Wire up the endings

    Every outcome leads somewhere: into the booking tool, into a fitting short form, to a detail page or to the phone.

  5. 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 visitors.

04Stages

The router is one of the most rewarding entry points there is: Tier 1 works entirely without AI and still brings noticeable relief right away.

Tier 1

Entry: the guided path

A rule-based flow with fixed questions and clear switches. Reliable, quickly built, immediately measurable – no AI at all.

Tier 2

Extended: it understands free text

Visitors can just start writing ("we're 25 people looking for something for Juli's birthday…") – an AI places the concern and joins the flow at the right point.

Tier 3

Full build: deeply wired

The router hands straight to the reservation system or CRM, adapts the website to the recognised concern and gives 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. It sounds unspectacular and that's exactly why it's reliable.
  • From Tier 2 a language model helps at the entry: it places freely worded concerns – the switches behind it stay rule-based and therefore predictable.
  • The data model behind it: your offers, inquiry paths and criteria as a clean structure – the same foundation a website companion can later build on.
  • Handovers as needed: booking tool, email, Airtable, CRM (e.g. HubSpot, Pipedrive) – or simply the right form.
  • 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.

06Related building blocks

See all use cases