Write down the action and the result
A check-in event, a wake-up request and a room-charge posting are different requirements. For each one, identify the source system, the receiving system, the information exchanged and the confirmation staff should see.
Ask the PMS provider which interface is available for your installed version, whether an additional licence or middleware is required, and who will configure and support it. Include those dependencies in the quote.
What the 3CX documentation establishes
3CX documents Mitel SX2000 and Fidelio integration paths. Its documentation says the Mitel path has no room-call billing interface; the Fidelio path provides billing information. That distinction matters if posting charges is a requirement.
These are vendor-documented capabilities, not confirmation of your PMS configuration or a ScandiTech-tested pairing. Do not infer compatibility with a cloud PMS, a newer release or a similarly named product without verification.
Turn compatibility into an acceptance record
Record the versions and interface, the workflow tested, expected and observed results, limitations, test date and responsible people. Keep vendor documentation and property test results as separate evidence.
Test a representative room through its whole guest cycle. Include failed or delayed messages, a room move if required, and what staff should do while the link is unavailable. Never test with real guest details when a test record will do.
- Product and version on both sides, including any middleware.
- Required licence, reachable interface and access permissions.
- One pass/fail result for each agreed operational workflow.
- Documented fallback and a retest after a relevant software upgrade.