Guest extra requests

Give every stay a little more possibility

Turn early arrivals, late departures and useful services into a clear guest offering, with prices, requests and fulfillment connected.

ChoiceServices worth discoveringLet guests browse your available extras.
ControlA decision for every requestCheck availability before making a promise.
Follow-throughFrom request to serviceKeep payment and fulfillment visible.
[ KEY FEATURES ]

Guest extra requests, with Sixto

Your offering

A small storefront inside the stay

Present the extras your team can deliver, with linked fees and unit eligibility. Guests discover them in the guest app.

  • Early check-in and late check-out
  • Airport pickup and other configured services
A considered yes

Welcome the request before making the promise

See the stay, requested time, travel details and price together before approving an extra.

  • Availability windows for arrival and departure extras
  • Approval requirements for your catalog
Service delivery

Keep the handoff attached to the request

Follow the extra’s decision, payment and linked fulfillment task without treating one as proof of the others.

  • Supported payment actions
  • Linked tasks where configured
[ HOW THE WORK SPLITS ]

What Sixto does, and what stays with you

What you can do in Sixto
Shows the enabled extras for eligible units
Keeps the request connected to its charge and task
You decide
Your service catalog and prices
Which requests to approve and who fulfills them
Inside the product
Late check-outStay until 14:00
01Done
Airport pickupArrival transfer
02Done
2 recorded items · 0 needing attention
[ ASK SIXTO ]

Ask in Spanish or English. Sixto answers and acts.

Ask about the product or bring the relevant record into the conversation. Available tools follow your permissions.

How do guests request an extra?Can an extra create a team task?
How do guests request an extra?
Guests select an available service from the guest app. Your team sees the request, checks availability and approves or declines it. Configured services can create a fulfillment task.
Late check-outRequested until 14:00COP 80,000
Departure windowAvailability determines approvalFor review
Explore the featureRead the guide
Ask Sixto anything…
Guest extra requests

Alex requests a later departure. The team checks the window, approves the request and follows payment and fulfillment separately, with the stay as the shared context.

Also included

A small storefront inside the stayPresent the extras your team can deliver, with linked fees and unit eligibility. Guests discover them in the guest app.
Welcome the request before making the promiseSee the stay, requested time, travel details and price together before approving an extra.
Keep the handoff attached to the requestFollow the extra’s decision, payment and linked fulfillment task without treating one as proof of the others.

Before you start

An extra is missing or cannot be charged.

Check its switch, unit availability and linked fee. Read the payment connection or permission blocker; do not promise collection while it is unresolved.

What should I verify?

Verify the request status, any charge and the fulfillment task separately.

What does not happen automatically?

Suggestions such as airport pickup are not automatically enabled. Approval and payment do not themselves complete the service.

More about Guest extra requests

Scope Sixto brings reservations, guest check-in, SIRE, TRA and DIAN invoicing workflows together for Colombian hospitality teams. Manage channel connections with Sixto, coordinate guest verification, compatible smart locks, cleaning, staff hours and finance. Reporting, invoicing and connected services require the relevant setup and permissions.

How it works, step by step

Guest extra requests

Manage early arrival, late departure, airport pickup and other services with explicit decisions and prices.

  1. Open the Extras catalog and enable services your team can deliver, with their fees, unit eligibility and approval requirements.
  2. Open a guest request and review the stay, service, price and relevant travel details before approving or declining it.
  3. Use the supported payment action when needed and follow any linked fulfillment task. Record the service outcome separately from payment.

The request has a recorded decision, with any linked charge and fulfillment task showing their own states.

Suggestions such as airport pickup are not automatically enabled. Approval and payment do not themselves complete the service.

Walk through the steps Open the guide (sign-in required)

Arrival and departure extras

Manage early arrival, late departure, airport pickup and other services with explicit decisions and prices.

  1. Open the early-check-in or late-check-out request and identify the requested time and affected stay.
  2. Check the available time window, unit eligibility, linked fee and approval requirement before deciding whether the team can provide it.
  3. Approve or decline the request through its supported action. Follow any required payment and fulfillment task without assuming approval changed booking dates.

The early-arrival or late-departure request records the requested time and approval decision; payment and fulfillment remain separately visible.

Suggestions such as airport pickup are not automatically enabled. Approval and payment do not themselves complete the service.

Walk through the steps Open the guide (sign-in required)