# 20-Minute Venue Review with Eric Young

> Twenty minutes on your venue. No charge, no pitch. Tell me where the guest journey breaks down — the gate that backs up, the lot that under-earns, the egress that takes ninety minutes. I'll ask four or five diagnostic questions, then give you a straight answer on what I think the binding constraint is and what I'd look at first. Often it's something you can fix internally, and I'll tell you when that's the case. You'll get a one-page written summary within two business days, yours to keep and circulate whether or not we work together. Good fit: stadiums, arenas, theme parks, parking operators, and municipal mobility staff moving large crowds. Not a fit: residential permit programs, small-lot commercial parking, or site-specific security assessments — those aren't appropriate for an introductory call. Eric Young — 26 years in venue security and mobility operations, from Army Military Police to director level on a $2.5B entertainment campus.

- Host: Eric Young
- Duration: 20 min
- Location: Cal Video, Phone call
- Host time zone: America/New_York
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/curbtoseat/venue-review
- Event type id: 6775479

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=6775479&start=YYYY-MM-DD&end=YYYY-MM-DD&timeZone=<IANA time zone>
cal-api-version: 2024-09-04
```

The response is `{"data":{"YYYY-MM-DD":[{"start":"<ISO 8601 with offset>"}]}}`; no API key is needed.

## Book

```http
POST https://api.cal.com/v2/bookings
cal-api-version: 2026-02-25
Content-Type: application/json

{
  "eventTypeId": 6775479,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "Venue-or-organization": "…",
    "Your-role": "…",
    "Peak-event-attendance": "…",
    "What-s-not-working--One-or-two-sentences": "…",
    "notes": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address), `Venue-or-organization` (Venue or organization), `Your-role` (Your role), `Peak-event-attendance` (Peak event attendance), `What-s-not-working--One-or-two-sentences` (What's not working? One or two sentences.)
- Optional fields: `notes` (Anything I should read before we talk?), `guests` (Add guests)
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.
- `location` is optional; without it the booking uses the event’s first location.
