{"id":97560,"plugin_id":"plugin_asdk_app_6ae8300d492c8191a072f79115188500","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-15T18:11:17.573Z","digest":"0b0bf4895cb4a14aad0b87f523a76145c06f6688aeb8f561c664a94351f656a8","against":null,"payload":{"description":"Use when a user asks whether bookings are ahead or behind, about booking pace or pickup, how many bookings came in per day or week, lead time (how far ahead guests book), or how demand compares with the same period last year or last month. Measures booking activity from WinCloud's reservation analytics.","included_files":[],"name":"wincloud-pickup-pace","skill_md_contents":"---\nname: wincloud-pickup-pace\ndescription: Use when a user asks whether bookings are ahead or behind, about booking pace or pickup, how many bookings came in per day or week, lead time (how far ahead guests book), or how demand compares with the same period last year or last month. Measures booking activity from WinCloud's reservation analytics.\n---\n\n# Pickup and pace\n\nFollow `wincloud-report-format`. Pace answers \"are we booking faster or slower than usual?\".\n\nResolve hotel names with `list_companies` before gathering data, and label every hotel by name in the output, as `wincloud` explains. For several hotels, use one row or series per hotel name.\n\n## Pickup: bookings made over a period\n\n1. Call `get_reservation_analytics` with `report` = `bookings`, `startDate`/`endDate` = the booking dates the user cares about (the date filter is the booking date). Add `roomTypeId` for one room type; ids come from `get_rate_plans`.\n2. Each row is one reservation still on the books (cancelled and no-show reservations are left out): booked date, arrival date, rooms (booked plus availed, as `wincloud` explains), lead time in days, ADR. Read every page and add up. Say if you stopped early.\n3. Total **room-nights are not available** from these rows (one row per reservation, not per night). Report **rooms** and **reservations**, not room-nights.\n4. Group by booked date for daily or weekly pickup; by arrival month for what the bookings are for; by lead-time band (booked after arrival, 0–7, 8–14, 15–30, 31–60, 61+ days) for how far ahead guests book.\n\n## Pace: compared with another period\n\n1. Pick two periods of equal length, the current one and the comparison (same dates last year, or the previous period). Say which.\n2. Compare like with like: bookings made in each period, **for the same arrival window** (for example, rooms in the last 30 days for next January, versus the same 30 days a year earlier for the January before). Filter rows by arrival date after reading them.\n3. Show the difference as a number and a percentage, and call it ahead or behind. If the base is small (under about 20 reservations), say the comparison is not reliable.\n\n## Show\n\n- **Headline:** rooms taken in the period, the change against the comparison, and the main reason visible in the data (a lead-time shift, a room type).\n- **Chart:** bars for rooms per day or week, with the comparison period as a second series (green).\n- **Second chart or table:** lead-time bands, and top room types or plans by rooms.\n- **Caveats:** the hotel, both periods, the date fields used, pages read.\n\n## Limits\n\n- The `bookings` report already leaves out reservations that are now Cancelled or NoShow, so its pickup is **net** of them. Don't subtract the `cancellations` report as well; that counts them twice. Gross pickup (including bookings later cancelled) can't be rebuilt, because cancellation rows carry no booked date.\n- No guest names or reservation numbers come back from analytics; use `search_bookings` for those.\n- Past trends don't guarantee the future. Don't call a pace figure a forecast.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}