Meetin.gs combines working booking pages and group polls with a clearly labeled roadmap for routing, team scheduling, reminders, integrations, and analytics.
Create your first meetingShare one polished link with live availability, buffers, limits, and custom questions.
Offer dates and times, collect votes, and see the strongest overlap without an account.
Match each visitor to the right teammate by region, specialty, ownership, or form answer.
Every invitee sees local time automatically, with daylight-saving changes handled safely.
Balance bookings across a team or require several hosts for collective events.
Add Google Meet, Microsoft Teams, Zoom, a phone call, or a physical location automatically.
Send confirmations, reminders, reconfirmation prompts, and follow-ups from one workflow.
Understand conversion, popular hours, lead time, no-shows, and team distribution.
Hide calendar details, define booking windows, and keep personal information private.
The availability workflow defines which choices are safe to offer.
The group-poll workflow collects preferences when one open slot is not enough.
The organizer publishes the choice. Meetin.gs records the response. Email and calendar files carry the result.
The directory combines working product paths with requirements pages because a complete scheduling system needs both an available core and a clear roadmap boundary. Use the status below when planning a rollout or comparison.
| Capability | Current status | What can be verified |
|---|---|---|
| Direct booking pages | Available core | Create a public page, reserve a slot, send configured email, download a calendar file, and cancel privately. |
| Group meeting polls | Available core | Offer options, collect participant availability, review overlap, finalize one time, and notify participants. |
| Website booking widget | Available core | Generate responsive iframe code, embed a booking form externally, retain a direct-link fallback, and book without third-party cookies. |
| Lifecycle email | Partly available | Confirmations, welcome email, and a deduplicated six-hour meeting reminder work with configured Resend credentials and the scheduled-email worker. Configurable sequences and follow-ups remain requirements work. |
| Connected calendars and conferencing | Requirements | Provider-specific data, permissions, ownership, lifecycle, failure, and acceptance criteria are documented. |
| Routing, teams, payments, analytics, and administration | Requirements | Workflow guides explain what must be deployed and tested before these capabilities should be promised. |
Look for the coordination step that consumes attention or produces unreliable meetings: checking conflicts, gathering group preferences, assigning a host, collecting payment, copying a video link, sending reminders, or returning the outcome to another system.
Define the event type, responsible person, participant, source of availability, public promise, required data, fallback, and success measure. A feature without an owner or failure path creates a new support obligation instead of removing work.
Publish the meeting, complete it while signed out, inspect confirmation and calendar output, then reschedule, cancel, finalize, or disconnect a dependency. Confirm that the same meeting identity and participant-facing details survive every change.
No. Every detail page carries an availability label. Requirements pages are useful for evaluation and implementation planning, but they are not live-feature claims.
Start with a one-to-one booking page and a group poll. Together they reveal how Meetin.gs handles organizer choices, participant effort, confirmation, calendar output, email configuration, finalization, and private cancellation.
Turn the required result into acceptance criteria, identify the account or provider dependency, name a failure owner, and request current production status before including it in a purchasing or rollout decision.
A feature list is a poor place to make a decision. If you already know the job, go straight to it: publish a one-to-one booking page when your availability is the constraint, or run a group availability poll when several people must agree. Both work today and need no account.
The scheduler comparison library tests twelve products against the same workflow, and the Calendly comparison is the one most teams start with. Use the scheduling overview to connect each capability to the workflow it supports.
Start from the audience rather than the feature: sales teams, recruiting, remote teams, and twelve other solutions each map the workflow, the metric, and the mistake to avoid. The Help Center then turns any of them into a task you can verify, and the integration directory documents what each connection would require.
The table above marks each capability as available or as a documented requirement. The editorial policy explains why unshipped capabilities are labeled rather than implied, and the free account guide explains the organizer workspace with no payment gate.
Start with the essentials and grow into team workflows when you need them.
Schedule free