One page, six real answers -- not nine thin ones.

Every pencilled or confirmed slot rides the same fixed-slot / identity-keyed capacity decision the schedule.software family is built on: no-double-book and per-slot capacity are both enforced at the database, not in application code that can race. This is the floor every state below -- pencilled, held, confirmed -- sits on top of.

Booked-or-nothing is a modeling choice, not a law of scheduling. The design: a pencilled slot is a third state distinct from both "open" and "booked" -- it counts against capacity (so it cannot double-book), it is visibly provisional to everyone who can see it, and it carries its own expiry. It belongs where the booking decision is made, not as a countdown drawn on top of an ordinary booking. To be plain about status: this state is not built today. The fixed-slot floor it is designed to sit on is; the hold state itself is the thesis of this product and the thing being built next. Nothing on penciled.software serves a real hold yet.

A pencilled hold is designed to carry an expiry the holder sees up front. If nobody confirms before it lapses, the slot releases back to open capacity automatically -- no admin has to notice a stale hold and manually clear it, and no client is left wondering whether an unconfirmed hold is still theirs. Auto-release is the design; it is part of the same unbuilt hold lifecycle above, and no expiry is running anywhere today.

The other resolution to a pencilled hold: the holder confirms before it lapses, in one action, and the slot moves from provisional to booked without re-entering anything they already told the system when they pencilled it in. Designed, not built -- the same unbuilt lifecycle as the two above.

The scheduling platform this family shares an engine with describes a self-healing reschedule proposer of its own: a ranked list of minimal-cascade changes when a disruption hits a schedule, with a human ratifying before anything commits, built for that platform's dispatch booking law. That is its account of its own engine, not a measurement taken here. "Smart reschedule" is the design intent to point that same proposer at a lapsed or declined pencil hold: instead of a dead end, the holder sees a short ranked list of nearby open slots. That specific application is planned, not yet wired -- this page does not claim it runs today.

A booking page at your own hostname, not a shared subdomain, is planned on every tier including the free one -- the same inversion the rest of this platform's family plans: the appointment-link tools you already know make you climb to a paid, often enterprise, tier just to put your own name on the page. This is a packaging and pricing plan, not a claim that the connect-your-domain flow is live: pricing on this page is display-only.

Your logo, your colors, and the small badge gone -- planned for the Pro tier, the tier a solo practitioner or small studio actually buys, instead of gated behind an Enterprise sales call the way several tools in this category structure it. Team adds org-wide brand inheritance across every seat on top of that, not a separate branding tier. None of this is built on penciled.software yet -- it is a packaging plan, not a claim that a branding surface is live; pricing shown is display-only.