Skip to navigation

Update Provider Priority Configuration

๐ŸŽฏ Configure Provider Priority & Routing

Update the provider priority configuration for a restaurant. This controls which booking providers are used, in what order, and under what conditions.

โš™๏ธ Configuration Options

Provider Priority

Set the order in which providers are attempted:

  1. Primary Providers (priority 1-3): First choice providers
  2. Secondary Providers (priority 4-6): Backup providers
  3. Fallback Providers (priority 7+): Emergency backup only

Conditional Routing

  • Time-Based: Use different providers for lunch vs dinner
  • Party Size: Route large groups to specific providers
  • Availability: Switch providers based on current performance

Fallback Strategies

  • Priority: Strict order based on priority numbers
  • Round Robin: Distribute load evenly across providers
  • Least Busy: Route to provider with best current performance

๐ŸŽฏ Best Practices

  • Primary Provider: Choose most reliable for main traffic
  • VAPI AI Calling: Use as fallback for restaurants without online booking
  • Load Distribution: Use round-robin for high-volume restaurants
  • Time Slots: Route dinner reservations to fastest providers

๐Ÿ”„ Dynamic Adjustments

The system can automatically adjust priorities based on:

  • Provider performance metrics
  • Real-time availability
  • Cost optimization goals
  • Customer satisfaction scores

Path parameters

restaurantIdstringRequired
Unique identifier for the restaurant

Request

This endpoint expects an object.
restaurantIdstringRequired

Restaurant identifier (must match path parameter)

providerslist of objectsRequired
Provider priority configuration
defaultProvider"opentable" or "vapi" or "tablecheck"Required
Default provider to use
fallbackStrategy"priority" or "round_robin" or "least_busy"Required
Strategy for provider fallback

Response

Provider priority configuration updated successfully
successbooleanOptional
messagestringOptional
restaurantIdstringOptional
updatedConfigobjectOptional
The updated configuration
timestampdatetimeOptional

Errors

400
Bad Request Error