How Vectoris works

From an enquiry to a controlled workflow.

AI is used where language and unstructured details have to be understood. Routing, approvals, thresholds and system actions follow deterministic rules. The result is controlled AI automation: an operational workflow with a trace, not an autonomous system.

Architecture

Six layers, kept separate.

1 · Inputs

EmailWebsite formsMessagingCRM leads

2 · AI

IntentLanguageEntitiesSummaryStructured dataDraft reply

3 · Rules

Deterministic rulesRoutingApprovalsThresholdsBusiness logicEscalation

4 · Integrations

REST APIWebhooksPMSCRMBooking EngineSpa softwareRestaurant / POSEmail / Teams

5 · Control

Human approvalRolesAudit logRetriesFallbackError handlingMonitoring

6 · Pilot

AnalyseBlueprintBuildPilotOperate / rollout

Integrations depend on the interfaces that actually exist. APIs, webhooks and exports are verified technically before a connection is promised.

Layers

What each layer is responsible for.

Inputs

Keep the current channels

Email, forms, messaging and CRM leads stay where the property already works. The guest is not moved to a new portal.

Understand language

Intent classification, language detection, entity extraction, summaries and structured data. Draft replies are optional and are not sent automatically.

Rules

Fix the action

Deterministic rules set routing, thresholds, approvals, escalation and which business logic may run without discretion.

Integrations

Connect systems

REST APIs and webhooks first. PMS, CRM, booking engine, spa software, restaurant/POS, and email or Teams only with a verified interface.

Control

Keep operations safe

Human approval, role permissions, an audit log, retries, fallback, error handling and monitoring. Unclear cases go to a person.

Pilot

Start with a boundary

One process, one success measure, one fallback. A wider rollout comes after that.

Where AI stops

Not every action is an AI action.

AI recognises and structures. It does not confirm availability, and it does not write into a PMS unless that interface has been verified and approved.

Two massages, Saturday evening

AIRecognises the spa request and extracts party size, day and time of day.

RuleChecks completeness and assigns the case to the spa team.

HumanApproves availability or a binding commitment.

LogStatus, errors and the fallback stay traceable in the audit log.

Pilot

Analyse, blueprint, build, pilot, operate.

Analyse

Map volume, exceptions, systems and the hand-offs used today.

Blueprint

Define triggers, AI tasks, rules, targets, approvals and failure paths.

Build

Connect the channels, implement the rules and test real cases.

Pilot

Shadow mode or a tightly limited live run with human approval.

Operate

Monitoring, logs, adjustments and rollout to further workflows.

Contact

One workflow is enough for the first cut.

We review the process and the available interfaces before any scope is promised.