# Positioning Assessment – results call with Peter Rochel

> Book the Positioning Assessment here and choose the date on which we go through the results together. How it works: you answer a few questions about your company and your market – from these, we build the questions we put to the answer engines. Once payment has been received, we measure across seven answer engines. You will have the report by the fourth working day at the latest, and in any case before our call. That is why the earliest date you can book is six days ahead. On the call, we go through it together: where you are named today, where you are not, who is named there instead – and what follows from that. If any of your answers is ambiguous, we will phone you briefly beforehand. Better to ask once than to measure the wrong market. What happens after you book is also set out in the brochure you can pass on (in German): https://oberwasser-consulting.de/positionsbestimmung/positionsbestimmung-danke/

- Host: Peter Rochel
- Duration: 45 min
- Location: Zoom Video, Cal Video, MS Teams
- Host time zone: Europe/Berlin
- Confirmation: Bookings are confirmed instantly.
- Payment: required, and collected on the booking page.
- Booking page: https://cal.com/peterrochel/positioning-assessment
- Event type id: 7217497

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=7217497&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": 7217497,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "telefon": "…",
    "firmierung": "…",
    "domains": "…",
    "region": "…",
    "sprachen": "…",
    "kategorie": "…",
    "reichweite": "…",
    "problem": "…",
    "ausloeser": "…",
    "personen": "…",
    "herkunft": "…",
    "verwechslung": "…",
    "empfohlen-von": "…",
    "notes": "…"
  }
}
```

- Required fields: `name` (your_name), `email` (Email address), `telefon` (Phone number in case we have questions), `firmierung` (What is your company called? Please include alternative spellings, the short form or any former name.), `domains` (Which web addresses are yours? Please include old sites, whether they are still online or not.), `region` (Where are you based, and where do your customers come from?), `sprachen` (What language do your customers search in?), `kategorie` (What would your customers say you are? Not your own description – the word someone uses when they look for you.), `reichweite` (Where do you want to be found?), `problem` (What do customers come to you with? Please put it the way they would say it themselves – not in technical terms.), `ausloeser` (What usually happens just before someone calls you?), `personen` (Which people should we include in the measurement? Answer engines often name people before they name companies. Up to three.), `herkunft` (What prompted you to book?)
- Optional fields: `verwechslung` (Do people confuse you with another company, or do you have sister companies?), `empfohlen-von` (If a recommendation or something else: who or what?), `notes` (Additional notes), `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.