Let agents coordinate the routine work behind every stay.
FirstConnect observes operational events, prepares the next action, works within property-approved rules and escalates anything that needs staff judgement.
Payment status unmatchedException · finance review
Conceptual states, not live customer records or performance data.
What do supervised hotel agents do?
Operational events can trigger permitted preparation, routing and status checks. Property rules determine which actions may proceed, which need staff approval and how failed or uncertain steps enter an exception queue.
Not another chatbot
Agents turn operational events into accountable next actions.
A FirstConnect agent is a focused workflow capability. It monitors an approved event or queue, gathers the information needed for that task, prepares or completes permitted actions and routes uncertain or sensitive cases to the right hotel team.
01
Observe
Detect a reservation, incomplete registration, consent state, guest request, upcoming checkout, payment update or unresolved exception.
02
Understand
Assemble the relevant journey information, property rules and current status.
03
Act within policy
Prepare or perform a permitted reminder, routing step, status update or guest communication.
04
Escalate and record
Send exceptions to staff with supporting context and preserve the workflow history.
Automate coordination—not accountability.
Eight focused agents
A specific job, trigger and control point for each workflow.
These agent definitions describe a pilot-scoped operating model. The exact automated actions, integration events and approval thresholds are agreed with each property.
01
Arrival Preparation Agent
Prepare each expected arrival before the guest reaches reception.
Trigger
Reservation information arrives or changes
Arrival enters the preparation window
Registration remains incomplete
Inputs
Available reservation details
Property arrival rules
Guest contact route
Registration status
Permitted actions
Prepare a journey task and secure invitation
Send an approved reminder
Add incomplete items to the arrival queue
Staff checkpoint
Staff review missing details, unusual requests and guests who need an assisted route.
Example exception
The reservation has no valid contact route or conflicts with submitted information.
ResultA prepared, visible arrival queue.
02
Registration Intelligence Agent
Reduce repeated entry while preserving guest and staff review.
Trigger
Registration form submitted
Supported document uploaded
Required information missing
Extraction confidence below a configured threshold
Inputs
Guest-submitted fields
Supported document image
Available reservation data
Property-required fields
Permitted actions
Extract and compare available fields
Flag gaps or inconsistencies
Present fields for guest correction
Prepare uncertain cases for staff
Staff checkpoint
Staff confirm low-confidence, inconsistent or property-specific information.
Example exception
An image is unclear or a submitted value differs from the reservation.
ResultA guest-reviewed digital registration record, not automatic identity approval.
03
Consent and Preference Agent
Apply recorded guest choices to later communication and data-use steps.
Trigger
Guest reaches a consent step
Preference changes
Promotional message is prepared
Consent is absent, expired or withdrawn
Inputs
Purpose-specific choices
Communication preferences
Property policy
Workflow context
Permitted actions
Present and record choices
Check promotional eligibility
Block or flag an ineligible action
Retain changes in consent history
Staff checkpoint
Staff define permitted purposes and review unclear use cases; they cannot silently override guest choice.
Example exception
A promotional offer is prepared without the required opt-in.
ResultCommunication eligibility tied to recorded preference.
04
Guest Communication Agent
Coordinate useful operational communication throughout the stay.
Trigger
Approved arrival or service update
New guest request
Request deadline approaching
Checkout preparation
Eligible approved offer
Inputs
Journey stage
Communication preference
Approved template
Request status
Property rules
Permitted actions
Prepare or send an approved operational message
Route requests and status updates
Escalate delays
Present eligible approved offers
Staff checkpoint
Staff approve campaign content, partner offers and service recovery requiring judgement.
Example exception
A request approaches its deadline or needs another department.
ResultA visible communication and request workflow across teams.
05
Offer Coordination Agent
Present relevant hotel services without weakening guest trust.
Trigger
Guest reaches an eligible stage
Approved service becomes available
Configured offer criteria match
Guest expresses interest
Inputs
Journey stage
Recorded preference
Hotel service availability
Approved offer inventory
Eligibility rules
Permitted actions
Prepare eligible offers
Route guest interest
Track offer status
Suppress promotion without consent
Staff checkpoint
Hotel teams approve offer content, price, availability and any partner participation.
Example exception
An offer is unavailable or conflicts with the guest's preference.
ResultConsent-led opportunities connected to the stay, where configured.
06
Checkout Preparation Agent
Begin checkout review before the departure queue.
Trigger
Departure approaches
Bill information becomes available
Early checkout requested
Charge changes
Billing question raised
Inputs
Available charges
Bill or invoice information
Departure time
Checkout policy
Guest contact route
Permitted actions
Prepare checkout task
Present available bill information
Request guest review
Route disputes
Prepare an approved payment-link request
Staff checkpoint
Staff approve corrections, disputed charges and exceptional checkout handling.
Example exception
A charge is questioned or changes after presentation.
ResultEarlier bill review and visible departure exceptions.
07
Payment Status Agent
Surface incomplete, failed or mismatched provider payment states.
Trigger
Approved link requested
Provider status update
Payment pending, failed or expired
Checkout status changes
Inputs
Approved payable amount
Provider reference and status
Checkout task
Escalation rules
Permitted actions
Send an approved provider link
Record reported status
Send permitted reminders
Alert staff to failure or mismatch
Staff checkpoint
Staff handle disputed amounts, refunds, corrections and financial exceptions.
Example exception
The provider reports success while the hotel checkout record remains incomplete.
ResultPayment status visible in the workflow without processing funds in FirstConnect.
08
Reconciliation and Handover Agent
Close gaps across checkout, finance and shifts.
Trigger
Checkout completed
Payment confirmation received
Mismatch detected
Shift handover begins
Reconciliation window closes
Inputs
Journey and checkout status
Provider-reported status
Staff actions
Property and shift context
Permitted actions
Compare available references
Prepare unmatched-item queue
Summarize pending handover actions
Surface configured cross-property exceptions
Staff checkpoint
Finance and operations approve corrections, write-offs and final exception closure.
Example exception
A provider reference cannot be matched to the hotel checkout record.
ResultA prioritized exception queue, not automatic accounting closure.
Payments are completed through the property’s approved payment provider. FirstConnect coordinates the workflow and reported status.
The sequence below shows what the agent may prepare, what the guest or staff must decide and how failures remain visible.
01
System event
A reservation, request, checkout or provider status changes.
02
Agent context
Relevant records and the current journey state are assembled.
03
Property rule
Eligibility, permission and approval level are evaluated.
04
Agent action
An approved routine action is prepared or performed.
05
Guest or staff decision
The guest reviews a choice or staff approve a sensitive action.
06
External-system update
Connected systems report or receive an agreed status update.
07
Exception
Uncertain or failed actions pause and route to the right queue.
08
History
Actions, decisions and outcomes remain available under the agreed policy.
One operations queue
One queue for work that still needs attention.
Pending arrival, service, checkout, finance and handover work can be organized around an owner and a next action. Items shown here are illustrative, not live operational records.
Arrivals
Registration incomplete
Guest unreachable
Submitted information needs review
Arrival mode requires staff
Guest requests
New or assigned
Near service deadline
Escalated
Completed
Checkout
Bill awaiting review
Disputed charge
Payment pending or failed
Checkout incomplete
Reconciliation
Payment unmatched
Status conflict
Manual review
Exception resolved
Shift handover
High-priority open items
Guest commitments
Outstanding checkout
Finance exceptions and owner
Staff reviewing arrival information at reception. This prepared image does not depict a live dashboard.
From folio to settlement
Checkout is a coordinated operation, not a single payment screen.
01Assemble available bill or invoice information.
02Give the guest a review route.
03Route questions and disputes to hotel staff.
04Obtain staff approval for corrections.
05Issue an approved provider payment link.
06Receive provider-reported status.
07Compare checkout and payment references.
08Place mismatches in the reconciliation queue.
09Have staff resolve financial exceptions.
10Retain the completed journey for reporting and permitted follow-up.
FirstConnect coordinates the checkout workflow. Financial records, payment execution and final accounting remain with the hotel and its approved providers.
Multi-property comparison and consolidated reporting depend on the configured pilot scope.
System responsibilities
Coordinate across systems without hiding responsibility.
Each connection has an agreed owner, trigger, response and failure route. The categories below show possible interfaces, not confirmed third-party integrations.
PMS or property system
Received
Available reservation and stay status
Returned
Agreed workflow status
Trigger / cadence
Event or scoped sync
On failure
Pause affected item; alert front office
System of record
PMS for reservations and stays
Reservation or booking source
Received
Available booking details and changes
Returned
Agreed acknowledgement
Trigger / cadence
Event or scoped sync
On failure
Flag missing or conflicting booking
System of record
Booking source until accepted by PMS
Registration workflow
Received
Guest-submitted fields and review state
Returned
Completion or exception state
Trigger / cadence
Guest submission
On failure
Route incomplete or uncertain fields
System of record
Agreed registration record
Consent records
Received
Purpose and communication choices
Returned
Eligibility or change event
Trigger / cadence
Choice or policy update
On failure
Block optional action if status is unknown
System of record
Ownership agreed during pilot
Messaging provider
Received
Delivery route and provider status
Returned
Approved message request
Trigger / cadence
Approved action or status event
On failure
Keep failed delivery visible
System of record
Provider for delivery; hotel for policy
Payment provider
Received
Provider reference and payment status
Returned
Approved link request
Trigger / cadence
Provider event or scoped lookup
On failure
Pause and alert on missing or mismatched status
System of record
Provider for payment execution
Finance records
Received
Available bill and reconciliation references
Returned
Exception and reviewed outcome
Trigger / cadence
Agreed checkout or finance cycle
On failure
Route unmatched entries for finance review
System of record
Hotel finance system for accounting
Operations dashboard
Received
Journey tasks, approvals and exceptions
Returned
Staff decision and task status
Trigger / cadence
Workflow event
On failure
Show stale or failed updates for review
System of record
FirstConnect for coordinated workflow
Integration availability and system-of-record responsibilities are confirmed during pilot design. Consent and audit-record ownership must be agreed explicitly.
Each workflow should use only information required for its approved task.
Purpose-based communication
Promotional eligibility follows recorded guest choices and property policy.
Human oversight
Sensitive, financial, low-confidence and exceptional actions can require staff approval.
Action history
Events, approvals and exceptions can be retained for review under the agreed data policy.
Configurable retention
Retention and deletion rules are established with the property and applicable requirements.
Role-based access
Teams should see only the properties, queues and functions required for their work.
These are design principles and configurable controls, subject to the agreed implementation. Each hotel remains responsible for its notices, access and record-handling policy.
Questions
What hotel teams should expect from supervised agents.
What is an agent in FirstConnect?
A focused workflow capability that observes an approved event, gathers relevant context, prepares or performs permitted actions and escalates exceptions to hotel staff.
Does FirstConnect operate without hotel staff?
No. Properties define which actions may run automatically, which require approval and which stay with staff.
Can agents change a guest's bill?
Agents can flag a question or prepare an exception. Hotel staff approve bill corrections and financial decisions.
Does FirstConnect process the payment?
Payment execution remains with the property's approved provider. FirstConnect can coordinate links, provider-reported status and exceptions.
Can agents send promotional messages?
Only when eligible under recorded preferences, approved property policy and the configured channel.
What happens when an integration fails?
The affected action should pause and remain visible with context in a staff exception queue.
Can different properties use different rules?
Yes. Approval levels, communication policy, arrival modes and escalation ownership can be configured per property.
Is every agent available today?
Availability depends on the property's systems and agreed pilot scope. A demo and pilot identify workflows that can be activated first.
Start with one operational workflow
Identify the routine work your hotel should stop coordinating manually.
Map one property’s arrival, communication, checkout and reconciliation process. Then select the supervised agents, approval rules and integrations suitable for the pilot.
