Skip to main content
Guests use one private reservation link to register, read property instructions, request services, and contact your team. Configure a reusable portal, then manage each guest’s registration and payments from their reservation. Background checks are no longer available in the Guest Portal. Older screening rules do not appear or run and do not block registration or access. Identity verification and other required rules continue to apply. The Guides catalog follows these rules too: guide names and descriptions, and place names and descriptions, translate automatically after saving. Each editor has the language dropdown and preserves manual translations. Addresses, links, phone numbers, and photos stay unchanged. New portals start in the workspace language. Editing portal or registration text in that language automatically generates translations for the other enabled languages in the background. You do not need to request translation or wait before publishing. While a translation is pending, guests see the source text. The language dropdown sits inside the guest preview. Select a language to preview and edit its text. Editing a field in another language creates a manual override for that field and language. Later source edits preserve it while regenerating the other translations. A small globe at the block’s top-right marks an override in the selected language, with the tooltip “Manually translated, will not generate.” Services and property Access guides follow the same translation rules. They open in the workspace language and translate saved text automatically in the background, including service titles, descriptions, guest questions, and guide titles, descriptions, and photo captions. Use the flag and language-name dropdown to preview or edit another language. Editing a translated field protects that field from regeneration; the small globe is visible only in the editor. Saving does not require generating or reviewing translations.
Use Preview for the guest view. Settings groups general settings, appearance, registration, access, guides, services, chat, contacts, and reviews. Click Preview again to open the phase and device options. Settings closes these options. Expand Simulate to choose a property and channel, or Use a reservation to select a stay. Change the language inside the guest preview. The history menu offers Use this version. Publishing asks for confirmation only for critical changes, with a list of changes and affected reservations. Registration forms remain under Reservations > Rules.Settings are independent of the preview property, channel, and phase. Changes save automatically, including appearance and the portal hostname. Expand the chevron to configure DNS or PMS link sync inline. Upload a logo in Appearance and a concierge photo in Chat; both show a preview. Expand Introduction to edit longer text. In Guides, the circles control phase visibility. Click a guide’s row to show or hide it; the open icon opens its editor in the Trellis sidebar. Enable cart sits above the services list.Chat visibility is controlled separately for each phase. Choose the AI agent, display name, photo, and contact shortcuts below it. Concierge by property contains scenario cards: properties on the left, the agent on the right. Add a scenario or remove it with the trash icon. The portal’s separate reply-delay override is below Photo. Revision history shows the revision number, status, relative time, and the person who saved it; older revisions without attribution show Unknown. Only connected PMS providers appear in Settings, each under Sync with [PMS]. Expand Sync with Guesty to configure its portal link and reservation field mappings. Registration contains a searchable rule picker: select rules to add them to this portal, or deselect them to remove them. Open a rule from the picker to edit it. Guest verification is in the Check-in form settings. Arrival and departure time windows are in the check-in form rule and apply to all forms in its registration profile. The portal publication recap applies the reviewed requirements to existing guests. It shows reservations in order of impact, with a warning first for guests whose access will be blocked again; there is no additional checkbox. In portal Settings > Services, presentation scenarios choose which services guests see. Omitted conditions match any value; different conditions must all match. Matching Show scenarios combine their services, and Hide takes priority. Simulate opens a side panel that updates while you edit. Booking restrictions remain under Service > Booking in the service editor and apply beyond this portal. There is no separate Availability tab. Open When to edit the conditions; collapse it to see their summary. Then show selects the services, with Hide available from the Show menu. Phase conditions use journey steps, dates and seasons use calendars, and time windows have From and To sliders with a selectable check-in or checkout reference and exact numeric values. Select services using the searchable checklist with photos. The catalog shortcut is beside Add scenario.Rename each scenario, add conditions with + beside When, and choose services under Then show. Click show to switch to hide. Comparison menus sit beside condition names. Property, channel, and payment selectors include images or icons and scroll within a fixed height. Season uses an annual date range, and monetary conditions use a decimal money input.
Revision history contains published versions only.

Live prices and checkout

Published prices, availability, payment status and access updates appear while the portal is open. Guides, images and translations can wait until navigation, refocus or refresh. Starting checkout locks the quoted amount, currency and payment terms for 30 minutes. There is no countdown. An expired unpaid checkout asks the guest to review the current total before trying again. Payments being authenticated, processed, authorized or already paid keep their accepted terms. Changing items or quantities requires a new checkout.

Plan the guest journey

Understand the four stay phases in Trellis
The portal has four phases: Registration, Pre-stay, In-stay, and Post-stay. Choose the information each phase should show. For example, a guest can complete their details after booking and receive protected entry instructions only when the access conditions are met. Registration can include forms, documents, a rental agreement, identity checks, fees, and damage protection. Manuals, local guides, services, and support help the guest during the stay.

Build and publish a portal

Create the template and assign properties

Assign properties to a portal in Trellis
Open Reservations > Guest Portal. Choose New portal, give it a clear name, and select its country, or duplicate an existing portal to reuse its structure. Open Settings > General settings > Properties to assign the properties that should use it. Each property can have one published portal configuration at a time. This page manages templates. To inspect a specific guest’s link, registration, or payments, open that guest’s reservation.

Arrange the guest journey

Choose which pages appear in each phase in Trellis
Open Settings > Guides to choose guide visibility by phase. For services, add a Phase condition to a presentation scenario under Settings > Services. Settings apply across properties and booking channels. Use Preview options to inspect the guest view for each phase.

Set appearance and support

Set branding and appearance in Trellis
Open Settings > Appearance for the display name, logo, colors, typography, and shapes. Review the Guest Portal and public access-page previews. Keep the introduction short and make the support options easy to find. Open Settings > Contacts to enter phone, SMS, WhatsApp, and email details. Each valid value makes that contact available throughout the portal. Empty or invalid fields are hidden; clear a field to remove a contact. Configure each channel separately. Contacts and AI Concierge open over the current page.

Decide when entry information unlocks

Decide when access unlocks in Trellis
In Settings > Access, choose how long before check-in access information becomes available. Review this timing together with required registration and verification steps. Use Show property location before access if guests should see the address and directions early. This does not reveal entry codes or private check-in instructions.

Choose what to preview

Select Preview, click it again to open its options, and expand Simulate. Choose a Property and Booking channel to use sample guest data, or choose Use a reservation to select a stay from the calendar. Choose a reservation to update the preview. Closing the dialog without applying discards those changes. Preview selections do not change saved reservations or portal assignments.

Preview and publish

Check desktop and mobile previews with representative bookings. Confirm the assigned properties, registration steps, prices, support buttons, and protected access content. Publish when the configuration is ready; Trellis fills missing translations automatically in the background and the header shows Published. Changes to a draft are not yet the guest’s published experience. Draft edits save automatically. In the Guest Portal editor, Publish opens a review only for critical changes to access controls, payment terms, required registration, legal acceptance, or identity/document collection and retention. Review the changes and affected reservations, then confirm once. Cosmetic edits, translations, optional questions and ordinary content publish directly. The separate Rules editor retains its publication review. Confirmed changes apply to existing portals, including guests who have already started registration. Changed settings can replace reservation-specific customizations. Completed payments, signed documents, and submitted answers are preserved. Publishing does not refund or charge guests. Publishing reviewed requirements from portal settings can reopen completed registration and block access again. Check the reservation warnings before publishing. The separate rule editor retains its option for reopening completed registrations.

Configure registration rules

Add registration rules in Trellis
Open Reservations > Rules to create or edit the requirements used in the portal. Choose the rule type, such as a check-in form, rental agreement, mandatory fee, or damage protection. You can also open that page through Settings > Registration > Open rules in the portal editor.
Configure a check-in form in Trellis
Give a form an internal name and a clear guest-facing label. Check whether it is live, whether it is Required before access, and whether it applies to the primary guest or the other travellers. In a check-in form rule, the Prefill names from the reservation option is on by default. Use the reservation name for the primary guest. Guests can edit it. Other guests enter their own names.
Collect arrival information in Trellis
Add the arrival fields needed for the stay, such as arrival time. Standard fields have defined types; use labels and help text to explain the requested answer.
Apply rule conditions in Trellis
Use conditions to apply a rule to the relevant channels, properties, reservation statuses, or guest counts. Test a booking that should match and one that should not.
Collect guest details with conditional fields in Trellis
For guest details, use conditional follow-up fields when an answer changes what you need next. For example, ask for a place of birth only under the applicable country condition. Preview each branch so guests do not have to answer irrelevant questions.

Additional travellers

In an Other guests step, enable Exclude the primary guest to collect only the remaining travellers. The booking holder keeps their existing details, and solo reservations skip this step. Enable Exclude owner stays in a rule’s conditions when that rule should not apply to reservations classified as owner stays. In a consent field, Ticked by default is off initially. Enable it only when the checkbox should start selected; guests can change it, and previously saved answers take precedence. For terms, Require consent is on by default. Turn it off to show the document for information only. It will not block registration, record acceptance, or create a signed copy.

Prepare a rental agreement

Prepare a rental agreement in Trellis
Create the agreement under Reservations > Agreements, then select it in the rental-agreement registration step. Write the agreement and insert supported property, guest, and reservation variables where the wording should vary by stay. Preview a sample booking to confirm the values and requested signature fields. After signing, the guest can download a PDF with the agreement, stay details, signature, timestamp, and document hash. To keep the signed copy for your records only, turn off Guest can download signed PDF on the rental-agreement step. Your team can always download it from the reservation’s Guest Portal section.

Collect registration charges

Set a mandatory fee

Configure a mandatory fee in Trellis
Choose the fee amount, currency, and calculation method, such as a fixed total or an amount per guest or night. Review any caps on the total, nights, or guests counted. These are registration charges; optional extras belong in Services.
Set fee exemptions in Trellis
Add the applicable exemption conditions and test them against representative answers and bookings. When a fee depends on registration details, the guest may need to complete the form before the final total can be calculated.

Offer damage protection

Choose damage protection options in Trellis
In Damage protection, choose whether to offer a non-refundable waiver, a refundable security deposit, or both. Explain each option in the guest-facing text and review its amount and currency. When both are offered, the guest completes one choice; completing it locks the other option. When both options are offered, choose a Guest layout. Checklist stacks the two options. Side by side compares them in two columns, labels the option marked Most popular as recommended and the other as the alternative, and shows whole prices without pence. Under Step wording, you can replace the step heading, introduction and explanation. Each option can also have its own subheading, button label and small print. Any field you leave blank keeps the default wording.
Test protection scenarios in Trellis
Set the default amount and any pricing scenarios, then use the sample booking controls to check which scenario wins and what the guest pays. Test both matching and non-matching bookings before publishing.
Review deposit timing in Trellis
For a deposit, review authorization timing before check-in and release timing after checkout. Saving a card, placing a hold, and capturing funds are separate actions. Check the deposit rules below before enabling renewal or inspection requirements.

Pricing scopes and request history

Pricing scenarios for fees, waivers and deposits can target properties, property groups, or both. If both are selected, both must match. Numeric conditions are optional. The first matching scenario applies; otherwise the default price applies, unless the waiver requires a matching scenario. Check the sample booking before saving. For standalone tourist-tax and damage-waiver rules, select booking channels below the property and group conditions in each charge scenario. A booking must meet every specified condition, including the channel. Choose Do not collect this charge to exempt matching bookings. Place this scenario before broader price scenarios that could also match. Change the channel in the sample booking to verify the amount before saving. To limit waiver availability, enable Only offer the waiver when a pricing scenario matches in the damage waiver settings. Guests whose booking matches a scenario can choose the waiver. Other bookings keep the security deposit option. Keep the deposit enabled while this setting is on. Use Bedrooms booked when eligibility depends on the accommodation booked, together with conditions such as the number of nights. This count can differ from the property’s total bedrooms. If the booked count is missing, check the reservation’s listing before collecting payment. Existing rules keep their default-price behavior until you enable this setting. Property selectors show search first, then an All properties or group filter. Select visible properties changes only the current subset; other selections stay unchanged. For service prices by group, create a separate service for each price, filter to the group and select its properties. Later group changes do not update saved selections automatically. Registration settings list all rule definitions. Use the Enabled/Hidden switch to choose which rules this portal uses. Hiding a rule keeps its definition and does not change other portals. A rule can be enabled for no portals; new definitions start unused. Use Open to edit a definition in Rules. The list headings open the full Rules, Services and Guides pages in a new tab. A fixed-price service with an amount of zero appears as Free and can only be requested, without payment. See Manage service requests below to follow requests and their quoted totals. Before saving a card, the guest must accept the displayed deposit amount and hold terms. Continue to card details stays disabled until they select the checkbox. If the quoted amount changes, the guest must accept the new amount. Saving a card does not itself charge the guest or place a hold. Authorization follows the configured timing before the property’s local check-in time. Enable Require inspection before release in the deposit settings when an operator must review the property first. Open the reservation’s Guest Portal, find the deposit, select Release, and confirm that the inspection is complete before releasing the hold. Trellis records that confirmation. This is an operator confirmation, not an automatic check of a cleaner’s task. With inspection required, automatic release is disabled. The bank hold can still expire, and renewal stops after the configured release delay. Review the actual authorization deadline in the reservation. Existing configurations keep their release behavior until you enable and publish this setting.

Card confirmation and payment exceptions

Saving a deposit card does not itself charge the guest or place a hold. If confirmation is pending, select Check confirmation before trying another card. This checks the saved setup without asking the guest to confirm it again. Workspace administrators can open the reservation’s Guest Portal section and select Mark as paid externally only after receiving the full amount outside the portal. Add a payment note and confirm receipt. To waive the requirement, select Exempt and record the reason. Trellis records who made the change and when. Neither action charges or refunds the guest. These actions can replace an uncharged saved deposit card. Trellis retires that card collection so it cannot later authorize a hold. Deposits with an authorization pending, an existing hold, captured funds, or a failed or unknown authorization outcome remain protected. Check the payment before attempting an override. Restoring an exempted saved-card requirement requires fresh guest consent and card collection. Payment exceptions do not approve manual verification or bypass the other access conditions.

Prepare access instructions and guides

Build the Access page in Trellis
Arrange the arrival steps in the order the guest follows them. Include a short instruction and a useful photo or video for each step. Maintain the underlying property instructions in Properties, then check the portal preview and its access-unlock rules.
Choose house manuals and local guides in Trellis
Use a house manual for the accommodation’s own information, and local guides for nearby places and activities. Select the content intended for guests; a staff manual can contain different details.
Create and edit a local guide in Trellis
Open Reservations > Guides to create a local guide with a name and description. You can start with AI-assisted content, then review the wording, places, and map links before sharing it. Check that the recommendations fit the property’s location.

Add guides and house manuals

On the Guide page, choose Add → Guide or House manual. Select a template in the sidebar, then Use template to attach it to the property. The template supplies shared content and structure; existing property values are retained and missing values stay empty. If the property already has a manual, use Add guide for another guide. When switching properties, wait for the sidebar to load. A property without manual content or a saved template opens the template chooser; an existing template opens in the editor, even if its guest sections are still empty.

Edit the house manual in the sidebar

Select a property in the preview, then open Guide > House manual. Edit its template, guest sections, points of interest, and guest QR code in the sidebar. Changes appear in the preview; select Save property changes to save them. Publishing the portal does not save the property manual. This editor contains guest content only.

Sync with PMS

Manage instructions in the property access editor, also available in the Guest Portal builder sidebar. Trellis remains the source for the published guide, with or without PMS export. Enable optional PMS export to send supported text to a compatible connected PMS after publishing. You can still edit photos, videos, and routes in Trellis. Review warnings for content the PMS cannot represent, such as media or conditional steps, and for export failures. Reservation and device codes are not copied into shared PMS instruction fields. A failed export does not undo publication in Trellis, and later PMS imports do not replace the published guide.

What guests see

Registration shows the configured steps and a summary before submission. Guests can leave and return without losing uploaded files that are still valid. When registration does not block browsing, they can read the guide while a reminder stays visible; private access information still follows the required checks and unlock time. The Access block uses the property’s published guide. Guests choose an arrival route and can switch between step-by-step and full-guide views. YouTube and Google Drive manual videos play inside the portal; Drive files must allow the guest to view them. Direct video files can include a captions URL in the Markdown link title: captions: https://example.com/captions.vtt. If a guest does not have their private link, the public Guest Portal access page can find one active portal using the PMS confirmation code or OTA reservation number together with any part of the guest name. Before opening the private portal, the guest confirms the complete surname or full name from the booking. The page does not show reservation results or booking details.

Handle guest questions

In the portal builder, open AI Concierge, select an active AI Agent in the right sidebar, and enable the concierge. If that agent becomes unavailable, choose another active agent before publishing it again. When a guest sends a message through the AI assistant, the conversation appears in Inbox with the Guest Portal channel. Your AI Agent can answer in that same conversation, and your team can review or reply from Inbox. Replies remain visible in the portal, so the guest can continue the conversation without switching to another messaging app. The conversation stays linked to the reservation, which supplies the agent’s stay context.

Offer guest services

Create the offer

Create a service in Trellis
Open Reservations > Services and create a service. Enter its name, description, image, and price, then choose its eligible properties and availability rules. Preview the offer as a guest to check the total and wording.
Choose direct purchase or approval in Trellis
Choose Requires approval when your team must check the request before confirming it. The request appears in the reservation conversation and sidebar; a paid service becomes payable after approval. Choose Direct purchase for services the guest can buy without that operator decision. Availability rules can still prevent a service from being offered or purchased. Approval, payment, and fulfillment are separate stages: an approved request is not proof that the guest paid or that your team delivered it.

Choose the payment account

Open Service payment settings at the top of Reservations > Services for the general service payment account. Follow its link to Settings > Integrations > Payments to assign Stripe accounts to specific properties. A new purchase uses its reservation property’s assigned account, or the general account when the property has no assignment. Payment accounts are not selected on each service. An existing payment attempt keeps its account during retries. If the assigned account is unavailable, payment is blocked instead of being moved to a different account.

Send service payments to Guesty or Kross

In the service’s settings, enable Sync with PMS and choose the Guesty fee category to send its paid orders and recorded payments to Guesty. Confirm the category’s taxes and owner allocation in Guesty. Pending payments can sync when Trellis verifies that payment automation is already disabled, or that they are recorded Airbnb payments or cash placeholders without a payment policy. Cash placeholders must also have no payment method attached to the reservation. Active or unverified payment automation and authorization holds block sync. Trellis checks the remaining balance and existing payment schedule before reporting success. Reconcile refunds separately. Stay extensions use their own reservation sync. For Kross, enable Sync with PMS and enter the Kross extra service ID. Each paid order is added to the Kross reservation as that extra service, with its quantity and the VAT set in Kross, and its Stripe payment is recorded. If Kross does not link the charge to the extra service, the sync stops for review. Reconcile refunds separately. Other PMS providers are not supported for this service-payment sync.

Translate and review the catalog

Services start in the workspace language. Saving text generates translations automatically in the background. Use the language dropdown to preview or edit them. Manual edits protect only that field and language from future generation; missing translations fall back to the workspace-language content. The surrounding catalog and payment controls use the selected app or portal language, including its date and price formatting. Arabic and Hebrew layouts use right-to-left presentation.

Follow the guest’s payment

Guests can change quantities and remove items before payment. Compatible services in the same currency can share one cart and Stripe checkout; different currencies require separate purchases. The checkout uses the account selected for that reservation, even when your workspace has several connected Stripe accounts. On supported devices, Stripe offers Apple Pay or Google Pay above the regular checkout button. Card payment and secure Stripe Checkout remain available. A successful payment records each service on the reservation timeline, and Stripe sends the receipt to the checkout email address.

Service availability and request details

In Reservations > Services, configure the service type, eligible properties, minimum and maximum stay length, sales opening date, earliest confirmation date, and arrival or departure conflicts. Dates follow the property time zone. A service without valid rules, outside its booking window, or, for a paid service, without an available payment account is hidden. Portal, conversation, and workflow offers use the same checks. Existing payment requests must still meet the current rules. New service payments authorize the amount before a final availability check. An unavailable service is not captured. Requests still require your approval; reaching the confirmation date does not approve them automatically. Early check-in, late checkout, and stay extensions remain unavailable until calendar blocking, reservation updates and cleaning notifications can be guaranteed. Seasonal dates control whether the service appears in the catalog. A season can cross the year boundary. Choose workflow-only visibility for services that should be offered through a workflow rather than listed for every guest. Guests choose the quantity and supply any required note before continuing. Their payment total and retries retain those details. To sell one unit per unused bed, such as extra linen, set Quantity limit to Spare beds in the property. Spare beds are the property’s beds minus the reservation’s guests. Guests can buy up to that number, within the maximum quantity. Stays with no spare bed or no recorded bed count do not see the service. Booking scenarios can also use Spare beds as a condition.

Saved cards and the payment drawer

Service and fee payments open in a drawer from the bottom of the guest portal. Guests can choose to save their card with Stripe and reuse it for later payments during the same stay, when those payments use the same payment account. Saving is optional. Each purchase still requires the guest to confirm payment.

Manage service requests

Manage service requests in Trellis
Open Reservations > Requests and review each request’s status and details. Use the list or monthly calendar to plan the next action. The list includes the request date, reservation check-in date, and quoted total for the quantity requested. The calendar groups by request date, not delivery date, so check the service details before planning fulfillment. Approve or decline requests that need a decision, then track payment and mark delivered services as fulfilled. To review sales and performance, open Insights > Results > Upsells. Filter by date and property, and select an activity row to inspect its linked conversation.

Review registration applications

Go to Reservations > Registration to review submitted registrations. The left side groups applications into To do, Approved, and Declined. Select an application to review the guest, property, stay, registered guests, and identity-verification evidence. For a manual identity check, review the submitted document and selfie, then approve or decline the application. Checks completed through a connected identity-verification service remain visible with the provider result and do not require a second manual decision. When the identity rule uses Automatic name check, Trellis reads the name on the guest’s document and approves it when it matches the name on the booking. Middle names and accents on the document don’t prevent a match. If the names differ or the document can’t be read, the application stays in To do, and the reservation’s Guest Portal section shows what the document says next to the booking name. The check compares names only. It doesn’t confirm that the document is genuine.

Review an individual guest portal from a reservation

Open a reservation from Reservations or Inbox to review its Guest Portal without leaving the reservation. The Guest Portal section appears only when that reservation already has a portal. Use the section to:
  • Check whether the portal is active, when the guest last opened it, and which registration step needs attention.
  • Review registration answers and uploaded files, download the signed rental agreement, and approve or reject a manual verification when required.
  • Approve or decline service requests, mark paid services as fulfilled, and review relevant payment or deposit status.
  • Review recent portal activity, open the guest preview, or copy the current link.
Link rotation immediately replaces the old link, and revocation disables guest access. Use those actions only when the current link should stop working. To create or configure reusable templates, go to Reservations > Guest Portal. The deposit row shows the authorization deadline when Stripe provides one, and View in Stripe opens that payment in the connected account. Expand Deposit history to review the latest 25 deposit events and their transaction links. An unknown deadline is shown explicitly; Trellis does not estimate it from a fixed number of days. Viewing the history never captures funds. If the bank declines the first hold, for example for insufficient funds, the damage protection step reopens. The guest sees the reason in the portal and is asked to add another card. The deposit row shows the same reason, and an alert with a link to the reservation goes to your configured workspace Slack channel. To let the guest continue without a deposit, exempt the step from the reservation. Enable Renew before expiration in the security deposit settings to renew a hold 24 hours before its actual Stripe deadline when the stay still needs coverage. Trellis confirms and records the replacement before releasing the original. A refused authorization keeps the original hold and raises an alert in your configured workspace Slack channel, with a link to the reservation. An interrupted attempt resumes from the recorded transaction; it does not automatically capture funds. The option is off for existing configurations until enabled and published. Renewable holds are released after the property’s local checkout time and the configured release delay. If an operator has captured funds, Trellis leaves the refund decision to the operator.

Review a blacklisted guest’s reservation

When a reservation is linked to a contact on the guest blacklist, a workspace administrator must review that reservation before its portal releases access details. Open the reservation, read the reason in Blacklisted guest — reservation review, and choose Approve access for this reservation or Deny access for this reservation. This review is available even before a guest portal is created. While the review is pending or rejected, the portal withholds entry codes, private check-in instructions, and Wi-Fi details. The AI concierge is also unavailable. The guest sees a neutral review message; the internal reason and blacklist label are not shared with them. Approval satisfies only this reservation’s blacklist review. Registration, identity verification, and access timing still apply. Each future booking needs its own review. Rejecting access keeps these details locked; it does not cancel the reservation.

Clear and restart registration

Workspace administrators can open an active reservation’s Guest Portal and use the trash icon beside a submitted field, file, or registration step. Confirm the action to clear the selected data and reopen the affected step. Other answers and files remain available when only one item is removed. Use Reset registration to clear registration answers and uploads and restart the non-payment steps, including identity verification and agreement signing. Resets remove the previous host approval. Payments, deposits, and historical signed agreements are retained. Guests complete the reopened steps through their existing portal link.

Send completion status to Guesty

In portal rules, turn off Mark checked in after registration when registration and physical arrival are separate. Completing the required steps still records registration completion; the reservation keeps its current status. Existing portals keep their previous behavior until this setting is changed and published. Guests can then confirm their arrival from the scheduled check-in time, after completing registration and any required verification. After arrival, they can confirm departure. Both actions require confirmation and are recorded in the reservation history. Guesty receives the current guest-stay status through a retryable update with readback verification; the booking dates and booking status are unchanged. Other PMS providers do not yet receive these guest-operated stay confirmations. In the portal PMS mappings, map Registration completed to a Guesty Boolean custom field. It becomes true when registration and any required manual review are complete. Incomplete, revoked, or expired portals return false. Configure your Guesty message conditions to use this field before sending arrival instructions. Creating the mapping does not change existing Guesty workflows.

Test the guest journey

Before publishing, test a booking through registration, identity review, and the access-unlock time. Download the signed agreement and confirm that portal messages and Inbox replies appear on both sides. For payments, check the transaction and deposit status in the reservation; a saved card alone does not create a hold.

Common problems

Read the editor error and fix the highlighted field or assignment. Reload to check the saved draft, then publish when ready. A saved draft and a published portal are different states.
Clear the search and check whether another published portal already uses that property.
Check the permitted format and size for that field. Supported registration uploads include JPEG, PNG, WebP, and PDF. Ask the guest to retry before the portal expires.
Open the reservation’s Guest Portal and check required registration, identity review, the access-unlock time, and any blacklist review. Completing the form alone may not satisfy all of those requirements.
Check its property assignment, availability rules, booking window, and payment account. An approval-required request must also be approved before payment becomes available.
  • Properties — maintain the source of guest instructions.
  • House manuals — choose information for each audience.
  • Inbox — answer portal messages and review the reservation.
  • Workflows — automate supported follow-up steps.

One service catalog

The Services page is available in all four portal phases, even when the catalog is empty. Reservations > Services and the portal builder share the same service list and editor. Manage the general Stripe account on the Services page. In the builder, set the page title, body, and cart option. Use presentation scenarios to show or hide services. Open service settings from the simulator or use the catalog shortcut beside Add scenario. Activating, deactivating, editing, or deleting a service updates the shared catalog.

House manual availability

The published house manual is available by default during registration, before arrival, during the stay, and after checkout. Guests do not need to finish registration to read it. Select a phase in the portal editor to hide the Guide page or set visibility rules for the manual in that phase. Private access details still follow the required checks and unlock time.

Property titles in the guest language

On the property page, click the globe icon beside Guest-facing title to enable Automatically translate for other languages. This optional setting is off by default. Turn it off to show the original title again. Guest-facing property titles are translated automatically into the selected portal language. Property names and brands stay unchanged; descriptive text is translated. The original title remains visible while a missing translation is prepared, then updates automatically. Changes to the saved title trigger a new translation.

Edit Access in the portal preview

Select a property and open Access in the Guest Portal builder. Edit the instructions directly in the preview. Open a route, then drag blocks from Basics or Property in the content sidebar into a step. The same editor works in mobile and desktop previews. The route outline stays outside the phone and inside the desktop preview. Changes save as an Access draft; use Publish in the Access sidebar to update the guest instructions. Switching to Live hides editing controls.

Manage service requests from mobile Inbox

Workspace admins can approve or decline a Guest Portal service request from its card in the mobile Inbox conversation. The card shows the service, quantity, quoted total, guest note, and current status. Approved or paid services can be marked fulfilled. Requests that still need an agreed price link to the web request queue. When manual verification is enabled, new document uploads wait for review. In the reservation’s registration section, choose Approve document or Request replacement and enter a reason for the guest. A replacement request reopens the upload form; approval completes only that document step. Other registration and access requirements still apply. Previously completed uploads keep their existing status.