Scheduling

Scheduling turns a 10xDotIn handle into a booking system. You can publish event pages, collect attendee details, connect calendars and video tools, accept paid booking checkout, and send booking events to downstream systems through webhooks.

Use Scheduling when a visitor should move from interest to a committed time: a demo, creator consultation, partner call, service appointment, onboarding session, support escalation, or paid expert slot.

If you are building a public handle page such as arjun.10x.in and need to add a booking CTA or inline slot picker, use Handle Booking Page with Scheduling as the developer handoff.

What Scheduling Helps You Do

• Publish handle-based booking pages for each event type.
• Collect attendee name, email, time zone, guests, answers, and custom booking fields.
• Connect Google Calendar/Meet, Office365 Calendar/Video, CalDAV, Zoom, and Stripe booking payments.
• Check availability against your local rules and selected external calendars before showing slots.
• Reserve a booking first, then create calendar, video, payment, and webhook side effects.
• Let visitors reschedule or cancel without needing Product Suite access.
• Send scheduling.* webhooks to your CRM, support desk, automation worker, or notification system.

Create Your First Booking Page

1. Open Product Suite and choose Scheduling.
2. Choose New event type and create an event type with a slug, title, duration, description, and location options.
3. Set availability with weekly working hours, date overrides, minimum notice, buffers, and a rolling or fixed booking window.
4. Add booking fields for the questions you need before the call.
5. Connect integrations for the tools you use. Google and Office365 can provide calendar availability and video links, CalDAV can protect legacy calendar availability, Zoom can create meeting links, and Stripe can collect payment.
6. Select the calendars that should block unavailable times.
7. Configure payment when the appointment should be paid. A paid booking sends the visitor to Stripe checkout before final confirmation.
8. Share the public booking link, such as /apps/public/scheduling/{handle}/{eventSlug}.

The public event response includes the event title, description, duration, locations, time zone policy, booking fields, payment requirement, and available actions. Slot responses use normalized ISO start and end times, the display time zone, source availability, and a booking nonce hint.

Visitor Booking Flow

The visitor flow is designed to stay simple:

1. Open the public booking page from your link, campaign, creator page, or support handoff.
2. Pick an available time from the slot picker.
3. Enter attendee details, custom field answers, guests, and location choice.
4. Complete checkout when this is a paid booking.
5. Receive the booking status, confirmation state, calendar sync status, and any next action.
6. Use the public reschedule or cancel flow when the time changes.

If a calendar or video provider fails after a valid booking is saved, 10x keeps the booking and marks the sync state as degraded instead of silently losing the appointment.

How Scheduling Connects To 10xDotIn Use Cases

Scheduling does not replace the existing use-case flows. It gives them a direct conversion endpoint.

Practical Examples

For SaaS and B2B, add a demo event type to every high-intent campaign. A pricing-page visitor can move directly from a personalized message to a booked sales slot while the booking keeps attribution context.

For Creator Economy, publish paid consultation, coaching, or office-hour slots from the creator handle. Stripe checkout collects payment, and scheduling webhooks can notify the creator's operations workflow.

For E-Commerce and Retail, use appointments for styling sessions, service consultations, installation calls, or high-value customer support.

For Affiliate and Partnerships, create separate event types for partner onboarding, campaign review, payout questions, and co-marketing planning.

For Events and Ticketing, use booking pages for sponsor calls, vendor coordination, VIP concierge windows, or post-event follow-up appointments.

Paid Booking Behavior

Paid event types reserve first and then send the visitor to Stripe checkout. The booking starts as pending payment. When Stripe confirms checkout with scheduling metadata, 10x marks the booking as paid and confirmed, then runs calendar and video side effects.

This prevents a paid appointment from disappearing because a calendar provider is temporarily unavailable. The booking stays visible, and any provider sync issue is tracked for follow-up.

Webhooks For Follow-Up

Scheduling webhooks let you automate the next step after a booking changes. Subscribe to the events your workflow needs:

• scheduling.booking.created
• scheduling.booking.confirmed
• scheduling.booking.cancelled
• scheduling.booking.rescheduled
• scheduling.payment.required
• scheduling.payment.succeeded
• scheduling.sync.degraded

Common webhook actions include adding the attendee to a CRM, sending a Slack alert, opening a support task, tagging a campaign record, or starting a fulfillment workflow after payment succeeds.

For delivery behavior, retries, and receiver debugging, see Webhook Delivery and Failure Handling.

Troubleshooting

If you need support, capture the handle, event slug, booking UID, approximate timestamp, and any checkout or webhook event ID, then use Troubleshooting and Support.