Pro’s guest-review workflow is tied to an eligible completed booking. A room testimonial entered manually and a review submitted through a guest invitation are different sources; do not present arbitrary text as verified guest evidence.
Invite an eligible guest
Use a legitimately entitled test environment first. Review invitations require a booking in Checked Out state. Confirm the intended recipient and the hotel’s communication settings before sending an invitation. Use synthetic mail addresses during regression.
The guest follows the invitation link and submits the supported rating and content form. Overall ratings must be from 1 to 5. For the room-level workflow, the submitted item set must match the eligible booked items before the invitation is consumed. An expired, invalid, already used or ineligible invitation must be investigated rather than replaced with an unrestricted public submission URL.
Moderate submitted content
- Open the Pro Reviews administration screen with the required permission.
- Read the submitted review and inspect its booking association and current state.
- Approve or reject it through the supported moderation action. Only submitted reviews are eligible for this moderation step.
- Reload and check the public room presentation. Pending or rejected content must not be treated as an approved public review.
The theme can style the approved review presentation; it should not decide verification, invent ratings or query private review/guest data directly. A missing review section can reflect no approved content or unavailable Pro capability rather than a layout defect.
Verify and recover
Test invitation, submission, moderation and public display separately. Sending or queuing an invitation is not proof of inbox delivery. Check a denied submission and ensure it creates no unauthorized review; do not run this test against a real guest’s link.
If display is stale, first confirm the saved moderation state, room association and active feature, then inspect page/cache behavior. Preserve review history and the original invitation evidence. Do not publish private booking codes, guest contact details or invitation tokens in screenshots or support reports.
