AI Phone System Features: Essential Guide for Restaurants

Featured Image for AI Phone Systems

TLDR: Restaurants need AI phone systems to handle the non-stop call volume that distracts staff and loses revenue. Key features to look for include 24/7 automated booking, conversational AI for menu questions, seamless POS integration, and robust reporting. Implementing this technology leads to significant labor savings and increased order capture, boosting overall profitability.

Table of Contents

Introduction: Why Restaurants Need Smart Automation

The restaurant business is exciting, but it’s also non-stop chaos.

Think about the busiest hour of your day—lunch or dinner rush. Your staff is running food, seating guests, and trying to manage the kitchen flow.

Now, imagine the phone starts ringing. And ringing. And ringing.

Every call takes an employee away from the floor, slowing down service for seated guests. Every busy signal or trip to voicemail means a potential customer is calling a competitor.

Every call takes an employee away from the floor, slowing down service for seated guests. Every busy signal or trip to voicemail means a potential customer is calling a competitor. This chaotic reality of high-volume phone lines causes staff overload. It results in busy signals or unanswered calls, directly translating to missed calls and lost revenue from reservations, takeout orders, and general inquiries (SourceName, SourceName, SourceName).

The Smart Solution

This is where advanced automation steps in.

AI phone systems revolutionize communication. They act as tireless, 24/7 intelligent assistants that ensure every single phone call is answered instantly.

They significantly reduce staff interruption. Most importantly, they capture those otherwise lost revenue opportunities—from a late-night order to a reservation booked after hours.

Real-world examples show the massive impact. Restaurants using this technology are saving hundreds of staff hours every month. They are also generating significant additional sales simply by never missing a chance to interact with a guest (SourceName, SourceName, SourceName, SourceName, SourceName).

Operators who have adopted these systems report huge wins: AI eases daily operations for 90% of users. It boosts revenue for 61% and improves the guest experience for almost half (SourceName).

This detailed guide will outline the must-have AI phone system features and the specific criteria for selecting a platform. We will show you exactly how to choose the right technology to optimize your kitchen flow and enhance the guest experience.

The Core Functions: Essential AI Phone Features

Modern AI-powered answering services go far beyond the old, clunky Interactive Voice Response (IVR) systems. You know, the ones that make you press “1” for this and “2” for that.

Today’s systems utilize sophisticated conversational AI. This means the software can talk and listen like a real human. It understands natural speech, adapts to context, and holds a real conversation.

This conversational AI is specifically tailored for the nuances of restaurant operations. It handles calls, manages bookings, and takes orders with high accuracy and flexibility (SourceName, SourceName, SourceName, SourceName).

When looking for the essential AI phone features, these core abilities are non-negotiable:

Reservation and Booking Management

One of the biggest time-sinks for busy staff is juggling reservations over the phone. A strong AI phone system completely automates this process.

Key Reservation Features:

  • 24/7 Automated Booking: The AI must handle bookings, cancellations, and modifications at any hour of the day or night, without requiring a single minute of human staff time.
  • Real-Time Availability Checks: The system instantly checks your current availability. If a requested time is full, the AI can suggest alternative times or dates automatically.
  • Waitlist Integration: If your dining room is full, the AI needs the ability to automatically place the caller on your digital waitlist. It can then send status updates via SMS (text message). This ensures customers don’t get frustrated and hang up when the restaurant is busy.
  • Confirmation and Reminders: Automated SMS or email confirmations and reminder messages are essential to actively reduce costly no-shows, protecting your revenue.

This automation organizes schedules, accurately records special requests (like needing a highchair), and optimizes table turns.

The impact is huge: AI enables 24/7 automated booking and waitlist management (SourceName). In case studies, systems have been shown to increase the number of covers (guests served) by up to 141% (SourceName, SourceName).

We see real-life wins everywhere:

  • The restaurant Dos Salsas booked over 5,800 reservations entirely through AI-handled calls (SourceName).
  • Systems like Yelp Host are capable of booking 2 a.m. reservations without ever sending a call to voicemail (SourceName).

How many times a day does your host or server stop what they are doing to answer a question about parking, happy hour, or if you serve gluten-free pasta? This disruption adds up.

Intelligent Information Dispatch:

  • Intelligent Menu Query Response: The AI should accurately answer detailed questions about specific menu items, specials, ingredients, allergens (like nuts or dairy), and pricing. It needs to access your live menu data.
  • General Information Dispatch: The system provides automated, instantaneous responses for common operational questions, such as:
    • Hours of operation (e.g., “Are you open on Sundays?”)
    • Precise location details
    • Parking availability
    • Dress code, or information about private dining rooms.
  • Dynamic Language Processing: Since customers call from different places and have different speaking styles, the system must use machine learning to adapt. It must be able to understand various accents, local terminology, and casual conversational styles, ensuring high comprehension every time.

By handling these repeated, low-value interactions, AI saves enormous amounts of staff time.

For instance, the Dos Salsas system fielded 41,000 calls that were answered using custom-built responses (SourceName, SourceName). Surveys show that 75% of restaurant operators desire AI specifically for handling these quick, consistent answers, ensuring the human staff can focus entirely on in-house guests (SourceName, SourceName).

Order Processing and Takeout/Delivery Coordination

For restaurants that accept phone-in takeout orders, the AI system becomes a highly accurate order-taker.

Order Management Capabilities:

  • Simple Order Capture: The AI must facilitate the capture of standard takeout orders directly from the conversation. This means understanding exactly what the customer wants, even if they speak quickly or use shorthand.
  • Automated Upselling: A crucial feature is the ability to increase revenue by automatically suggesting relevant add-ons or upsells. For example, if a customer orders a pizza, the AI should suggest a side salad, extra toppings, or a beverage bundle during the confirmation process.
  • Integration with Delivery Platforms: If you use third-party delivery services (like Uber Eats or DoorDash), the AI should seamlessly connect the customer to the appropriate channel. If the restaurant handles its own delivery, the system should be able to provide real-time order status updates.

Accuracy is paramount when dealing with food orders. AI captures simple takeout details with an impressive 96% accuracy (SourceName). Furthermore, the automated upsell feature can be incredibly effective, boosting the average order value by as much as 27%, raising it to around $52 per transaction (SourceName).

These sophisticated phone answering services handle unlimited simultaneous calls. This guarantees 0% missed orders, even during the Saturday night rush (SourceName). Consistent handling leads to reliable revenue; one example, Local’s Pub, saw 132% online order growth just from consistent AI call handling (SourceName).

Selecting AI Phone System: Operational Must-Haves

Once you understand the core features—reservations, menu answers, and order taking—it’s time to look deeper. You need to move past generic AI capabilities and focus on the operational and integration requirements.

These requirements define the difference between a simple, generic answering tool and the best AI phone for restaurants—one that truly integrates with your unique operational flow.

When selecting AI phone system options, prioritizing restaurant-specific integrations is key. This is what distinguishes top-tier tools from generic offerings (SourceName, SourceName, SourceName).

Integration Capabilities

A smart system doesn’t just talk to your customer; it must talk to your technology.

Essential System Links:

  • POS System Integration: This is perhaps the most critical link. The AI must connect directly with your existing Point of Sale (POS) system (like Toast, Square, or Aloha). This allows for automatic order entry and payment processing. Orders taken by the AI should transfer smoothly into the Kitchen Display System (KDS) without any staff having to manually punch in the details.
  • Reservation Platform Compatibility: You need guaranteed compatibility and real-time data sync with popular reservation platforms, such as OpenTable or Resy. If a reservation is booked on the phone by the AI, that table must be marked instantly as unavailable in your online system, preventing double-bookings.
  • CRM/Customer History Access: The system should access existing Customer Relationship Management (CRM) data. This allows the AI to identify repeat customers by their phone number. It can then tailor responses based on their past orders, recorded preferences (e.g., “Welcome back, we see you usually order the pasta special!”), or logged details (like known allergies or a preferred seating area).

Top systems leverage this integration to log preferences like outdoor seating or birthday recognition. Transcripts of AI conversations are kept, ensuring staff are informed and ready to provide personalized service (SourceName, SourceName, SourceName).

Customization and Training

Customers should feel like they are talking to an extension of your restaurant, not a robot. Customization ensures the AI is indistinguishable from your brand.

Customization Requirements:

  • Brand Voice Customization: You must have the ability to select a voice and tone that accurately matches your restaurant’s unique brand identity. A fine dining restaurant might want a polished, formal voice, while a casual burger joint might prefer a friendly, casual tone.
  • Easy AI Training/Updates: Restaurant operations change constantly—daily specials, seasonal menus, and special events. The platform must allow managers to easily input these changes. This ensures the AI’s knowledge base is always current and accurate, adapting via machine learning to handle new menu combos or promotions.
  • Handling Ambiguity and Escalation: Even the smartest AI can encounter complex, non-standard queries. The system must implement a clear escalation matrix. This means the AI efficiently recognizes when a caller has a difficult question (e.g., a media inquiry, a large catering request, or a specific complaint) and routes them immediately to the appropriate human staff member without delay.

Other usability features, such as multilingual support and advanced spam filtering, are also critical to enhance efficiency and ensure that only relevant, real customer calls reach your staff when necessary (SourceName, SourceName, SourceName, SourceName).

Determining the Best Fit: Practical Selection Criteria

When evaluating what to look for in restaurant AI, you need to look past the sales pitch. Focus on the underlying technology and how the system translates call volume into actionable data and proven financial returns.

The technical stability of the platform and the data insights it provides are what guarantee long-term success and ROI.

Scalability and Reliability

The system must never fail, especially during your busiest hours. Reliability is about guaranteed uptime and capacity.

Technical Must-Haves:

  • Architecture: The best systems utilize a robust cloud-based architecture. This means the system runs on the internet and doesn’t require any physical hardware (like a server box) inside your restaurant. This ensures high uptime, continuous remote updates, and zero physical maintenance required by your staff.
  • Handling Peak Volumes: The system must reliably handle potentially high concurrency. Concurrency means many people calling at the exact same moment. The AI must guarantee that peak service times do not result in dropped calls or busy signals. The goal should always be a 0% missed call rate.

This stability provides enormous operational benefits. Cloud-based architectures handle all concurrent calls without drops (SourceName, SourceName). This means your staff is no longer constantly interrupted.

Staff time savings from using AI can range anywhere from 45 hours to over 300 hours per month. This uninterrupted focus can result in kitchen productivity gains of up to 40% (SourceName, SourceName, SourceName, SourceName).

Reporting and Analytics

An AI phone system is more than just a call answerer; it’s a data collector. The insights it gathers can help you fine-tune every aspect of your business.

Data Requirements:

  • Key Performance Metrics (KPIs): The platform must provide detailed, easy-to-read metrics. You need to see:
    • Total call volume handled.
    • Common inquiry types (e.g., 60% of calls ask about directions).
    • Time saved by automation.
    • Order accuracy rates (should be 96% or higher).
    • Upsell success metrics (how often was the AI successful in selling an appetizer?).
  • Operational Feedback Loop: Require the ability to analyze conversational transcripts. By reading what callers ask, you can reveal gaps in your website FAQ or notice frequently misunderstood menu items. This data drives deeper operational tweaks and service improvements.

These data points provide powerful financial ROI metrics. AI systems have been shown to drive hundreds of thousands of dollars in new sales just from handling phone calls ($440,000 in one example) (SourceName, SourceName).

In specific real-world scenarios, restaurants have reported annual benefits of $118,800 from a combination of revenue gains and labor savings, positioning these systems as an essential revenue protector and operational optimizer (SourceName, SourceName, SourceName).

Conclusion: Transforming Restaurant Operations

Investing in a dedicated, sophisticated AI phone system for your restaurant is not merely purchasing new equipment. It is investing in guaranteed efficiency and a guaranteed level of consistent customer experience.

The days of staff juggling phones while trying to run food are ending. The modern restaurant relies on intelligent automation to manage the high-volume, repetitive tasks that drain time and distract valuable employees.

To recap, the critical AI phone system features for restaurants include:

  • 24/7 Automated Reservation Handling with real-time sync.
  • Conversational AI for accurate menu and FAQ responses.
  • Seamless POS and CRM Integration for personalized service and automatic order placement.
  • High Scalability and 0% missed call rates during peak hours.
  • Detailed Analytics to drive continuous operational improvement.

The chosen AI system acts as an indispensable operational partner, not just an answering machine.

The benefits are clear: Operators report that using AI eases daily operations for a vast majority of users (90%) and boosts revenue for 61% (SourceName).

Use this detailed feature checklist when you evaluate potential vendors. By focusing on these essential features, you will select the perfect system to transform your phone line from a source of chaos and lost revenue into a powerful, reliable engine for sales and efficiency.

Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link, Link,