Out-of-Office Handoff & Multi-Provider Payments

Set up an out-of-office period and let meetergo reassign your appointments automatically — then pick the right payment provider for every meeting type, one by one.

Automatic Appointment Handoff for Out-of-Office

You can now schedule out-of-office periods directly in meetergo. Set your start and end dates, choose how bookings should be handed off — to a queue you're part of, a specific colleague, or your whole team — and meetergo takes care of the rest.

While you're away, you're automatically removed from any queues you belong to, so new bookings route to available colleagues instead of you. Existing appointments during the OOO window get reassigned to the target host, with conflict detection so nobody ends up double-booked. When your OOO period ends, you're restored to every queue you were in before.

A key detail: reminders are re-scheduled under the new host, but the original booking confirmation doesn't fire again. That means your customers don't get a duplicate WhatsApp or SMS when the appointment is handed off — just a clean reassignment behind the scenes.

Multiple Payment Providers Per Meeting Type

Up until now, each meeting type could use one payment provider. Some of you run mixed customer bases — a Stripe account for card payments and PayPal for customers who prefer it — and wanted both available on the same booking link.

You can now enable multiple payment providers on a meeting type, and the booker picks which one to use at checkout. If you've only got one provider enabled, the booking flow is unchanged — you won't see any extra steps. Existing meeting types keep their current provider as the default, so no migration or reconfiguration needed.

The new paymentProvider field also works through the booking API, so if you're integrating meetergo into your own flow, you can specify which provider to use for a given booking.

All Changes

New Features

• Out-of-office with automatic handoff: Schedule OOO periods with queue, specific-user, or team handoff. Queue memberships are snapshotted and restored when you return.
• Multi-provider payments: Enable multiple payment providers per meeting type; bookers pick at checkout.
• Configurable URL on meeting type templates: Admins can set the booking URL on a template once and have it propagate to all assigned colleagues, instead of the URL being auto-derived and mangled with -1, -2 suffixes.
• Bulk operations for availability and templates: Apply availability schedules, holiday exceptions, and meeting type templates to multiple users in one action. Meeting type duplication now supports a userIds parameter.
• Instant booker with signed PDFs: Hosts can create on-the-spot bookings against a hidden "Quick Meeting" meeting type. PDF confirmations are cryptographically signed with an audit page appended.
• Google Tag Manager integration: New GTM container ID field on companies with GTM-XXXXXXX validation and connect/disconnect flow.
• Higher custom domain limits: Default cap raised from 3 to 10 custom domains per company, configurable per plan.
• Physical address on business card: Add street, city, postal code, and country to your online profile. Exported as ADR in vCard downloads.
• Smart default sort on appointments dashboard: Upcoming and all-appointments views default to earliest-first; finished and cancelled views default to latest-first.
• Internal notes on meeting types: Organizer-only notes (up to 5000 characters) for project keys, partner info, or anything else that shouldn't be visible to bookers.
• Channel parameter for recurring and multi-slot bookings: API now supports channel-specific availability resolution for recurring series and multi-slot bookings.
• Form field variable picker: Custom form fields now appear automatically in notification template variable pickers under "Form Fields".

Improvements

• Friendlier WhatsApp registration errors: Payment-method, rate-limit, and data-localization errors from Meta now show actionable guidance instead of raw API responses.
• Apple and CalDAV reauth indicator: Invalid credentials now surface a "needs reauth" flag with a single notification per connection, instead of silently failing syncs.
• PDF signature flow streamlined: Signatures auto-submit as soon as the signed PDF is ready, and persist across dialog close/reopen so you don't lose your work.
• Email verification errors: Clearer messages for each failure case (invalid token vs. wrong code vs. expired).
• Pricing plan descriptions: Updated plan copy to highlight each tier's core value, with NEW badges on Visual Branding Editor and e-signatures.
• Email sync upgrade modal: Now fully translated and includes the plan tier label.

Fixes

• Availability offset after calendar events: When a calendar event ended mid-interval, later slots were incorrectly offset (e.g., first slot at 14:20 instead of 14:00 when opening at 14:00). Slots now anchor to your business-hours start.
• Multi-block schedules: On days with multiple schedule blocks (e.g., 09:20–12:00 and 14:00–17:00), the morning block's offset no longer leaks into the afternoon block.
• Availability when a specific host is picked from a queue: Availability now correctly reflects the chosen host's calendar instead of the full queue.
• Duplicate confirmations on appointment handoff: Reassigning an appointment no longer re-fires booking-confirm workflows, so attendees don't receive a second WhatsApp or SMS.
• Concurrent booking race conditions: Advisory locks now prevent two bookers from claiming the same slot at the same time. In the rare case a paid booking loses the race, the payment is refunded automatically.
• Salesforce Event sync: Event subject and description now use the real calendar invite content (including API-provided overrides) instead of a placeholder.
• Email change blocked for SSO users: Users logged in via Google federation can no longer change their email, which previously could leave the Cognito account in a broken state.
• Booking conflict detection across meeting types: Conflict checks now ignore the meeting type (hosts can only be in one meeting at a time regardless of which type it is).
• WhatsApp phone registration: App is now subscribed to WABA webhooks before phone number registration, fixing "destination account must have webhooks set up" errors during EU migration.
• WhatsApp storage configuration: Fixed invalid payloads sent to Meta; now uses the correct IN_COUNTRY_STORAGE_ENABLED / NO_STORAGE_ENABLED enums.