Meetin.gs event types overview

Short answer: Understand reusable meeting templates, duration, location, and questions. Begin with “Name the outcome rather than using a vague label such as meeting.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Name the outcome rather than using a vague label such as meeting.Start with the intended outcome and the record that controls it.
Set a duration that includes the decision but avoids spare calendar time.Review every related setting before saving so one rule does not mask another.
Choose one location and ask only preparation-changing questions.Keep private data and guest-facing information clearly separated.
Save the pattern and run a complete guest test.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot Meetin.gs event types

These are the failures reported most often for this specific task, with the cause that explains 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.

Meetin.gs event types overview acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Name the outcome rather than using a vague label such as meeting.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Set a duration that includes the decision but avoids spare calendar time.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Choose one location and ask only preparation-changing questions.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Save the pattern and run a complete guest test.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Custom event types

Create focused templates for discovery calls, interviews, office hours, reviews, workshops, and recurring conversations. This page explains custom event types requirements. Confirm production availability before depending on this capability.

Review scope

Meetin.gs event types overview: frequently asked questions

Short answers to the questions organizers ask most about Meetin.gs event types.

What is an event type?

A reusable template for one kind of meeting: its public title, duration, location, availability rules, and the questions asked at booking. Publishing a link means publishing an event type.

How many event types should a host have?

Usually two to four. Each one you add is another set of rules to maintain and another decision for the invitee. Add a new type only when duration, location, or preparation genuinely differ.

What makes a good event type name?

The outcome, not the format. 'Project kickoff — 30 min' tells an invitee what will happen; 'Meeting' does not, and vague names measurably reduce completion.

Should I ask questions at booking?

Only questions that change your preparation. Every extra field costs completions, so three required fields beat eight optional ones.