How should a restaurant set up and test Join?
First enable the correct venue's QR registration form, review its core guest fields and privacy explanation, and test the complete experience on a real phone before printing table cards. Rezervem Join provides the browser-based form; the restaurant's manager chooses the optional fields and signs off the configuration. A successful page load is not the same as a completed guest record.
A printed QR is not a finished deployment
A host team may receive a stack of new cards without anyone testing the final address. If the restaurant is wrong, the form is disabled or the wording is confusing, the problem appears during service. Give one manager responsibility for the printed URL, the on-screen venue identity and the final test results.
1. Confirm the venue and form availability
Scan the actual URL and check the restaurant name, selected language, visible logo and whether registration is enabled. A closed form should not accept a guest's details. Keep linked Rezervem registration and independent Connect QR paths separate because their permissions and backend records differ.
2. Review core and optional fields
First name, last name and phone are the core fields. Email, birth date, anniversary date and other supported inputs depend on the configured form. Ask why every optional field is required before making it visible. A short form is not only more welcoming; it is easier for the team to explain.
3. Test consent and telephone verification
Read the actual data-use explanation and commercial messaging choices. In applicable phone and consent scenarios, verify that the OTP step works and that the recorded permission matches the guest's choice. A previously verified grant may affect whether another SMS is needed. The independent Connect path has its own WhatsApp grant requirement.
4. Compare new and existing guest outcomes
Register a fictional new guest, then test using a controlled existing identity. Examine profile matching, supported optional-field behaviour and duplicate handling. Do not borrow a real customer's phone number for a demonstration or assume a repeat submission represents another newly acquired individual.
5. Test a configured gift separately
If the venue offers an eligible welcome benefit, verify both the registration and the gift issuance result. Check validity and repeat-scan behaviour. The success message for the form alone is not proof that an entitlement was issued, nor that it can be redeemed at every location.
6. Inspect the physical card and service explanation
Scan from the place where the card will be used. Check mobile text size, contrast, second-language content and the final registration response. Staff should be able to say that the card is for optional guest registration, not for viewing the menu or paying a bill.
How Rezervem supports the launch checklist
Rezervem Join handles registration. Gift handles eligible benefits and Connect supports separately permitted communication. Record which test guest, environment and employee verified each step, including expected failures, before moving the form into live service.
A final controlled failure test
Leave one required field blank and try an invalid phone format in a controlled test. Then check how the disabled-form state is presented. The guest should see a clear explanation rather than a misleading success screen. Document the actions the restaurant team can take if the service is unavailable.
Frequently asked questions
**Does Join require an app download?** No. The form runs in the phone browser.
**Are all QR consent flows identical?** No. Linked Join and independent Connect have different rules.
**Does a completed registration prove gift issuance?** No. Check the gift separately.
