Capabilities

Four ways a call can go.

Verified path by path in the code that runs it, on 1 September 2026. Nothing on this page is planned or coming soon.

Schematic of a live call: TALON on the line with four outcome cards beside the handset.
On the phone — schematic
Live
  1. The caller

    Hi, do you have a table for four on Saturday evening?

  2. TALON

    Good evening. I am an assistant, not a person. Saturday at 8:30 pm I have a table for four: shall I confirm it?

  3. The caller

    Yes, under Rossi.

  4. TALON

    Done: Saturday, 8:30 pm, four people. The confirmation is on its way to your email.

What it did

It answers on your number
A real number, activated from the console. TALON answers, says it is an assistant, and speaks the caller’s language among the five it knows.
It books while talking
It offers only slots that are free — covers and overlaps counted — and writes the booking in the same transaction that checks it.
It leaves a full record
Summary, transcript, the data it collected, the outcome and how the call scored against your criteria — and the recording, playable in the console.
Live
  1. The caller

    It’s Bianchi, I booked with you last week.

  2. TALON

    Welcome back. I see Tuesday’s booking: the same time, on Thursday?

  3. The caller

    Thursday is fine.

  4. TALON

    Thursday at 7 pm is free: confirmed.

What it did

It recognises who calls back
A caller who already booked or already called is known: name, last booking and last summary are at hand during the call.
It books while talking
It offers only slots that are free — covers and overlaps counted — and writes the booking in the same transaction that checks it.
It leaves a full record
Summary, transcript, the data it collected, the outcome and how the call scored against your criteria — and the recording, playable in the console.
Live
  1. The caller

    I wanted to know if you deliver at home.

  2. TALON

    I don’t have that information. I’ll take a message and someone will call you back.

  3. The caller

    Fine, by tomorrow please.

Urgency: mediumWaiting for your acknowledgement

What it did

It takes the message when it should
When there is nothing to answer with, it takes a message: transcribed, flagged low, medium or high urgency, waiting for your acknowledgement.
It leaves a full record
Summary, transcript, the data it collected, the outcome and how the call scored against your criteria — and the recording, playable in the console.
Missed call

  1. 12:41 — the call could not be answered.

  2. SMS sent from your number

    We couldn’t pick up. You can book from here: your booking link

What it did

It texts back a missed call
A call it cannot take gets an SMS with your booking link. Needs SMS switched on for the number.
Three written channels side by side: email, messaging and site chat, each with a draft frame.
Written paths — schematic

One request, three written channels.

The same message can arrive by email, on messaging or from the chat on your site. Switch channel, then decide how much it may do on its own.

Customer

Good morning, is there room for four on Saturday evening? Around half past eight.

TALON’s draft

Good morning! Saturday evening there is a table for four at these times. Which one shall I hold for you?

8:30 pm 9:00 pm Real slots, read from the calendar when the draft is written.
It sends on its own
Autonomy on this channel
It sends on its own

Sent. The conversation goes on without you and stays on the record.

Connect the mailbox you already use — OAuth or IMAP. TALON skips spam and auto-replies, spots booking intent and drafts answers with real slots already in them.

Customer

Good morning, is there room for four on Saturday evening? Around half past eight.

TALON’s draft

Good morning! Saturday evening there is a table for four at these times. Which one shall I hold for you?

8:30 pm 9:00 pm Real slots, read from the calendar when the draft is written.
It sends on its own
Autonomy on this channel
It sends on its own

Sent. The conversation goes on without you and stays on the record.

Scan a QR code from the business phone and the channel is on — no separate business account. Drafts there follow the same rules and the same approvals.

Customer

Good morning, is there room for four on Saturday evening? Around half past eight.

TALON’s draft

Good morning! Saturday evening there is a table for four at these times. Which one shall I hold for you?

8:30 pm 9:00 pm Real slots, read from the calendar when the draft is written.
Chat on your site
Autonomy on this channel

In the chat it answers straight away, from your knowledge base, and says it is an assistant.

One script tag, your colour, your assistant’s name. It answers from your knowledge base and says it is an assistant, on every visit.

On every written channel

It answers from your own articles
Every channel draws on the knowledge base you write. What it quotes is the summary you give each article — your words, not its guesses.
Tickets, when a reply is not enough
A helpdesk underneath: kanban, canned responses, SLA timers with escalation, satisfaction surveys and ticket analytics.
Manners built in
One-click unsubscribe on commercial sends, a suppression list it never writes to, and rate limits on every public surface.
Booking timeline with five beats from write to follow-up.
Booking — from minute zero

A booking, from the first minute to the day after.

Move along the timeline. Every step is something TALON does on its own once the booking is written.

Before the first booking

Services, your way
Duration, buffers, booking window, auto-confirm, price, capacity per slot, and custom questions the guest answers while booking.
A public page under your name
One page per service, with your logo and your colour, and an anti-bot check on every booking.

Written

Written in the same transaction that checked the slot: capacity per slot and overlaps counted, whether it came from the phone, an email or the public page.

Confirmed

An email the moment the booking is written. From that link the guest moves or cancels on their own, without calling back.

The day before

A reminder email goes out on its own.

One hour before

A text message, where SMS is switched on for the number.

Fifteen minutes after

If nobody showed up, the booking is marked a no-show on its own, fifteen minutes after the slot ends. No list to go through by hand.

The follow-up

A no-show or a completed visit can start a sequence you designed — email, SMS, waits and conditions.

Growth router: four inbound lines converging on one agent, then out.
Growth — who answers what

More than one agent, and the numbers to read.

Each inbound line goes to the agent you choose, with its own persona, hours, autonomy, knowledge scope and budget. Pick one to see where it lands.

Routed to

Front desk

Hours
24/7
Autonomy
Answers and books on its own
Knowledge scope
Opening hours, services, bookings
Monthly cap
€ 40 Spend tracked per agent
Routed to

Sales

Hours
Mon–Fri, 9 to 18
Autonomy
Drafts wait for approval
Knowledge scope
Price list and quotes
Monthly cap
€ 120 Spend tracked per agent
Routed to

Sales

Hours
Mon–Fri, 9 to 18
Autonomy
Drafts wait for approval
Knowledge scope
Price list and quotes
Monthly cap
€ 120 Spend tracked per agent
Routed to

Front desk

Hours
24/7
Autonomy
Answers and books on its own
Knowledge scope
Opening hours, services, bookings
Monthly cap
€ 40 Spend tracked per agent

The autonomy matrix, the approvals queue and the two budget thresholds are shown further down, in Control. Control

And to grow on

Leads with a score
Every inbound email can become a lead, scored 0–100 on source, engagement, fit, recency and tone, on a kanban from new to won.
Sequences
Email, SMS, waits and conditions, started by a new lead, a no-show or a completed visit. They go out in working hours; outside them they wait.
An API with a spec
A public REST API with an OpenAPI document and self-service keys — tickets, bookings, leads, articles, conversations. Webhooks and team-chat notifications for the events you pick.
Numbers you can read
Calls answered, answer rate, bookings made by the AI and the revenue they represent, month to date. Ticket analytics with SLA compliance and agent performance.

Verified path by path in the code that runs it, on 1 September 2026. Nothing on this page is planned or coming soon.

The telephone, SMS reminders, the lead pipeline and sequences depend on the plan. Everything else is in every plan.

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