(After hours)

Explore booking support for the hours your team is away.

Guests enquire before opening and after close. Try Amira's browser booking demo, then review what an after-hours connection would require for your restaurant.

Try the live demo
(The gap)

Bookings don't wait for opening time.

Most booking calls are ordinary: a date, a time, a party size. What makes them hard is when they arrive.

(01)

Before opening

Morning calls about tonight or the weekend, before anyone is on the floor to answer them.

(02)

During the rush

The host is seating a table and the phone keeps ringing behind them.

(03)

After close

Late calls from guests planning tomorrow, while the team is closing up or already home.

(Try the workflow)

What you can try in the browser demo.

Bookings use the sample restaurant's configured tables and times. Review your venue's requirements and test the full conversation before guest use.

(01)

Books the tables that are free

In the demo, Amira checks configured table capacities, dining time and booking start times. If a time is full, she can offer available alternatives. The booking is saved before confirmation. How availability is checked.

(02)

Takes private-event bookings

A party big enough for your private room is checked against the room and booked into it. Menu and deposit details become a follow-up for your team. Nothing is sent to the guest automatically.

(03)

Moves and cancels bookings

Guests can change the time or party size, or cancel, on the call. If the new time is full, the original booking stays.

(04)

Leaves the rest for your team

A request that needs a person can be saved with a summary, booking context and any available contact details. Your team handles the follow-up; saving a request does not mean the guest has been contacted.

Example calls, a different guest each time
(Next morning)

Your team picks up where Amira left off.

The host workspace shows saved bookings and requests, with unowned and overdue requests first. Try that workflow before planning overnight coverage.

(01)

Claim it

A host takes a request under their own name and sets when they'll follow up.

(02)

Close it with a note

A request can't be resolved without a note, so the next shift knows what happened.

(03)

Reopen it if things change

Reopen a request with a reason. The history stays with it.

(Your hours)

Agree which calls a future connection would cover.

These are proposed routing options. A restaurant telephone connection is not live yet; each option needs carrier and connection testing.

(01)

After hours

A proposed routing window to agree and test with your carrier and team.

(02)

Missed calls

A possible setup where your team answers first, subject to carrier support and a tested fallback.

(03)

Every call

A broader routing option that needs connection, capacity and fallback tests before it can be enabled.

(Questions)

Asked about after-hours cover.

Does Onla answer at three in the morning?

You can try Amira in the browser now. After-hours telephone coverage is a proposed setup: your exact carrier, connection, capacity and staff fallback must be qualified before guest calls are routed to Onla.

Can guests book a time when we're closed?

No. Amira books only the start times you set for your venue. If a guest asks for a time outside them, she offers the free times that exist.

What if a caller hangs up halfway through booking?

Nothing is held until the booking is saved. If the guest hangs up before that, the table stays free for the next caller.

Does this replace our host?

No. The proposed setup supports calls your team cannot take. Greeting guests, sorting out a seating problem and making exceptions stay with your team.

Do we need a new phone number?

Keeping your number is the planned approach. We need to qualify your exact carrier and phone setup, then test the connection and staff fallback before agreeing a go-live date.

What does it cost?

One monthly plan per venue, with no setup fee, and you can cancel any month. The price is agreed on the walkthrough call.