# TheFork > **Who is this for?** This integration is for restaurants that take reservations through TheFork (TheFork Manager). If you don't use TheFork, you can skip this page. > > Use a different reservation system? Anything with an API can still be connected: see [Connecting a Tool We Do Not List](connecting-other-tools.md), which covers custom functions, the API and webhooks. > **Availability.** The TheFork connection is built, but it is not switched on yet. It runs on TheFork's partner API, and TheFork issues those partner credentials only after approving a partnership, so the TheFork card stays hidden until that approval comes through. There is no date to give you yet — if you run your reservations in TheFork and want to know the moment it opens up, send us a note via [email support](mailto:hi@dmchamp.com). TheFork is the reservation platform behind thefork.com, used by restaurants across France, Spain, Italy and other European markets for online bookings and table management. Connecting TheFork to DM Champ lets your AI Agent check real availability, book a table, and change or cancel a reservation for a guest, right inside the WhatsApp, SMS, Instagram or website chat the guest is already in. --- ## What the AI Can Do With TheFork Once connected and picked as the booking provider on an AI Agent, the Agent can: - **Check bookable times** for a date and a party size against the restaurant's live TheFork availability, and look across a range of dates to tell a guest which days still have tables. - **Flag what a time costs before booking it.** If a slot needs a credit-card guarantee, or is only bookable together with a particular offer or set menu, the Agent says so instead of quietly booking something else. - **Book the table** with the guest's name, email, party size, date, time and any special request they mention. - **Find the guest's own upcoming reservations** so it can quote or act on one. On WhatsApp and SMS it looks them up by the phone number the conversation is on; on other channels it only knows about reservations that were made in that same chat. - **Change** the date, the time or the party size of a reservation. - **Cancel** a reservation. Your team sees every one of these in TheFork Manager like any other booking, listed with **TheFork Manager API** as the channel it came from. ### Good to know - **Some reservations come back "on request".** The restaurant confirms those later rather than the table being held straight away, and the Agent tells the guest exactly that instead of promising a confirmed table. - **Times that need a deposit or a card imprint can't be booked in chat.** The Agent explains why and sends the guest to you or to your TheFork page to finish it there. - **Reservations only, not the menu.** See [Menu Questions](#menu-questions) below. --- ## Where the reservations show up Every reservation the Agent makes also appears on your **Appointments** page with a THEFORK badge, so you see it next to your other bookings. TheFork stays the system of record for the guest: TheFork sends its own confirmation email, so DM Champ does not send a second one, and these reservations are not copied to Google Calendar. Your restaurant's calendar is TheFork Manager. --- ## Connecting TheFork > **Before you start:** your restaurant needs the DM Champ partner enabled on its TheFork account. That is something TheFork switches on for the restaurant; ask your TheFork account manager or TheFork support for it. Until it is done, TheFork does not let us reach the restaurant and the Restaurant ID step below stops with a message saying so. 1. In the left sidebar, click **Settings** (gear icon). 2. In the Settings sidebar, under the **Integrations** group, click **Booking & Calendar**. 3. Find the **TheFork** card and click **Add restaurant**. 4. Paste your **Restaurant ID** and click **Verify**. This is the long identifier TheFork gives your restaurant (a UUID, a string of letters, numbers and dashes); you'll find it in TheFork Manager, or ask TheFork support for it. We check that the restaurant is reachable before going on. 5. Give the restaurant a **name** (this is what you'll see in the list and what the AI calls it), and save. You can add several restaurants this way, one per TheFork Restaurant ID: click **Add restaurant** on the connected TheFork row for each one. The AI books at the active one; pause the others. ### Pausing or Removing a Restaurant Each connected restaurant has its own **Pause** and **Remove** buttons on the Booking & Calendar page. Pausing stops the AI taking reservations for that restaurant while leaving it set up; removing deletes it entirely, though you can add it back any time with the same ID. --- ## Telling your AI Agent to book with TheFork 1. Click **AI Agents** in the sidebar and open the Agent. 2. Go to the **AI Abilities** step and find the **Bookings** card. 3. Turn on **Let this agent book appointments**. 4. Click the provider picker, choose **TheFork**, and pick which of your connected restaurants this Agent books for. No event type is needed: TheFork brings its own availability, opening hours and table plan. --- ## How a booking conversation goes 1. The guest asks for a table. The Agent asks for the date and the number of guests, and a preferred time if they have one. 2. The Agent checks TheFork and tells the guest what is bookable. If nothing fits that day, it can say which nearby days still have tables. If the time they want needs a credit-card guarantee, or belongs to a particular offer or set menu, the Agent says so before booking. 3. The guest picks a time and gives their name and email. The Agent books the table and confirms it, or explains that the restaurant still has to confirm it when TheFork returns the booking as a request. 4. Later, the guest can ask the same Agent to change the day, the time or the number of people, or to cancel. Times are always the restaurant's local time. --- ## Menu Questions The TheFork connection covers reservations; it does not read your menu. To let the AI answer menu questions: - **Add the menu to the knowledge base:** put your dishes, prices, allergen notes and daily specials in your AI Agent's FAQs or knowledge sources, and the bot answers "What vegetarian options do you have?" from there — see [Managing FAQs](../ai-automation/faq-management.md). - **Send the menu as a file:** upload the menu PDF or image to the media library with a "when to send" note, and the bot sends it when a guest asks for the menu or price list. --- ## Tips for Restaurants - **Fill in your phone number and website** in your account and on the restaurant, so that when the AI has to hand a guest over (a slot that needs a deposit, a change the restaurant has to make), it gives them a real way to reach you. - **Add operational FAQs** to your AI Agent's knowledge base: hours, parking, private dining, allergen policies, dress code — see [Managing FAQs](../ai-automation/faq-management.md). - **Use tags** to segment your guest list — for example "wine-lover", "birthday-celebration", "large-party" — and send targeted broadcasts to each segment. --- ## Next Steps - [AI Agents](../ai-agents/ai-agents.md) — configure your restaurant's AI Agent. - [Booking System](../appointments/booking-system.md) — how bookings work across providers. - [Managing FAQs](../ai-automation/faq-management.md) — add restaurant-specific questions and answers.