Booking automation with clear human boundaries.
Finnor is built to recover missed, overflow, after-hours, and slow web leads while keeping decisions, judgment, and escalation ownership with the service company.
Operating boundary
Human team owns next steps
Boundary 01
Human teams stay in control
FINNOR quotes ranges computed from your pricing tiers and real public water data, and books the visit. People remain responsible for final figures, repair decisions, ETAs, dispatch, and customer promises.
Boundary 02
The agent never invents numbers or diagnoses
Quote ranges come only from the pricing you configured and the measured water data on record. FINNOR does not diagnose repairs, invent prices, guarantee ETAs, or make health claims about water.
Boundary 03
Urgent language routes to human escalation path
Companies define the escalation path for urgent or concerning language. Finnor flags that language and routes it according to the approved process.
Boundary 04
Company-approved scripts and knowledge boundaries
Pilot scripts, booking questions, and knowledge boundaries are approved before use so the system stays within the company's operating model.
Boundary 05
Public-info-only demo builder
The personalized demo builder uses public website information and user-provided inputs. It is not a production deployment or a claim about private systems.
Boundary 06
Unknown fields stay marked unknown
If a caller does not provide a field, the route should show that it is unknown rather than inventing or assuming an answer.
Boundary 07
Data minimization during pilots
Pilots should use only the information needed to test booking paths, urgent routing, escalation, and follow-up workflow.
Boundary 08
Scoped deployment before production
Finnor is intended to start with a defined routing scope, reviewed scripts, test scenarios, and clear human ownership before broader use.
What Finnor does not replace
The company remains the decision-maker.
Deployment note
Production scope depends on the final routing, systems, and agreements.
Production readiness depends on final routing, data handling, vendor agreements, access controls, retention settings, escalation procedures, and the company's own policies. Finnor scopes those decisions before launch.
Conservative operating principle
Quote only from configured pricing and measured water data, book the next step, route urgent language, and leave final figures, dispatch decisions, repair judgment, ETAs, and promises to the human team.