# See Crewsheet in action — 15 minutes with Peter Schrader

> A quick walkthrough of how Crewsheet uses SMS to keep crews, dispatch, and the office on the same page — no app to install, no logins for the field. We'll show how jobs, timecards, and daily updates flow in and out by text, then answer whatever's most relevant to your operation. Best for: GCs, subs, and logistics teams running 10+ field workers who are tired of chasing texts, paper tickets, or app adoption. Come with: a rough sense of your current workflow (how dispatch reaches the field today) and one or two pain points you'd want a tool like this to solve.

- Host: Peter Schrader
- Duration: 15 min
- Location: Google Meet
- Host time zone: America/New_York
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/peter-schrader-nlnj5x/crew-sheet-in-action
- Event type id: 5623403

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=5623403&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": 5623403,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "Company-Website": "…",
    "notes": "…",
    "Company": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address), `Company-Website` (Company Website)
- Optional fields: `notes` (Additional notes), `guests` (Add guests), `Company` (Company Name)
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.
