Koordinato

What Koordinato can handle

Koordinato works above email, WhatsApp, forms, and existing systems: it organizes guest requests, prepares replies, drafts, quotes, follow-ups, and team involvement according to hotel-approved rules.

Operational control

Hotel rules become actions

Koordinato reads the request, evaluates what can happen inside the agreed scope, and involves the team when human control is needed. The first flow starts from real cases, clear rules, and planned team involvement.

Agreed scope

We define what it can handle, what it should only prepare, and what must always go to the team.

Human-in-the-loop when needed

Tone, content, exclusions, and team involvement rules are approved by the hotel before the flow goes live.

Koordinato works above the tools you already use, without forcing a PMS change.

Where systems are accessible

It can read availability, prices, rules, and useful data to prepare coherent replies or quotes.

Where systems are not yet connected

It can still gather context, prepare replies, and separate points to pass to the team without blocking the first flow.

Controlled scope

It does not promise instant integration with any PMS or blind autonomy: the first flow is decided together, with approved behaviour.

We do not promise immediate integration with any PMS or channel manager. We start from the first useful flow and decide together what to connect, what to prepare, and what to leave to the team.

First-flow capabilities

Informative replies

It understands what the guest is asking and can reply to repetitive questions inside the agreed scope.

  • Check-in, parking, breakfast, cancellations, pets, and accessibility
  • Replies aligned with approved tone and rules
  • Points that need a decision go to the team when data is missing or the case is ambiguous

Quote requests

When systems allow it, it prepares availability, options, and pricing to send or to complete with the team.

  • Reads dates, party size, and request constraints
  • Prepares the quote inside the agreed scope
  • Involves the team when human control or final confirmation is required

Room proposals

It can suggest rooms or options that fit specific needs when the rules are clear.

  • Families, pet friendly, accessibility, view, bed type, late check-in
  • Suggestions based on accessible rules and availability
  • No blind promises on cases that still need manual confirmation

Multiple requests in the same email

It reads multi-intent requests and separates what it can handle from what stays pending.

  • Availability, parking, pet friendly, and late check-in in the same thread
  • One unified context instead of scattered information
  • Sensitive points passed to the team with order and priority

Requires human review

When something is out of scope, it does not fail silently: it informs the guest and involves the team.

  • Ambiguous, sensitive, or not safely manageable cases
  • Clear guest message on what the team will complete
  • Human-in-the-loop active where it matters most

Operational summary

The team receives a summary of what was handled, what was prepared, and what still needs action.

  • Full context without rebuilding email, chats, and notes
  • Pending points already isolated
  • Less work scattered between channels and shifts

How it stays reliable

Controlled reply

No blind autonomy: public behaviour is defined and approved first.

On top of existing tools

Where systems are accessible it reads useful data; where they are not, it prepares and hands off to the team.

One real first flow

It starts from one high-value request type, not from a generic suite or an endless project.

Start from the request type that is actually worth handling first