About Islay Crofte

we make a link that books the meeting.

That is the whole company. A client opens a page, picks a time that is genuinely free, and the right person gets the meeting. We think software that does one job and admits where it stops is a relief to use.

  1. 01For teams whose clients book time with them, not the other way round.
  2. 02One job: availability, routing, intake and reminders.
  3. 03Plans from $0. The paid ones say plainly what they add.
The problem, indexed 01–03

booking a meeting should not take nine emails

Every client-facing team has the same thread. “Does Thursday work?” “Not Thursday, how about Friday?” “Friday morning is out, I forgot about the dentist.” Somewhere around message six, two people are double-booked and nobody knows who typed what.

Scheduling links already existed when we started. The trouble was what sat behind them. They read one calendar, sent every request to whoever owned the link, and left the useful questions for the first five minutes of the call. The client got a nicer form. The team got the same mess.

Islay Crofte was built around the team, not just the link. It reads every calendar a person uses, decides who should take the meeting, asks what you would have asked anyway, and reminds the client before they forget.

  • Mon 09:12“Could we do Thursday at 11?”
  • Mon 14:40“Thursday is gone. Friday 10:30?”
  • Tue 08:05“Friday works, who from your side is joining?”
  • Tue 16:22One link, one click. Nothing left to confirm.
Principles, indexed 01–04

four rules we hold ourselves to

  • 01

    say what it does not do

    Every feature on our site comes with its limit. A reminder cuts no-shows, it does not end them. You will find the catch anyway, so we put it first.

  • 02

    ask fewer questions

    Every required field on a booking form costs a few bookings. We default new intake forms to short and make you add the extra question on purpose.

  • 03

    respect the calendar you have

    We sit on top of Google and Outlook, we do not replace them. Your events stay where they are, and we only read busy time to offer honest slots.

  • 04

    price by what a team needs

    One person pays nothing. A team pays when it needs shared pages and SMS. A firm pays when it needs rules, sign-on and audit logs. No feature is held back to force an upgrade you do not need.

How it is built and supported, indexed 01–03

a small product, run like a utility

Scheduling is the kind of software people only notice when it breaks, usually five minutes before a client call. So we spend our effort on the dull parts: sync that stays current, reminders that actually send, and a clear record when one does not.

01

sync you can see

Every calendar shows when it last synced. If a connection drops, you see it in the dashboard, not from an angry client.

02

failed sends in one list

A reminder that bounces lands in a single view with a resend button. Nothing fails quietly.

03

a person answers support

Write to support@islaycrofte.com. You get a reply from someone who has the product open, not a canned article.

Where it is going, indexed 01–03

what we are working on, and what we will not build

No dates we cannot keep. This is the order we are thinking in.

  • Shipping

    routing rules that read intake

    Payroll questions to payroll, large engagements to a partner. Available on Enterprise today, and we keep adding conditions.

  • Building

    clearer reminder reporting

    A plainer answer to “did the reminder work?” per client, per channel, without a spreadsheet export.

  • Considering

    more connections

    Eight integrations today. Requests from customers decide what comes next, and Make covers the gaps meanwhile.

What we will not build

We will not turn this into a CRM, a video platform or an all-in-one suite. One job, done properly, and a clean hand-off to the tools you already pay for.

Next step

stop typing “does thursday work?”

Solo is free for one person. Team and Enterprise are there when a whole group needs it.

Get access