An event type is a reusable meeting pattern: name, length, location, and the questions you ask. Set it once and every invitation inherits it. The event types page lists the requirements; the duration guide helps pick a length.
Before you start
- Name the outcome, not the format ("Onboarding call", not "Meeting").
- One length, one location.
- Only questions that change your preparation.
How to complete this task
- Name the outcome rather than using a vague label such as meeting.
- Set a duration that includes the decision but avoids spare calendar time.
- Choose one location and ask only preparation-changing questions.
- Save the pattern and run a complete guest test.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
Two event types offer the same times.
They share the same underlying availability. Give each one its own working window, notice, or daily cap, or the second will keep mirroring the first.
Invitees skip my custom questions.
Optional questions are usually ignored. Mark only the answers that genuinely change your preparation as required and delete the rest — three fields complete far more often than eight.
The duration looks wrong on the invitee's calendar.
Check whether a buffer is being added to the guest-facing length. Buffers should protect your calendar without appearing in the invitee's meeting duration.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
