Close Civitatis tour dates or cut places when a guide is off

1. Log in to the Civitatis provider panel with your username and password; Civitatis says the panel is where you close and open dates and set quotas for each activity.
2. Close the affected dates on every activity the missing guide runs. A supplier with the same guide on a walking tour and a bike tour makes the change on both listings.
3. When only part of the team is missing, the provider panel quota for each day and time is the lever: a smaller group on the 16:00 slot instead of a closed day.
4. Then open the bookings in the provider panel for those days, because the date closure itself does not show who already booked the slots.
5. The pain is the second half: every existing booking needs a new date or a cancellation through Civitatis, and one forgotten slot means a traveler waiting at the meeting point.

Our guide Marta is off from 20 to 22 October: close the 10:00 bike tour on those days, keep the 16:00 tour open with 8 places instead of 14, and tell me who is already booked.

1. 01

   Match the absence to activities

   The agent reads your activities with list_activities and asks which ones the missing guide or boat runs, unless you named them. A guide who leads both the old town walk and the tapas tour means two calendars to change, not one.

2. 02

   Read the calendar before changing it

   get_availability for the affected days shows what is open now and the current quota per start time. The agent keeps those numbers, so it can put the 16:00 slot back to 14 places when the guide returns instead of guessing the old value.

3. 03

   Close or cut, slot by slot

   Slots nobody can run are closed with close_dates for only the listed start times. Slots a smaller team can still run get a lower cap with set_quota. If the quota you ask for is below the people already booked on a slot, the agent stops and asks instead of setting it.

4. 04

   List who is already booked

   list_bookings for the same dates and activity returns the confirmed travelers on the closed slots. The agent groups them per slot with head counts, so you can ask the Civitatis booking department to offer each one another date.

5. 05

   Check and plan the reopening

   A second get_availability call confirms the change landed. The agent reports the reopening date and the original quotas, so reopening on the 23rd is one sentence to your agent.

Bike tour of the old town, 20 to 22 Oct
Closed: 10:00 on 20, 21 and 22 Oct
16:00 cut from 14 to 8 places on 20, 21 and 22 Oct
Already booked on closed slots: 3 bookings, 7 people (Lucas Moreau x2 on 20 Oct, Hanna Berg x3 on 21 Oct, Paolo Ricci x2 on 22 Oct)
16:00 on 21 Oct already has 6 people, still under the new cap
To restore on 23 Oct: 10:00 open, 16:00 back to 14 places

• Civitatis dates and start times are set by the supplier, and travelers cannot change them themselves except on private services, so moving a booked traveler goes through Civitatis, not through the traveler.
• The Civitatis general conditions say that when a supplier has no availability, the traveler is offered another date where possible, and the booking is cancelled and refunded right away if the traveler does not answer within the supplier's deadline or refuses.
• Civitatis picks a main supplier for each activity with an automatic score that weighs availability, price, operational reliability, reviews and profitability, and that status can change as those metrics change.
• Civitatis connects with booking systems such as Bokun, FareHarbor, TourCMS, Rezdy and Turitop, and a Bokun supplier sends real-time availability to Civitatis from Bokun, so that supplier's calendar is driven from Bokun.

close_dates and set_quota change only your own Civitatis data and reach no one else, so they run without asking first.

Sources: Civitatis: provider FAQ (Spanish, panel, main supplier, connected systems) · Civitatis: general conditions of use (changes and supplier cancellations) · Bokun: becoming a Civitatis supplier (availability sync)

curl https://cotlet.dev/api/v1/civitatis/close_dates \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"activity_id":"act_48213","from":"2026-10-20","to":"2026-10-22","times":["10:00"]}'

{
  "activity_id": "act_48213",
  "activity": "Bike tour of the old town",
  "closed": [
    {
      "date": "2026-10-20",
      "times": [
        "10:00",
        "16:00"
      ]
    },
    {
      "date": "2026-10-21",
      "times": [
        "10:00",
        "16:00"
      ]
    },
    {
      "date": "2026-10-22",
      "times": [
        "10:00",
        "16:00"
      ]
    }
  ],
  "bookings_on_closed_slots": 0
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is civitatis_close_dates. Example data.

• Send guides a daily Civitatis booking list for tomorrow
• Answer Civitatis customer messages with AI drafts
• Request and reconcile your monthly Civitatis payment
• Civitatis API and MCP server: every tool
• All use cases