Ticketing integrations let MARA push its automated service tickets straight into the tools your operational teams already use - so the maintenance and housekeeping teams don't need a MARA login.

Learn more in this video.

Ticketing integrations are only available once you have set up a PMS integration (the room-level data is what powers the tickets). You then add a ticketing integration on top.

Whenever a new housekeeping or maintenance ticket is created, MARA pushes it automatically into the connected system. (Only housekeeping and maintenance tickets are pushed.)

Notes:

Setup in your Account Settings is straightforward: enter the required credentials (e.g. a client ID and client secret, or for Flexkeeping an API key). Once validated, a few additional settings appear that you can adjust afterwards.

Flexkeeping example: you configure how maintenance and housekeeping tickets are assigned using assignment codes. You can use an existing code or ask your Flexkeeping support team to create new ones. We recommend dedicated codes such as "MARA repair" and "MARA housekeeping" so your teams immediately recognize a ticket that was created automatically from a review. The pushed ticket includes the title, the guest complaint, sometimes the AI recommendation, and the check-in/check-out dates.

Because tickets are generated from reviews, there is a natural delay: a guest checks out, gets their review request, leaves a review a day or two later, and the platform then takes a few days to publish it before MARA can analyze it and create a ticket. From checkout to a ticket in your system is typically 3–7 days, and can be longer if the guest reviews late.

As a result, the issue may already have been resolved. Make sure your teams know these tickets are MARA-generated (retroactive, from a review) so they verify whether the issue is still open rather than assuming it's new. Many customers add a triage step - routing all MARA tickets to one person who checks what already happened before reassigning to the right team.