Questions people actually ask

No. You get your own booking link (e.g. foglalas.meetply.com/fogaszat) that you can put in your Instagram bio or Google Business Profile. If you do have a website, you can embed it with a single line of code.

About 15 minutes: you add your resources (colleague, room, machine, bay), your weekly schedule, and your services with their duration. We can set up your first schedule for you on request.

They get a signed, one-time-use cancellation link - we never identify anyone by name or email. The slot reopens immediately on cancellation, and you're notified.

No. Availability is calculated server-side, at the moment of booking - so there's no double booking even if two people click at the same time.

Just like individual ones. You set a capacity on the service: 1 = one guest or one car, N = several can come. Same booking, cancellation, and calendar.

No. 14 days free, no card required. If you don't continue, your booking page closes, but your data stays and can be exported.

The interface is in Hungarian; English and German are already prepared. Let us know if you need them - we'll bring them forward.

Yes, the booking page is built for mobile: large touch targets, a sticky booking button, and it comes with a QR code too.

It calculates from your weekly schedule, your exceptions (time off, holidays), and your existing bookings. The guest only ever sees what's genuinely free.

Yes, if you set one. A service can have a duration and a displayed price - so the guest already knows the cost when choosing.

Yes, you can add custom questions to the booking form alongside name, phone, and email, plus request terms-of-service acceptance.

If you set it up that way, yes. By default it's automatic, but you can turn on approval so every booking waits for your yes.

They get a signed, one-time-use link in the confirmation email - we never identify anyone by name or email. You set the cancellation deadline.

The slot reopens immediately, and you're notified. That freed-up time can go to someone else - the cheapest revenue there is.

Yes. You add a phone booking from the calendar or list view, following the same rules as an online booking.

The booking page is built for mobile: large touch targets, a sticky booking button. It also comes with a QR code you can put on the counter.

Yes: your own link, name, logo, and services. Your notification emails' text can be yours too.

Yes. Every resource (colleague, room, service bay, machine, meeting room) has its own weekly schedule, with exceptions - time off, holidays, special openings. An exception overrides the schedule.

Yes: a minimum lead time (e.g. at least 2 hours ahead), a maximum booking horizon (e.g. 60 days), and a daily limit per service.

Yes, you can set a duration and a following buffer (cleaning, setup) per service, which the system factors into the available slots.

Yes. Every resource gets an ICS subscription and two-way Google Calendar sync, so bookings show up there too.

Yes, you can add or cancel bookings from the calendar or list view, following the same rules as an online booking.

Staff only sees their own bookings and schedule; admin sees everything. This permission is enforced by the server, not just hidden by the UI.

With a single script tag. The widget calls the exact same availability calculation and booking rules as the public page.

Yes. The REST API and the MCP layer run the same booking logic, so your own system - or an AI chatbot embedded on a website - can book too.

Online card payment, a deposit, or pay-on-site - you decide per service. Sending a payment link also works, and the invoice and receipt can be automated.

To the guest, the resource, and the admin on booking and cancellation, plus a reminder up to 24 hours ahead.

Your own subpage: foglalas.meetply.com/yourname. You choose the name, and it can be changed later.

No, you don't. The booking page works standalone, with its own branding - many businesses use only this.

When editing your profile, paste the link into the website field. That's it.

Yes, as a downloadable file. You can put it on the counter, in the shop window, or on your business card.

The interface is built specifically for mobile: large touch targets, a sticky booking button.

Then you can embed the same booking flow with a single line of code - the link keeps working regardless.

No. You just paste one line into your site's HTML; in most site builders that's a few clicks.

Yes, inserted into a custom HTML block. No separate plugin is needed.

Yes, it calls the same availability calculation and booking rules - there's no difference in behaviour.

No. The widget loads asynchronously and only renders once the visitor actually opens it.

Yes: colour, size, and whether it appears as a button or an embedded calendar.

No. One widget is enough, and the guest picks the service inside it - but it can also be narrowed down to a single service.

In settings, right next to the booking link. Available as both PNG and SVG.

Yes, the SVG stays crisp at any size - even for a poster.

Yes. You can generate a separate code for a specific service or colleague.

When you change the address, you need to download a new code - the old printouts work only as long as the old address does.

No, the phone's camera recognizes it.

By default yes, but you can override them - you know best when an exception is justified.

Yes, if you entered their email address or phone number.

No. Manual entry works from the exact same availability calculation.

The admin for any resource, staff for their own.

Yes, it appears in the booking's history.

Yes. A short consultation can have a different lead time and limit than a full-day job.

Self-service cancellation no longer works - the guest has to reach you through your listed contact details.

The guest immediately gets a "pending" confirmation, and you get a notification. Until you approve it, the slot stays reserved.

Yes. The system calculates with duration + buffer combined, so the next guest never runs into you.

Yes, you can cap how many bookings fit into a day, both per service and in total.

With manual entry, you decide - you can override the rule if a guest asks for something unusual over the phone.

As many as you want, but less is more: every extra field lowers the completed-booking rate.

Yes. You ask something different for a consultation than for a long treatment.

In the booking details and on the customer record.

Yes, individually per field.

Yes, a checkbox, with a link to the terms and conditions and the privacy notice.

That their request has arrived and is awaiting approval - not that the booking is confirmed.

Yes. Until you decide, no one else can take it.

You get a reminder. It can also be set to expire the request automatically after a while.

Yes. Some services need it, others would only be slowed down by it.

Yes, you can add a message, which the guest receives.

Weekly, biweekly, and monthly recurrence, with a set number of sessions or an end date.

The system flags it, and you decide: skip it, or move it to a different time.

Yes, the rest of the series stays untouched.

You typically set up the recurring series yourself - that way long-term commitments stay in your hands.

No. If a session doesn't fit, the system flags it right when you set it up.

With a signed, single-use token in the link. Not by name or email - so they can never access someone else's booking.

It can be booked again immediately. If there's a waitlist, whoever's on it gets notified.

Until the cancellation deadline you set. After that, they have to reach out to you directly.

It's better: the guest doesn't leave, they just pick a new time - the revenue stays.

Yes, immediately - and so does the colleague the booking belonged to.

Hungarian is complete. The English and German framework is ready, the text is being filled in - let us know if it's urgent.

Based on the visitor's browser language, but it can also be switched manually.

You provide those per language yourself - so no machine translation goes out under your name.

Yes, they go out in the language the guest chose.

Write to us and we'll take a look. The framework can handle any language.

No. It's the same service form - you just enter a number greater than 1 in the capacity field.

You hold it or cancel it - cancelling notifies everyone who already signed up. We don't automatically enforce a minimum headcount.

No. They only see the number of free spots; the participant list is visible only to you and your colleagues.

Yes, if you allow it - the number of spots to book can be set at booking time.

No, not if it's the same resource (room or instructor) - the system calculates from a shared calendar.

The first person to book opens the session and decides who else can join. Good for closed training groups or a company team.

Whatever you define: age group, skill level, weight class, language, or any other criterion.

You hold it with a smaller group, or cancel it - registrants are notified automatically.

Yes, at booking they see that their choice determines the group.

As the admin, you can override it at any time if it's warranted.

The Studio plan.

Instantly, sent the moment the booking is made.

Yes, an .ics attachment and a Google Calendar button.

The booking still stands. You can see it in the list view and reach the guest by phone.

Yes, both the content and the branding are yours to change.

Yes, and so does the colleague - toggleable per recipient.

24 hours by default, but it's adjustable. It can also differ per service if one needs more preparation time.

SMS works on a credit basis: sending one uses up a credit, while email is unlimited.

The guest, the resource (colleague), and the admin - each can be turned on or off individually.

Yes, both the content and the branding are yours. We don't send out a template with someone else's brand on it in your name.

Yes, an .ics attachment and a Google Calendar button - the guest can add it with a single tap.

The confirmation can't be delivered, but the booking still stands. You'll see it in the list view and can reach them by phone.

SMS runs on credits: each message is billed separately. Email, on the other hand, is unlimited.

Confirmations and reminders - toggleable per event.

SMS sending stops, but email notifications keep going without interruption.

Yes, wherever a missed appointment costs more than the message itself - typically for long, expensive jobs.

SMS is a one-way notification; they can cancel using the link inside it.

Yes, and more: per resource. A machine or a room can also have its own opening hours.

As an exception, with a date range. No available slot appears on the booking page for that period at all.

You set up two separate weekly schedules, and the system alternates between them. No need to open them up by hand.

Yes, a winter and a summer schedule tied to dates - the switch happens automatically.

Yes. 8-12 in the morning, 14-18 in the afternoon - the time in between can't be booked.

We suggest the Hungarian public holidays, but you decide - some businesses work the most precisely on those days.

Anything that can be booked: a person, a piece of equipment, or a room. A colleague, treatment bed, reformer machine, service bay, meeting room.

No. The number of colleagues who log in isn't limited - it's the number of resources that counts.

Yes. A teacher + a rehearsal room, a mechanic + a service bay: the slot is only free if both are free.

Each location's resources run on their own calendar, within a single account.

Yes, at any time. The slider also shows you right away what it means for the price.

You add an exception for it - it can't be booked during that time, while the other machines stay available.

By the calendar week number, but you choose the starting week.

Yes, per resource - even in opposite phase.

Yes, with an exception. An exception always outranks the schedule.

They only see the available time slots - they don't need to understand the rhythm.

Currently only the alternating two-week pattern is supported. If you need a three-week one, write to us - we're interested in the use case.

On the date you set, automatically - you don't have to remember.

They stay as they are. A season change only affects future open slots.

Yes, everyone can have their own seasonal schedule.

It currently switches between two schedules; if you need more, exceptions can cover it.

Yes, any time - the new schedule takes effect after saving.

Yes, as many as you need - the gaps in between won't be bookable.

Yes, but a schedule can be copied from one resource to another.

The exception. Time off or a holiday always overrides the weekly schedule.

Yes, if your calendar is synced.

A change doesn't delete bookings already made - those need to be handled manually.

Yes, if you allow it. Or you can let the system offer the earliest available slot instead.

Yes, the same service can take a different amount of time.

Yes, if that's how you work.

Assign it in one click - it becomes bookable with them immediately.

Of course - the system offers them based on available capacity.

As many as your day calls for - usually two or three is enough.

Yes, everyone can have their own time-of-day setup.

You can always override it with a manual booking.

No. The limit controls how many, this controls when.

No. It flags a conflict, and you decide: reschedule or cancel them.

We suggest Hungarian public holidays, but you decide whether you're working that day.

Yes, per resource or for the whole team.

Yes - an exception isn't only for closing.

As far as you want, there's no limit.

No. That time simply won't show up as bookable.

They can flag it from the staff view, and you approve it.

The system lists the conflicts so you can reschedule or cancel them.

Yes, the period can be set down to the hour.

Yes, in the team calendar.

No. You set it per service: some require a deposit, others are fine with payment on-site.

You decide on the refund according to your own policy - the system shows how much it is and which booking it belongs to.

Yes. You can send one for a phone booking or a business customer too, and the guest pays from there.

Yes, after payment. A receipt can also be issued if your business needs one.

You set it yourself - a fixed amount or a percentage of the full price, per service.

Card details are handled by the payment provider, not by MeetPly - we never store card numbers.

With the payment provider. MeetPly never stores card numbers.

Refunds follow your own rules; the system shows you the amount and the booking.

Yes, after a successful payment.

According to the payment provider's own settlement schedule - MeetPly doesn't hold it back.

Match it to the risk: 10-20% for a short session, up to half for a full-day job.

Your own rule decides. Many refund it if cancelled within the deadline, not otherwise.

Yes, a partial invoice - and another for the remainder at completion.

Yes, and it can be a fixed amount or a percentage.

For most providers it's the single most effective tool for cutting down no-shows.

You generate it from the booking, then send it by email, SMS, or message.

If you set it to, yes - and you're notified if it isn't paid in time.

Yes, the payment is recorded against the matching booking.

Yes, it can also be used to buy a pass.

Yes, by email after payment. You don't need to issue it manually afterwards.

Yes, if your business needs one - typically for payment made on-site.

The deposit gets its own document, and the remaining amount gets one at completion.

Yes, the period's documents can be exported all at once.

You keep your prices net, and VAT appears separately on the document.

The document tied to the booking can be voided, and it stays visible in the history.

Automatically, after a recorded in-person payment.

Yes, an invoice can still be issued after the receipt.

Yes, monthly receipts can be exported all at once.

If they ask, they get it by email.

No, it's generated within the system.

The booking page gets its own subpage. If you need your own domain, embedding the widget is the way to go.

SVG or PNG, transparent background works best.

Yes, your brand colour sets the colour of the buttons and highlights.

Discreetly, in the footer - the interface carries your own branding.

Yes, for services and for your introduction.

Yes, all four types - but whichever you don't touch keeps the proven default text.

Yes: parking, arrival, what to bring - this cuts down on phone calls.

Yes, in the header, along with your colours.

Yes, with separate text per language.

Emails go out in your name; the technical sender belongs to the system.

The admins, and the colleague the booking belongs to. Staff don't see other colleagues' customers.

An internal field on the customer record. The guest never sees it, and it never goes into an email.

A customer on the list can no longer book online. You can still add them manually if you want to.

Yes, any time. The data is yours - we don't lock it in.

No. Neither we nor the system - there's deliberately no customer marketing automation built in.

Yes, at the first booking. Next time, the system recognizes them by their contact details.

Yes, at the first booking - the system recognizes them by contact details next time.

Admins, and the colleague the booking belongs to.

No. Neither we nor the system does - there's deliberately no customer-marketing automation.

Yes, any time. The data is yours.

Yes, if someone booked with two different contact details.

One click next to the booking - the counter on the customer record increases automatically.

No, it's internal information.

No, that decision is yours. The system just shows you the number.

No. Cancelling within the deadline is normal behaviour - we track it separately.

Yes, in the reports, by service and by period.

Their online booking simply won't go through. We don't send a separate notification.

Yes, manual booking isn't blocked - the decision is always yours.

Any time, in one click.

No. The system shows the number of no-shows, but adding someone to the list is a human decision.

By the contact details on their customer record.

Never. The note is an internal field that never appears in any outgoing message.

Admins can, and so can the colleague the booking belongs to.

On a new booking, and when the booking is opened.

Practically none, but a short note is more useful.

CSV, which opens in any spreadsheet program.

No, export is free in every plan.

Yes, you still have access to data export for 30 days after it closes.

Yes, internal notes are exported as well.

Yes, by period, service, and colleague.

The connection with Google Calendar is two-way. Apple Calendar, Outlook, and any ICS-capable calendar can read bookings via subscription.

Yes, if you entered it in the synced calendar. The system treats that slot as busy.

No. They only see whether a slot is free or busy - never the details.

Yes, the sync runs per resource - so everyone sees their own on their phone.

The entry disappears from the synced calendar too - no blank appointment is left behind.

Yes, an .ics attachment and a Google Calendar button in the confirmation email.

Only that the given time is busy. We never show anyone the content of the event.

Yes, sync runs per resource.

Practically instantly, in both directions.

Yes, any time - after that only the MeetPly calendar stays live.

No, the subscription is read-only. Google sync is what you need for writing.

Depends on your calendar app's own settings, typically hourly.

In the resource's settings, under the calendar section.

Yes, as an .ics attachment in the confirmation email.

It's unique and unguessable; it can be regenerated if it ever leaks.

Only the admin. Staff see their own bookings, not the aggregated numbers.

Week, month, and a custom range, with comparison to the previous period.

Yes, based on recorded payments - it doesn't calculate from the listed price sheet.

Yes, broken down per resource and per service too.

Every booking automatically deducts one session. The guest can also see their own balance.

If you set it up that way, yes. You set the expiry date - and it can be extended.

You decide: it can be general, or restricted to selected services.

Yes, by card. For an on-site purchase, it can also be entered manually.

The booking page shows it when there's no open slot in the period they want.

Everyone is notified, and whoever books it first gets it. That's the fairest order.

Until the given period passes, or until they unsubscribe.

The Studio plan.

As many as you want. The number of users isn't limited and carries no extra fee - it's the number of resources that counts.

No. Staff only see their own bookings; all calendars are visible only to the admin.

Yes: the filtering happens server-side, not in the interface. What they can't see, they can't even request.

Yes, from the staff view. You then see it and can approve it in the team calendar.

Right now there are two roles: staff and admin. If you need finer-grained control, write to us - we're interested in the use case.

The admins, and the colleague the booking belongs to. No one else.

No. The number of users is unlimited - you only pay for bookable resources.

They can flag a change or time off; approval is yours.

No, only their own.

Yes, for their own resource.

Yes, the interface is built for mobile too, and their calendar can be synced.

Yes, the endpoints come with descriptions and examples. If something's missing, write to us - developer feedback is the fastest way to get it added.

A standard through which AI assistants can natively call the booking operations, without writing a separate integration.

No. The same logic runs: lead time, horizon, daily limit, and capacity all apply through the API too.

Yes - for booking, cancellation, and rebooking events, so your own system gets notified instantly.

That's what the trial account is for: real endpoints, but with your own data, no risk.

Within a business day. Paying subscribers are handled with priority.

Yes - we can add your first schedule and services for you on request.

The chatbot answers on weekends; email gets a reply on Monday.

Yes, and it's worth doing - feedback shapes what we build next.

Through our own MeetPly interface - so you immediately see how it works from the guest's side too.

Usually twenty minutes, longer if needed.

No, it runs from the browser.

Yes, of course - that way the whole team gets trained in one session.

If you have 1..N people or resources with their own schedule, and your service has a duration, then yes. From a dental practice through a tire shop to a product demo, it's the same model.

Yes, that's supported: a booking can occupy multiple resources (e.g. a teacher plus a trial room), and the slot is only free when both are.

In the same calendar. Capacity is a single number on the service: 1 = individual, N = group - no two separate systems.

Yes. Car detailing or ceramic coating is a multi-hour block - the duration and the buffer are configurable per service.

Yes, every site, room, chair, or bay is its own resource with its own schedule. Plans are tiered by the number of calendars and resources.

Yes - a calendar per model, with an accompanying salesperson; group demos run with a capacity limit, on the same interface.

Yes. Just write to us, and we'll set up your first schedule, services, and resources together - on the Studio plan, even over a video call.

Yes, along with its follow-up break — free slots are calculated from that.

Yes, both in length and price.

No. Most salons just put the booking link in their Instagram bio.

Yes, per service — standard practice for longer work.

You can set up a recurring booking for them, so their slot stays fixed.

Yes, along with its buffer - the system factors both into free-slot calculations.

Yes, with custom questions on the booking form.

Yes, for long, product-intensive treatments.

Yes, each one is its own resource, with its own calendar.

As a private note on the client profile - the guest never sees it.

Yes - with different lengths and prices, otherwise your day keeps slipping.

Yes, as a separate service or add-on, with its own duration.

Yes, with recurring bookings on a three-to-four-week rhythm.

No, most salons just put the link in their Instagram bio.

Yes, each one is its own resource.

It's worth it: as a short, separate service, so it doesn't eat into the long treatment.

Yes, as a series - the guest sees both dates at once.

Yes, and it's strongly recommended for long sessions.

Yes, on the form; you can store treatment-related details in a private note.

Yes, as a separate service, repeating every two to three weeks.

Yes, as two separate services, each with its own length and price.

Yes - for a long session, it's standard practice.

A recurring booking can reserve every session at once.

Yes, with a custom question - the estimated duration depends on it.

Yes, everyone is their own resource.

Yes, the booking horizon is configurable per service.

Yes: as a longer block, or with capacity if you're working in parallel.

Yes, with an exception or a dedicated time slot outside your regular working hours.

Yes, as a buffer after the service.

Your own rule decides on the deposit refund; the system shows you the amount.

Yes, weekly or biweekly, with a set number of sessions.

Yes, as the service's follow-up break — the system accounts for it.

Then one resource is enough — that's the cheapest plan.

Yes, as a private note on the client's record; the guest can't see it.

Yes, and you don't have to pick up the phone — the system handles it.

No. The booking is for the booth - as far as the system's concerned, that's a resource just like a person.

Yes, as a buffer after the service.

Yes, visit-based or time-based, deducted automatically.

Yes, with capacity N.

Yes, from their phone using the displayed QR code.

Yes, but it's worth including the setup time in the service length.

Yes, with a recurring booking, all at once.

Yes, with custom questions on the booking form.

Yes, each one is its own resource.

Yes, with a recurring booking - the system spaces out the sessions at the rhythm you set.

It's worth it, since the length and price both differ.

Yes, as a separate, short service ahead of the series.

Each one is its own resource, with its own calendar.

Yes - the slot is only free when both are.

Yes, with capacity N, at fixed times.

Yes, with a displayed QR code or the link.

Yes, each with its own resources and its own schedule.

Yes, with a winter and summer schedule, tied to dates.

Yes, each service has its own length and follow-up break — free slots are calculated from that.

Yes, every doctor is a separate resource with their own weekly schedule and exceptions.

Yes, with a custom question — so you know what to expect before the patient arrives.

The private note is an internal field the guest can't see. You're responsible for following health-data handling rules yourself.

Yes, each specialist is their own resource, with their own hours.

Yes, with a daily limit, per exam type.

Yes, with custom questions on the form.

The private note is an internal field; you're responsible for following health-data handling rules.

Yes, a manual booking can override the rules.

With self-organizing groups: the first booker's area determines the session.

Yes, as a recurring booking, even several times a week.

Yes, with a custom question on the booking form.

Yes, with capacity 1 — in the same calendar.

Studio, because of the self-organizing groups.

Yes, with a recurring booking, months ahead.

You decide what it shows - even in a synced calendar.

Yes, as a separate service; the call link goes into the notification.

The cancellation deadline decides - past it, the fee applies per your own rule.

Yes, as a private note; it's an internal field the client never sees.

Yes, as separate services, each with its own length and price.

Yes, as a separate service — you can put the call link in the confirmation email.

Yes, biweekly or monthly recurring.

Yes, with custom questions on the booking form.

Yes for the first session — that's where the no-show rate is highest.

Yes, with a daily limit - so retail work isn't affected.

Yes, in the reminder email text.

With a recurring booking, or a reminder noted on file.

Each one is their own resource, with their own calendar.

Yes, as its own service with its own length.

With a recurring booking — set it up once, and their slot is theirs for months ahead.

Yes, session-based or time-based, with automatic deduction.

A cancellation past the deadline doesn't refund the session.

Yes, with capacity N — in the same calendar.

If you rent a room, add it as its own resource so it can't double-book.

As the service's capacity - sixteen bikes, capacity 16.

Yes, in the Studio plan; when someone cancels, everyone on the list is notified instantly.

Within the cancellation deadline, yes; beyond it, you decide.

Yes, with a recurring booking.

Yes, editable for just that one class, leaving the rest of the series untouched.

As the service's capacity — six machines, capacity 6.

Yes. If it's the same room or instructor, they can't overlap.

If cancelled within the deadline, yes — beyond that, it's your call.

Yes, in the Studio plan. Waitlisted guests are notified the moment a spot opens up.

Yes — by level: beginners join beginners, not advanced sessions.

With self-organising groups: the level of the first person to book sets the class.

Yes - one booking can take two spots.

Yes, with capacity 1.

Yes, with a recurring booking, breaks included.

Each one is its own resource.

With self-organizing groups: the first booker's details decide who can join.

Yes, either as separate services or as a filtering criterion.

Yes, a time-based pass — book freely until it expires.

You can cancel it, and everyone signed up is notified automatically.

Yes — if training runs in several rooms, each gets its own calendar.

Yes - the slot is only free when both resources are.

As the service's capacity.

Yes, with self-organising groups.

Yes, with custom questions on the form.

Yes, with capacity 1, in the same calendar.

With self-organising groups - the age group of the first booking sets the session.

Yes, with a recurring booking, including breaks and holidays.

Yes, and notifications go to them too.

Each one is its own resource.

Editable for just that one session, leaving the series untouched.

Yes, with a daily limit per resource.

Yes, one booking reserves both.

Yes, with a self-organizing group or with separate services.

Each one is its own resource.

Yes, with a session-based pass.

Yes, as a time-based pass - the member books freely until it expires.

Yes, you mark it alongside the booking, and the record builds up the full picture.

Each one is its own service, with its own training schedule.

Yes, with recurring bookings.

Yes, in the Studio plan - headcount, utilization, no-shows.

Yes, as a single, long service with a headcount limit.

Yes, and people on it are notified immediately on a cancellation.

Yes, with custom questions: age, meals, parent contact.

Each is a separate date within the same service.

Yes, and can have its own price — indoor or outdoor.

Yes, with a winter/summer schedule tied to specific dates.

Yes, with self-organizing groups, matched by skill level.

Yes — standard practice for court rentals.

Yes, every location's courts are separate resources.

Yes, with recurring bookings - set up in advance for the season.

Yes: the half-courts are separate resources, so they can be rented in parallel too.

Yes, by card at booking or with a payment link afterwards.

Yes, with separate winter and summer schedules.

Each one is a separate resource.

It's worth it: the length, price and headcount limit all differ.

Yes, as a separate resource.

Yes, with different capacity and offerings by time slot.

Yes, session- or time-based.

Yes, as a checkbox on the booking form.

Yes, and they can have different prices too.

Yes - the booking reserves both the instructor and the equipment.

Yes, one booking reserves the whole simulator's time.

Yes, and they can have different prices too.

Yes, with different services by time slot.

Yes, with adjacent bookings.

Yes, if you set up the weekend slot as a separate service.

Yes, configurable per service.

Yes, with recurring bookings, set for the season in advance.

Yes, from the same calendar.

Yes, with separate summer and winter schedules.

Each with its own lanes and calendar.

With self-organizing groups: the first sign-up's level determines the session.

Yes — the slot is only free when both resources are.

Yes, with a recurring booking, including holiday exceptions.

Yes, capacity decides which one it is.

Yes, anyone can book on the public page — and you decide what data to collect.

Yes, the room is its own resource — bookable on its own.

No. Once a lesson has booked the room, it can't be rented for that time.

Yes, with a recurring booking, including breaks and holidays.

The teacher is the resource — so you naturally get a separate calendar per instrument.

Yes, with capacity N.

With a self-organizing group - the first person's level decides.

Yes, with recurring bookings.

Yes, to hold the spot.

Yes, with capacity 1.

Capacity is the upper limit; below a minimum, you can notify the registrants and cancel the session.

Yes, by turning on approval.

Yes, with custom questions - billing details, catering, prior experience.

As a separate service with capacity 1 - the company books the whole session.

With a payment link or invoicing afterward.

Usually the bay — there are fewer of them. If a job is tied to one mechanic, they can be a resource too.

Yes, with a custom question — so you know in advance what's coming in.

Yes, with a seasonal schedule: longer hours during tire-change season.

You can move the following bookings in the calendar, and the guest is notified.

Yes, with a daily limit per service.

Yes, with a custom question on the form.

Yes, in the reminder email text.

Each one is its own resource.

Yes, with a manual booking.

Yes, the service length is fully customizable - up to eight hours.

Yes, with time-slot-specific service availability.

Yes, each one is its own resource.

Yes, the service length can be set in days too.

Worth it: it's short, and doesn't tie up the work bay's time.

Yes, every job is its own service, with its own time.

Yes, with a daily limit.

Yes, with a seasonal schedule.

Yes, with a custom question on the form.

The next bookings can be rescheduled, customers are notified.

Yes, with a seasonal schedule and a daily limit.

Yes, with a daily limit.

Yes, with a custom question.

Each one is its own resource, with its own calendar.

Either can be - one booking can hold both at once.

Yes, with capacity N and a headcount limit.

Yes, with a custom question on the booking form.

Yes, every test car is its own resource.

Yes, as a separate service - so it never collides with another booking.

Yes, the slot is only free when both are.

Yes, as a pass - every lesson automatically deducts one.

Yes, if you allow the longer block.

You set a cancellation deadline - inside it, the lesson isn't refunded.

Yes, with a custom question — for grooming this also affects the duration.

The appointment reminder is automatic; an annual reminder needs a recurring booking or a manual note.

Yes, everyone is a separate resource.

Yes, on the owner's customer record, as a private note.

With a self-organizing group - the first dog to sign up sets the age and level.

Yes, with a recurring booking.

Yes, with custom questions on the form.

Yes, with capacity set to 1.

Each one is a separate resource.

Yes, as a single, long booking.

Yes, and the price can vary by size too.

Yes, with custom questions - even as a required field.

Yes, as two separate services.

Yes, every service has its own length and price.

Yes, with a minimum lead time - so no one walks in half an hour later.

Yes, as a separate service; the call link goes into the confirmation.

Only ask for what's necessary on the form; the private note is internal, the client never sees it.

Yes, everyone is their own resource, with their own office hours.

Yes, each one is its own service, with its own time.

Yes, the call link goes into the notification.

Yes, with a minimum lead time.

Yes, with custom questions - only what you actually need.

Each one is a separate resource, with their own calendar.

Yes, so viewings can never overlap.

Yes, with capacity N - one slot, multiple viewers.

Yes, with custom questions on the booking form.

You deactivate the resource, and further bookings stop.

Yes, everyone as their own resource, with their own calendar.

Yes, with a recurring booking, on a biweekly cadence.

Yes, as a separate, short service.

The cancellation deadline decides - past that, the fee follows your own rule.

Yes, with a payment link or invoicing afterward.

Yes, as a post-service buffer - the system counts it into the free slots.

Yes, as a separate resource - it won't clash with your own shoots.

As a separate service with a longer duration - travel time can be built in too.

Yes, as a separate service or as a pass.

Yes, as a separate service.

Yes - the booking reserves both resources.

Yes, the service length can be set freely.

Yes, as the service's after-buffer.

Yes, by card or with a payment link.

No. The number of users is unlimited - the price comes from the number of resources.

Yes, each is its own resource, with its own equipment.

Yes, with a daily limit.

Yes, as a separate resource.

Yes, on the public booking page - even at a different price.

Yes, the service length can be set freely.

Yes, turning on approval makes every request wait for your yes.

Yes, in the service length or its after-buffer.

Yes, each one is its own resource.

Yes, as the service's after-buffer.

Yes, with a custom question - pricing can depend on it too.

If table assignment matters, yes. If only seat count matters, one resource with capacity is enough.

Yes, with capacity N and a headcount limit.

Yes, with a custom question.

Yes, with a fixed-length service and time slots.

Yes, in the confirmation email text - it saves a lot of unnecessary trips.

Yes, with a daily limit, per case type.

Everyone is their own resource, with their own specialty.

Yes, a manual booking can override the rules.

Yes, with a daily limit.

Yes, with a custom question on the booking form.

Everyone is their own resource, with their own calendar and hours.

You can reschedule the following ones in the calendar, and customers get notified.

Yes, capacity decides which one it is.

Yes, as a separate service - the call link goes into the confirmation.

Yes, with custom questions - so your colleague arrives prepared.

Everyone is their own resource, with their own calendar.

Yes, via the API, on the Studio plan.

The number of calendars and resources - the number of bookings is never limited. Solo includes 2, Studio includes 3 resources; any extra resource can be added for a fee.

The yearly price is lower than the monthly total; the billing toggle on the plan picker shows exactly how much you'd save.

14 days, no credit card required. After that, net prices + VAT, billed monthly or yearly.

No. With monthly billing you can cancel anytime; with an annual subscription, it runs until the end of the period because of the discount.

Yes, up or down, anytime. You set the resource count with the slider, and the price updates immediately.

No. There's no per-seat fee for your colleagues - what counts is the number of resources, not how many people log in.

It stays. If you don't subscribe, the booking page closes, but your data remains exportable and you can pick back up anytime.

We put together a custom offer. Write to us on the Contact page and we'll get back to you within one business day.

Yes, every price is net, VAT excluded. The invoice is issued automatically.

Within one business day, by email. If you leave a phone number, we can call too. On weekends the chatbot is on duty.

One sentence about what you do and how many people or resources you work with is enough - that tells us how many calendars and resources you'll need.

Yes, 20 minutes with screen sharing. You book the demo itself on our own booking page, so you see how it works right away.

Same address: info@meetply.com. Subscribers get priority.

We only use it to answer your message. We don't send a newsletter, and we don't pass it on.

Yes. On request we set up your first schedule, services and resources, so your first day isn't spent on data entry.