Meeting Types

Meeting types are named sets of scheduling defaults — duration, time options, time-of-day windows, follow-up cadence, buffers, and conferencing provider — that Skip applies when scheduling. Every workspace has a Default meeting type seeded automatically, and admins can add more for the distinct kinds of meetings their team runs.

Skip currently applies your Default type’s settings to every meeting. As you build out your catalog, Skip will learn to match meeting names in email — “discovery call,” “onboarding,” “demo” — and apply the right type’s settings automatically.

When to use meeting types

Meeting types let you stop repeating scheduling instructions in every email:

• Different durations per meeting kind — Discovery calls are 30 minutes, demos are 45, onboarding is 60. Set each as its own type and Skip applies the right duration when matching kicks in.
• Different time windows per meeting kind — Demos only on weekdays 10–4. External calls outside core hours. Each type carries its own preferred windows.
• Different conferencing per meeting kind — Internal syncs use Google Meet, external demos use Zoom. Pick the provider once on the type instead of asking Skip every time.

The Default type

Every workspace has a Default meeting type, seeded when the workspace is created. Default is the fallback Skip uses whenever a more specific type doesn’t apply. You can edit Default’s settings — duration, slot count, follow-up cadence, and so on — but you cannot archive it. The archive option is hidden on Default’s row because removing it would leave Skip without a fallback.

Default applies to every meeting today. Custom types you add will take effect once Skip starts matching them by name.

Settings reference

Every field below is optional on a non-Default type. Unset fields fall back to Default. On Default itself, fields apply directly to all meetings until matched types take over.

Setting	What it controls
Duration	How long the meeting is, in minutes.
Time options per request	How many time slots Skip offers in each scheduling email. More options give participants flexibility; fewer make a tighter ask.
Earliest / Latest time	The preferred time-of-day window for this meeting type.
Days of the week	Which days Skip will offer for this meeting type.
Follow-up attempts	How many follow-up emails Skip sends if scheduling participants don’t respond. “Off” means none. This is scheduling follow-ups, not post-meeting check-ins.
Buffer before / after	Padding around calendar events for this meeting type. Skip won’t offer a start time within the buffer of an existing event.
Conferencing provider	Which video link to attach (Google Meet, Zoom, Microsoft Teams).

Meeting type settings take precedence over member-level scheduling preferences (set per user under Settings > Preferences) when both are configured. If a meeting type sets a 30-minute duration, that wins over a member’s 25-minute default.

Creating, editing, and archiving

Meeting types are managed under Settings > Meeting Types. Workspace admins have access; regular members do not see the page.

• Create — Click New Meeting Type. Give it a clear name and an optional description. The description helps Skip match meeting requests once matching activates, so be specific: “First call with a new prospect” is more useful than “Sales.”
• Edit — Click any non-archived row. Changes apply to future scheduling requests; meetings already in progress finish with their original settings.
• Archive — Use the … menu on any non-Default row and pick Archive. Archived types stop being used; Skip falls back to Default for any conversation that previously matched.
• Restore — Toggle Show archived above the table to see archived types. Use the … menu and pick Restore.

The Default row is editable but cannot be archived.

See also

• Smart Defaults — The workspace-wide defaults Skip applies when no other settings are set
• Teams — Group members so Skip can schedule on behalf of a group; teams and meeting types compose
• Manage Preferences — Member-level scheduling preferences apply when no meeting type setting conflicts