Features, indexed 01–07

seven things it does, and what each one can’t.

Islay Crofte is a scheduling tool, so it does scheduling things. This page walks through each one on a real screen, says who it helps, and states the limit up front. Skip to the part you care about.

  1. 01Availabilityreads busy time only
  2. 02Booking pagesneeds open hours
  3. 03Reminderscuts, doesn’t end, no-shows
  4. 04Routingrules need good answers
  5. 05Intake and depositsevery field costs bookings
  6. 06Time zonescan’t fix a wrong profile
  7. 07Reportingcounts bookings, not outcomes

Capabilities

01

availability that reads every calendar

Connect Google and Outlook, work and personal. Islay Crofte offers only the slots that are free on all of them, so a client never books the hour you already gave to a dentist.

The limit: it only knows what your calendars know. A meeting nobody wrote down can still be booked over.

In your week: a partner with a client calendar, a firm calendar and a personal one connects all three once, then stops checking them by hand before every reply.

02

booking pages that look like your firm

Your logo, your colours, your meeting types and a short intro in your own words. A client picks a day, picks a time and is done in under a minute, on a phone or a laptop.

The limit: a page is only as good as your calendar. Book yourself solid and clients see an empty month.

In your week: paste one link into your email signature and proposals. “Does Thursday work?” stops being a thread.

03

reminders that people actually answer

Email confirmations and reminders on every plan, SMS on Team and above. Set the timing per meeting type: a day before for planners, two hours before for the forgetful. Failed sends collect in one list you can resend from.

The limit: reminders cut no-shows; they don’t end them. Someone who forgot will still forget, just less often.

In your week: Friday morning, you select the one failed SMS and resend it before lunch instead of finding out at 13:05.

04

routing that settles who takes the call

Round-robin hands each new request to the next free person in the queue. On Enterprise, rules read the intake answers first: payroll questions go to payroll, large engagements go to a partner.

The limit: round-robin is fair, not clever. It won’t know who suits the client. That’s what rules are for.

In your week: nobody argues over the last intro call. The queue shows who is next, and why.

05

intake answers and a deposit, before the meeting exists

Ask what you’d ask in the first five minutes, and take a deposit if no-shows cost you real money. The booking confirms only when both are done, and the answers travel with the event.

The limit: every required field costs a few bookings. Ask only what you’d otherwise ask out loud.

In your week: you open the call already knowing the topic, the headcount and which engagement letter to read.

06

time zones handled, so nobody does the sums

Clients see slots in their own zone and your team sees them in theirs. Confirmations carry both, with the zone named, which is the one detail people always leave out of a manual email.

The limit: it trusts the zone a device reports. A client on a travelling laptop may need to switch it themselves, and the page lets them.

In your week: a Friday 13:00 booking from a client two hours ahead is clear to both of you without a calculator.

07

a weekly count you can check against your diary

Bookings, no-show rate and who took what, by week. It’s there so you can see whether reminders and routing are doing anything, not so you can admire a dashboard.

The limit: it counts meetings, not outcomes. Whether the meeting went well is still your department.

In your week: Monday, you compare last week’s no-show rate with the week before and decide whether the two-hour SMS stays.

Under the hood, indexed 01–03

security, reliability, and what we won’t promise

A scheduling tool holds your calendars and your clients’ answers. Here is how that’s treated, in plain terms.

01

access you control

  • Calendars are read for busy and free time, not event titles, unless you choose to show them
  • Single sign-on and audit logs on Enterprise
  • Role permissions: who edits pages, who only sees their own queue
02

data you can take back

  • Intake answers are visible only to the people routed the meeting
  • Export bookings and answers when you want them
  • Delete a client record and its answers go with it
03

reliability, honestly

  • Live service status is posted on the Status page
  • If a calendar sync stalls, the page stops offering that person’s slots rather than guessing
  • We don’t quote an uptime figure here; the Status page shows what actually happened
Connections, indexed 01–08

every confirmed booking goes where your work already lives

Eight connections today. Calendar sync is two-way; the rest push the booking out. If your tool isn’t here, Make can usually bridge it.

01

Google Calendar

Two-way availability and event creation

02

Slack

An alert for every new booking

03

Jira

Tickets from intake answers

04

Asana

Follow-up tasks after the call

05

Mailchimp

Booked contacts into your lists

06

Xero

Deposits matched to invoices

07

Salesforce

Meetings logged on the account (Enterprise)

08

Make

Custom automations for the rest

Decision time

that’s the whole list. pick a plan.

Solo is free for one person. Team adds routing, shared pages and SMS. Enterprise adds rules, sign-on and audit logs.

Get access