Begin with the guide that matches the exact record or lifecycle step you are changing. Each article provides task-specific actions, verification, and troubleshooting so a saved setting is tested through the guest experience.

Public URLs remain stable so teams can bookmark, cite, and share the relevant guide.

Move from a setting to a verified result

Identify the meeting purpose, model real availability and ownership, complete the invitation as an external participant, and test confirmation, calendar output, email, reschedule, cancellation, and failure. Record the metric that matters after the meeting, not only how quickly a slot was selected.

Direct booking, group polls, poll finalization, calendar files, private cancellation, and email through configured credentials are testable now. Pages for connected calendars, routing, payments, administration, analytics, and native integrations explicitly identify themselves as requirements until production availability is confirmed.

A quick path through this directory

Find the controlling record

Begin with the Meetin.gs setup guide.

Follow one task

Use the unavailable-times checklist when the result looks wrong.

Keep proof

A test booking shows whether the setting creates the expected guest result.

Pick one question.Choose the page that matches the user's actual job.
Follow the related links.Move from concept to product and then to verification.
Record the outcome.Keep the result, failure, and owner in plain language.

Subject: the organizer or team.
Action: the scheduling rule or choice.
Result: one confirmed and usable meeting record.

Tip: read the short summary first. Open the detailed guide only when it matches your task.

How to troubleshoot without guessing

Begin with the exact public URL, event code, participant action, and time zone. Reproduce the result in a signed-out browser before changing settings. This separates an organizer-session assumption from what an invitee can actually see.

Check rules in dependency order

For an unavailable slot, inspect the organizer and event type first, then working hours, date overrides, minimum notice, booking horizon, buffers, daily limits, connected conflicts, and active reservations. For missing email, confirm the lifecycle trigger, recipient, delivery configuration, provider response, and suppression state.

Keep a before-and-after record

Record the controlling setting, expected public result, test input, actual output, and final fix. A screenshot can show the symptom, but the event code, time zone, and repeatable steps explain the cause. Never include passwords, private calendar text, management tokens, or unrelated participant data.

When to contact support

Contact support after the documented checks fail, when the same action creates inconsistent records, or when a privacy or security boundary may be involved. Include the smallest safe reproduction and the business impact. Use the Meetin.gs contact form for product support and the security page for responsible reporting guidance.

Do Help Center pages prove a feature is live?

No. Help content can document a working task or the acceptance criteria for early-access work. Availability labels and the current product scope determine whether a capability should be relied on.

What is the fastest useful test?

Create one small booking page or poll, open it while signed out, complete the participant action, and exercise one cancellation or finalization path. That test covers more risk than reviewing a saved configuration alone.

Frequently asked questions

Where should I start in the Help Center?

With the guide matching the record you are about to change — an event type, availability, a calendar connection, or a booking. Each guide includes the task steps, how to verify the result, and the failures specific to that task.

Why does my booking page show no available times?

Work through the rules in order: displayed time zone, conflict calendars, working hours, minimum notice, booking horizon, buffers, daily caps, then date overrides. The first rule that matches explains it.

How do I test a change safely?

Open the public link in a signed-out browser session. The organizer view cannot prove what an invitee sees, and most reported problems disappear once the page is checked as a guest.

What should I include when contacting support?

The public URL or event code, the action taken, the expected and actual result, the time zone, and roughly when it happened. Never include passwords, API keys, or private calendar contents.

Meeting Scheduler Help Center

Getting started with Meetin.gs

Meetin.gs event types overview

Meeting availability settings

Connect a calendar to Meetin.gs

Create and finalize a meeting poll

Create and share a booking link

Cancel or reschedule a booking

Time zone scheduling and daylight saving

Video conferencing scheduling

Meeting confirmations and reminders

Meeting routing forms overview

Configure round robin scheduling

Collective event scheduling

Group event scheduling and capacity

Embed Meetin.gs on a website

Paid meeting scheduling

Scheduling contacts and meeting history

How to use scheduling analytics

Meetin.gs administrator guide

Meetin.gs security and privacy overview

Meetin.gs API and webhooks

Troubleshoot missing available times

Troubleshoot scheduling email delivery

Meetin.gs profile and branding settings

No page matches that search.

How to use this help directory