{"id":2070,"date":"2026-09-28T14:14:18","date_gmt":"2026-09-28T08:44:18","guid":{"rendered":"https:\/\/www.geedesk.com\/blog\/?p=2070"},"modified":"2026-09-28T14:14:20","modified_gmt":"2026-09-28T08:44:20","slug":"reassign-hotel-tickets-on-the-go-with-geedesk-android-app","status":"publish","type":"post","link":"https:\/\/www.geedesk.com\/blog\/reassign-hotel-tickets-on-the-go-with-geedesk-android-app\/","title":{"rendered":"Reassign Hotel Tickets on the Go With Geedesk Android App"},"content":{"rendered":"\n

<\/p>\n\n\n\n

Tickets do not always land with the right person. A staff member goes off shift, gets pulled into something urgent, or the request simply belongs to a different department. When that happens, the ticket sits idle and the guest or the task waits.<\/p>\n\n\n\n

Over time, this is one of the small operational gaps that adds up across a busy hotel day. A complaint raised at the front desk, a maintenance request from housekeeping, a guest request that needs a specific department to act on it. When the wrong person holds the ticket, nothing moves.<\/p>\n\n\n\n

Geedesk is a cloud-based hotel complaint and request management platform that helps hotels track and resolve every request through one system. Staff raise tickets, the platform assigns them, and the right person gets notified. When a ticket needs to move to someone else, the reassign feature handles it in a few taps directly from the Android app.<\/p>\n\n\n\n

Here is how it works.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

One Setting That Controls Everything<\/h2>\n\n\n\n

Before you start reassigning tickets, check one setting in your Rule Engine. This setting decides who shows up in the reassign dropdown.<\/p>\n\n\n\n

Go to Admin<\/strong>, open Rule Engine<\/strong>, and look for Reassign Tickets to All<\/strong>.<\/p>\n\n\n\n

\"\"<\/figure>
\n

Turn it on and the dropdown shows every user on the platform, whether they are on shift or not. Alternatively, leave it off and the dropdown shows only users from the relevant department who have their attendance active.<\/p>\n<\/div><\/div>\n\n\n\n

Most hotels leave this off. That way, tickets only move to staff who are actually present and available to act on them. However, if your team needs more flexibility, turning it on gives managers full visibility across all users.<\/p>\n\n\n\n

How to Reassign a Ticket<\/h2>\n\n\n\n

To get started, open the ticket you want to reassign and go to the Ticket Detail page. Find the Reassign To<\/strong> option, tap the dropdown, and select the person you want to hand it to. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Geedesk then moves the ticket immediately and sends the new assignee an SMS so they know something is waiting for them.<\/p>\n\n\n\n

The whole thing takes under a minute.<\/p>\n\n\n\n

Nothing Gets Lost in the Handover<\/h2>\n\n\n\n

The new assignee does not start from scratch. In fact, they can see the full ticket history, including what the request is about and everything that has happened so far. As a result, the context travels with the ticket.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

On the other side, the original assignee no longer sees the ticket in their active queue. The handover is clean and therefore there is no risk of two people working on the same request.<\/p>\n\n\n\n

When Reassignment Actually Helps<\/h2>\n\n\n\n

The most common situation is a mid-shift absence. A staff member calls in sick or leaves early and their open tickets need to go to someone who is present. Consequently, reassignment handles that without any back-and-forth.<\/p>\n\n\n\n

It also comes up when a request turns out to need a different skill set or a more senior person to resolve it. Rather than the original assignee trying to manage something outside their scope, they hand it off and the right person takes over.<\/p>\n\n\n\n

Furthermore, for teams that reassign frequently, enabling Reassign Tickets to All<\/strong> in the Rule Engine removes the department filter and gives managers more room to move tickets wherever they need to go.<\/p>\n\n\n\n

Why This Matters for Hotel Operations<\/h2>\n\n\n\n

In a hotel, requests do not wait. A guest complaint that sits unresolved for an extra hour affects the stay. Similarly, a maintenance issue that nobody picks up affects the next room turnover. Keeping tickets moving is not just about internal efficiency. In fact, it directly affects what the guest experiences.<\/p>\n\n\n\n

Geedesk gives hotel teams the tools to make sure every ticket reaches the right person and stays visible until it is resolved. Reassignment is one part of that. Beyond that, the broader platform covers automatic assignment, escalation policies, department-level tracking, and a manager dashboard that shows everything happening across the property in real time.<\/p>\n\n\n\n

Moreover, the Android app brings all of that to the floor. Staff and managers do not need to be at a desk to act on a request. Instead, they can open a ticket, check its status, or move it to someone else from wherever they are on the property.<\/p>\n\n\n\n

Want to see how Geedesk works across your property? Book a demo<\/a> and we can walk you through it.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Tickets do not always land with the right person. A staff member goes off shift, gets pulled into something urgent, or the request simply belongs to a different department. When that happens, the ticket sits idle and the guest or the task waits. Over time, this is one of the small operational gaps that adds […]<\/p>\n","protected":false},"author":5,"featured_media":1996,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[39,28,14],"tags":[],"class_list":["post-2070","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-features","category-geedesk","category-product-update"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts\/2070","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/comments?post=2070"}],"version-history":[{"count":1,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts\/2070\/revisions"}],"predecessor-version":[{"id":2075,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts\/2070\/revisions\/2075"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/media\/1996"}],"wp:attachment":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/media?parent=2070"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/categories?post=2070"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/tags?post=2070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}