# OpenXCEL AI Systems Mapping Session with Ahmad Bukhari

> Your AI system. Owned by you. OpenXCEL AI gives your business its own AI system, built around your company knowledge, connected tools, workflows, and permissions. In this 25-minute session, we will explore how OpenXCEL AI could work inside your company: what the system should remember, which tools it should connect, where specialized assistants or automations would help, and which actions should remain under human approval. Bring your current setup, an example of work you want the system to handle, or simply the business outcome you want. You will leave with a clear first implementation plan covering scope, ownership, and next steps. The session is complimentary. No generic pitch deck. No obligation.

- Host: Ahmad Bukhari
- Duration: 25 min
- Location: Zoom Video, Google Meet
- Host time zone: Asia/Karachi
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/ahmad-bukhari/revenue-handoff-map
- Event type id: 6348711

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=6348711&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": 6348711,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "bookingFieldsResponses": {
    "broken-process": "…",
    "people-and-tools": "…",
    "business-result": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address), `broken-process` (Which process or handoff is breaking?), `people-and-tools` (Which people and tools touch it today?), `business-result` (Which business result is affected?)
- Optional fields: none
- `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.