Outcome and prerequisites
The goal is to offer only configured restaurants with availability for the same requested date, time, meal shift and party size when the preferred venue is full. The business needs active venues, sufficient settings access and correct service rules.
1. Configure eligible alternative venues
In the relevant online/platform settings, use the restaurant suggestions setting to choose which other venues are allowed as alternatives. Do not mix in unrelated accounts. Verify names, locations and active booking links.
2. Align service periods and party limits
Ensure each alternative is open for that meal shift and can accommodate the requested number of guests. Check breakfast, lunch, dinner or bar rules and closed days. Payment and cancellation terms may differ.
3. Test a genuinely full primary slot
Use a synthetic party and requested slot for which the primary restaurant is actually `FULL` or `BLOCKED`. The recommendation endpoint searches only under those conditions.
Before creating test reservations, check whether the test environment writes to live data. Do not create fictitious guest bookings in production.
4. Verify the exact time at the recommended venue
The recommendation service returns an eligible candidate when that exact slot is `AVAILABLE`. It does not automatically search all nearby times, so 7:45 p.m. availability does not imply success for an 8 p.m. enquiry.
5. Separate guest choice and booking confirmation
Displaying an alternative is not a reservation. After the guest chooses a venue and finishes that venue's booking flow, verify the restaurant, date, time, party size and confirmed status.
Pre-launch acceptance scenarios
Document synthetic requests and the results.
- Primary full, alternative available: only suitable recommendations appear.
- Primary available: do not show unnecessary alternatives.
- Primary and alternative full: never promise a table.
- Inactive candidate, wrong account or closed meal shift: exclude the venue.
- Requested party larger than candidate capacity: do not imply availability.
- Suggestion shown but no booking completed: do not count a confirmed booking.
How Rezervem supports the process
The API `GetSmartRecommendationsAsync` checks the primary slot, the configured `RecommendedRestaurants` set and the alternative slot status. Configuration supports the Manager booking workflow.
See how to redirect diners from a fully booked restaurant for the management perspective.
Troubleshooting
No recommendations: the primary may not be `FULL`/`BLOCKED`, candidates may not be configured, or none is available at the exact time.
No confirmed booking at the suggested venue: showing a recommendation and completing the reservation are separate actions.