Product and implementation guide
Map the stay from request to departure
Hotel Management is the ArcApps application for hospitality operations. Discuss reservations, front-desk work, room readiness, guest information and billing requirements as part of the proposed scope. Define the difference between an enquiry, a provisional reservation and a confirmed booking. An attractive availability screen is not enough if staff interpret the same status differently.
Example: a changed arrival date
A guest requests a later arrival after a room has been reserved. Identify who checks availability, approves the change and communicates any revised conditions. Test the effect on room allocation and operational work through the supported workflow. External booking channels, payment services and automated synchronization require explicit confirmation.
Coordinate room readiness
Agree how front-desk and room-operation staff communicate that a room is ready. Specify who can update the status and what happens when information is uncertain. Avoid assigning a room solely because an outdated screen appears clear. Staff need an understandable escalation route for discrepancies and guest requests.
Protect guest records and review checkout
Limit access to personal and financial details according to approved responsibilities. Do not use real identity documents in demonstrations. Rehearse check-in, checkout and a correction with synthetic records, and review financial or legal requirements with qualified advisers. Confirm reporting, export and retention in your implementation plan. The business software guide provides questions about ownership, support and evaluating exceptions.
Access, setup and support
Start with a confirmed subscription and implementation scope, then use the sign-in address supplied by the team. The public website does not provision accounts. Your organization should identify an administrator, approve each user's role, and confirm which locations and records belong in the setup. Use unique accounts and follow the approved recovery process rather than sharing passwords. Confirm the available controls in your configured environment before entering live information.
Validate before going live
Prepare synthetic examples covering an ordinary workflow, a correction and a restricted action. Reconcile imported records against the approved source and agree who resolves differences. Ask each intended role to complete its tasks, including on the devices they will actually use. Record issues with the expected outcome and the observed result. Do not use real customer or employee records in a public demonstration.
Daily operation and changes
Keep operational policies and responsibilities alongside the configured workflow. When a task fails, note the time, action and visible error without sending credentials or sensitive records. Contact the support route agreed in your service terms. Changes to modules, integrations, exports, retention or commercial scope require confirmation; they are not implied by this guide. For onboarding and troubleshooting specific to your deployment, request a walkthrough using your approved scenarios.
Open the product guide · Product FAQ · Implementation support