Activating add-ons on Rezlynx
Activation is a supervised, reversible process. Nothing goes live until your own test cycle has passed, and every step below can be undone in minutes. Most properties complete the whole path inside one working day; complex chains usually finish within the same week.
- An active Guestline Rezlynx subscription with at least one property configured and taking bookings.
- Administrator rights to the Integrations / API keys area of your Rezlynx settings — typically the owner, general manager or IT lead.
- The permission scope list agreed at purchase (for example: availability read, reservations write, rates write, guest profile read). Each module page states its exact scopes.
- A named UAT contact — whoever will run the test reservations and sign off go-live.
The activation walkthrough
Each numbered stage maps to what you saw during checkout and correspondence. Your activation engineer stays with you from first key paste to final sign-off.
Mint a scoped key in Rezlynx
Sign in to your Rezlynx environment. Open Settings → Integrations → API keys and create a new scoped credential covering only the permissions listed on your module pages. Copy it immediately — Rezlynx displays the full value once.
Paste it into your client area
In the client area activation form, submit the key against the property it belongs to. We run a harmless read-only handshake through the official Guestline Rezlynx API to confirm reachability and scope fit. No passwords ever travel, and the handshake writes nothing.
Set preferences per module
Choose module behaviour: which room types the booking widget exposes, whether the rate engine proposes nightly prices automatically or queues them for approval, quiet hours for SMS, sender identity wording, and so on. Preferences are editable later without re-activation.
Run the supervised UAT cycle
Your engineer walks your UAT contact through the checklist below live. Any failure is diagnosed on the call or fixed by us before retest — nothing ships half-tested.
Sign off and go live
After the checklist passes, we flip activation outside booking peaks, confirm first real reservation round-trip within the hour, and remain reachable for the rest of that day.
Post-live review
A short review after seven days covers usage logs, error rates and any preference tuning you want — included in every licence.
UAT checklist — what we verify together
Nothing is marked done until these items have run clean on your own environment:
Test reservation round-trip
A booking made via the widget (or imported by sync) appears correctly in the Rezlynx diary with correct dates, party size, price and channel tag, then cancels cleanly in both directions.
Webhook receipt log check
Reservation events arrive in our webhook log within seconds, are acknowledged properly, and retry behaviour behaves as documented when an endpoint hiccup is simulated.
Sender ID verification
For SMS confirmations: carrier registration status confirmed for your brand name, a live text received on UK networks (test numbers excluded), and opt-out handling demonstrated end-to-end.
E-sign document filing
A registration card signed in a sandbox reservation files as a time-stamped encrypted PDF, surfaces with an arrival-screen completion badge, and consent flags land back in the Rezlynx guest record exactly as specified.
Rate-table writes under approval
If you license the dynamic engine: a proposed rate accepted once applies to the correct Rezlynx rate table rows, with the change visible and reversible in the audit trail.
Dashboards reconcile
Analytics tiles match your native Rezlynx reports for yesterday's figures within rounding, so trust in the numbers is established on day one.
Rollback and revocation
Every connector can be stopped without touching your PMS:
- Pause — toggle the module off in the client area; queued work drains gracefully and no further API calls are made.
- Revoke — the revoke switch severs our access instantly; pairing keys remain in your Rezlynx settings for you to delete there whenever you wish.
- Reactivate — resuming uses the same scoped key after a fresh handshake; no configuration is lost while paused.
- Data exit — cancellation triggers the documented deletion schedule within 30 days, confirmed in writing.
Rate changes pushed by the engine carry a reversible trail, so any accepted recommendation can be rolled back individually from your client area history.
Timeline expectations
Fast track — single property, modules purchased together, UAT contact available: same week, frequently same day. Morning starts help; we prefer not to activate over a Friday-evening peak.
Standard — two to three properties or mixed licence bundles: typically within five business days including one prep call.
Chain programmes — phased waves per property with central reporting between waves, scheduled alongside your operations calendar.
Migrations — legacy import projects run parallel to this path and are timed against your Guestline go-live plan rather than our queue.
Ready when you are
Browse the shop or ask an engineer anything before committing.
Prefer to talk it through? Contact the Leeds desk — replies within four business hours.