> ## Documentation Index
> Fetch the complete documentation index at: https://restaurants.poly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> This article covers the main limitations of your PolyAI agent. 

# Limitations

Your PolyAI agent is designed to handle the majority of reservation and FAQ-related interactions. However, there are certain actions it cannot perform.

<Tabs>
  <Tab title="Reservation limitations">
    ## 1) Reservation-related requests the agent cannot perform

    <AccordionGroup>
      <Accordion title="Modify or cancel experiences">
        The agent cannot modify or cancel bookings related to OpenTable experiences.

        If a guest requests changes to an experience booking, the call will be transferred to your designated transfer number.
      </Accordion>

      <Accordion title="Modify seating selection">
        The agent cannot change the seating area associated with an existing reservation.

        If a guest requests a change in seating preference, the call will be transferred.
      </Accordion>

      <Accordion title="Modify the booking time for guests running late">
        If a guest indicates they are running late:

        * If they are running **15 minutes or less late**, the agent will inform them that their table will be held.
        * If they are running **more than 15 minutes late**, the call will be transferred.

        The agent cannot modify the booking time in OpenTable or apply a “late” tag to the reservation.
      </Accordion>

      <Accordion title="Re-trigger the OpenTable booking confirmation text message">
        The agent cannot manually re-send an OpenTable confirmation SMS.

        If a guest requests that their confirmation message be re-sent, the call will be transferred.
      </Accordion>

      <Accordion title="Add guests to a waitlist">
        The agent cannot add guests to an OpenTable waitlist.

        If a guest requests to be placed on a waitlist, the call will be transferred.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="General limitations">
    ## 2) General functional limitations

    <AccordionGroup>
      <Accordion title="Dining area selection during booking">
        The agent does not proactively ask guests to choose a dining area during the reservation flow.
      </Accordion>

      <Accordion title="Speaking or understanding other languages">
        Currently, the agent is able to understand and respond in English only.

        If a guest begins speaking another language, the agent will inform them accordingly.
      </Accordion>

      <Accordion title="Collecting email addresses during booking">
        The agent does not collect email addresses during the booking flow.
      </Accordion>

      <Accordion title="Looking up reservations by email address">
        The agent cannot search for reservations using an email address.

        Instead, it will ask for the mobile phone number associated with the booking.
      </Accordion>

      <Accordion title="Passing the 2% OpenTable service charge on to guests">
        Guests will not be charged the OpenTable service fee when making a reservation through the agent.
      </Accordion>

      <Accordion title="Multiple transfer destinations per site">
        Each restaurant site currently supports a single transfer destination.

        The ability to configure multiple transfer numbers per site will be available in the future.
      </Accordion>

      <Accordion title="Sending FAQ-related text messages">
        The agent cannot send text messages containing FAQ-related information.
      </Accordion>
    </AccordionGroup>
  </Tab>
</Tabs>