Colleague
Advantage

Colleague Advantage should be used as a preparation tool, not simply a place to look up a reservation after the guest arrives. A strong Front Office operation uses CA to identify important arrival details in advance, including loyalty status, special requests, traces, alerts, guest preferences, stay history, billing notes, and reservations requiring follow-up. The purpose of this review is to reduce surprises at the desk and help the team deliver a more polished arrival experience.

When CA is used correctly, the guest should feel that the hotel was ready for them. The agent should already know when a guest is elite, when a reservation has special handling, when a room assignment should be reviewed, when preferences are visible, and when a billing or routing concern requires closer attention. Preparation is one of the easiest ways to improve both service quality and operational accuracy.

The Pre-Arrival Dashboard is one of the most useful starting points for AM shift preparation. Agents should use it to review the day’s arrivals with enough detail to understand who is arriving, what needs attention, and which reservations should be handled before the guest reaches the Front Desk. This review should not be rushed. The goal is to identify anything that could affect room assignment, billing, service delivery, guest recognition, or the arrival conversation.

A practical arrival review should include loyalty status, VIP designation, room type, rate information, alerts, traces, preferences, special requests, comments, stay history, and any billing or routing instructions visible through the reservation or guest profile. If the report is printed or reviewed manually, elite arrivals and VIPs should be highlighted so the team can quickly identify guests requiring additional attention throughout the shift.

The Pre-Arrival Dashboard can also help the team organize its work. Rather than waiting for each guest to arrive and discovering issues one at a time, the AM shift can prepare the day in advance, resolve what can be resolved early, and clearly pass along anything still pending to the PM team.

Guest preferences and stay history are valuable because they allow the hotel to provide service that feels informed rather than generic. If a guest has a known room preference, arrival pattern, special request, prior concern, or repeated behavior, the agent should use that information to support the stay. This does not mean every preference can be guaranteed, but it does mean visible information should not be ignored.

Agents should review notes carefully and professionally. Not every note requires guest-facing conversation, and not every piece of information should be mentioned at check-in. The purpose is to prepare the operation. If a note indicates a prior issue, special sensitivity, room preference, accessibility request, or manager involvement, the agent should use that information to avoid repeating the same problem and to ensure the next step is handled with care.

When adding or relying on notes, remember that they should be factual, relevant, and useful to future users. Avoid emotional language, assumptions, or vague comments. A good note helps the next agent understand what happened and what needs to be done. A poor note creates confusion or adds unnecessary commentary without operational value.

Elite arrivals should be identified before check-in so the team has time to review upgrade opportunities, preferences, benefit handling, arrival notes, and any special recognition needs. A loyalty guest should not have to remind the hotel of information that is already visible. When an agent acknowledges status confidently and accurately, it communicates that the guest is recognized and that the hotel was prepared.

Recognition should be professional and accurate. Agents should avoid overpromising benefits that depend on availability, property procedure, or eligibility. If an upgrade is unavailable, the response should still acknowledge the guest’s loyalty and explain the situation clearly. The goal is not to promise what cannot be delivered; the goal is to show that the status was reviewed and taken seriously.

Elite and VIP arrivals should be communicated in shift handoff when there is anything pending, unusual, or important for the next shift to know. This may include room assignment concerns, delayed arrivals, special requests, benefit questions, prior complaints, or manager follow-up.

Traces and alerts should be treated as action items. They exist because something about the reservation requires attention, communication, review, or follow-up. Agents should not clear or ignore these items without understanding what they mean. If a trace requires action from another department, the agent should confirm whether the action has been communicated and whether follow-up is still needed.

Alerts may affect check-in, billing, room assignment, guest communication, or service recovery. When an alert is visible, the agent should pause and review it before proceeding. If the alert is unclear or appears outdated, ask a supervisor or manager before disregarding it. A missed alert can easily create a guest-facing issue that could have been prevented.

When an action is completed, documentation should reflect what was done. If the item remains pending, the shift handoff should explain what still needs attention, who is responsible, and whether the guest has been informed.

Room assignment should be intentional whenever possible. Agents should use visible guest information to support appropriate room blocking, especially for elite guests, VIPs, special requests, accessibility needs, long stays, prior service concerns, and survey-prone arrivals. When availability allows, the team should consider room condition, room location, guest preference, and recent inspection history before assigning a room.

Room blocking is also a communication tool. If a reservation needs a specific room type, should not be moved without manager approval, or has a special request that cannot be guaranteed, the reason should be documented. The PM team should not have to guess why a room was assigned or why it should remain blocked.

If a room cannot be assigned according to the guest’s preference or request, the team should prepare clear language for check-in. It is better to acknowledge the limitation professionally than to appear unaware of the request.

Back-to-back reservations and multiple reservations should be reviewed before arrival because they can create unnecessary confusion at check-in, during the stay, and at Night Audit. Agents should identify whether the reservations belong to the same guest, whether the dates connect, whether the room type remains the same, and whether the reservations should be handled together according to property procedure.

If a guest has multiple reservations, the agent should review them carefully before discussing the stay with the guest. Confirm whether the guest expects to remain in the same room, whether payment and routing are consistent across the reservations, and whether any notes or alerts need to be carried forward. If something requires manager or supervisor direction, it should be handled before check-in whenever possible.

B2B or multiple-reservation concerns should be passed along clearly. The next shift should know whether the guest has been informed, whether the room assignment is protected, whether any reservation needs to be checked in, merged, extended, or monitored, and what still needs follow-up.

CA can help identify reservations that require closer billing review, but the agent must still verify the final setup in the appropriate system. During pre-arrival review, look for OTA indicators, rate codes that suggest special handling, comments about billing, group-related notes, direct bill references, award stays, comp rooms, or any instruction that changes who should be responsible for charges.

When CA reveals a billing concern, the agent should not assume the reservation is ready. The concern should be verified against the folio, routing instructions, payment method, authorization, and supporting documentation. If CA and Opera Cloud do not appear to match, escalate before check-in.

Billing-related notes should be included in the shift handoff when the setup is unusual, incomplete, pending manager review, or likely to affect the guest conversation. The goal is to prevent another agent from discovering the issue with the guest standing at the desk.

Guest experience notes should be reviewed with care because they can help the team avoid repeating prior concerns and create a more personalized stay. If a guest has shared preferences, past frustrations, celebration details, service recovery history, or other meaningful information, the team should use that information to support the arrival and stay experience.

The goal is not to make the guest feel watched or over-documented. The goal is to use available information thoughtfully. A guest who previously had a room issue may appreciate being assigned a room that has been carefully reviewed. A guest celebrating an occasion may appreciate acknowledgment. A guest with a known preference may appreciate not having to ask again.

Any guest experience action that still needs follow-up should be included in the shift handoff. If something was promised, requested, or escalated, it should not depend on memory alone.

CA review only helps the operation if the information is acted on or communicated. If the AM shift identifies an arrival concern that will affect PM check-in, it must be passed along clearly. If PM identifies a reservation issue that will affect Night Audit or the next morning, it must be documented. Information that stays in one person’s head does not protect the operation.

A strong handoff includes the guest or reservation affected, the issue found, what was reviewed, what action was taken, and what still needs attention. Avoid vague statements such as “check CA notes” without context. The next agent should understand why the note matters and what they are expected to do with it.

Escalate when CA shows conflicting information, unclear billing notes, unresolved traces, high-profile guest concerns, VIP issues, multiple reservations that may affect the stay, special requests the property may not be able to meet, or any arrival detail that could create a guest-facing problem. It is better to ask for direction before check-in than to apologize later for something the team could have reviewed in advance.

When escalating, be specific. Explain what you found in CA, what reservation or guest is affected, what action you believe may be needed, and what decision or support you are requesting. Clear escalation helps leadership respond quickly and prevents avoidable delays at the desk.

Before completing a CA review, ask whether the guest’s arrival is ready from both a service and operational standpoint. Have elite and VIP arrivals been identified? Have preferences, traces, alerts, notes, and billing concerns been reviewed? Have unusual reservations been escalated? Has anything pending been documented for the next shift? If the answer is no, the review is not finished yet.