Where Linemerge fits
Scheduling tools split into two camps: ones that sync calendars to each other, and ones that publish a booking page. If you run more than one line you currently need both.
| Capability | Calendar-sync tools | Booking-page tools | Linemerge |
|---|---|---|---|
| Merge several calendar accounts into one view | Yes — that's the product | Usually one primary calendar, plus conflict checks | Yes |
| Public booking page with slot rules | No | Yes — that's the product | Yes |
| Per-calendar public/private, enforced at ingest | Varies; usually stores full events | Not the model | Yes — private calendars store times only |
| Source tag on every busy block | Sometimes | No | Yes |
| Calendars with no server API (iCloud, Exchange) | Rarely | No | Bridged from the phone |
| Merged availability as a subscribable feed | Sometimes | No | Yes |
| One subscription, one bill | Second tool | Second tool | One |
Compared by capability category rather than by naming a competitor's feature list, because those change often and a stale comparison table is worse than none. Categories are representative, not exhaustive — check any specific tool's current docs.
The honest version
If you have one calendar and want a booking link, a booking-page tool is a fine answer and probably cheaper in effort. Linemerge earns its place when you genuinely run more than one line and the merge — plus keeping the private one private — is the hard part.
That's the whole bet: one tool instead of two, with privacy designed in at ingest rather than bolted on at display.