The call

What happens when it rings.

A booking taken over the phone is a chain of small decisions. Here is the order they happen in — and the point where TALON stops deciding.

Four-step call diagram ending in a hand-back stamp for your decision.
The call — four moves
Schematic map: a caller reaches TALON, which checks the calendar and your rules, then either acts or asks you.
The route — schematic, not a mockup

  1. It picks up, and says what it is

    Your number rings and TALON answers, introducing itself as an assistant. That disclosure is built into the product, not a setting you remember to switch on.

  2. It checks before it promises

    Availability comes from your calendar, covers and overlaps included. What it offers is what is actually free — and when it writes the booking, it checks once more inside the same transaction.

  3. It confirms, and keeps confirming

    The guest gets an email with a manage link at once, a reminder the day before, a text an hour before where SMS is on. Moving the booking is self-service; not showing up is recorded on its own.

  4. When it shouldn’t decide, it doesn’t

    Nothing in your data to answer with? It takes a message — transcribed, with an urgency level — instead of improvising. On the written channels every reply queues for your approval; on the phone it acts in real time and leaves you the full record.

The autonomy is yours to set: which actions are forbidden, which need your approval, which run on their own. Whatever you choose, every action is logged with its cost.

TALON is one of ours.

It shares its identity layer, its AI gateway and its European footprint with the rest of the Altovar catalogue. One supplier, one place to ask, one jurisdiction.

Talk to the teamThe Altovar catalogue