Questions, answered

It sends appointment reminders to everyone involved, not just to whoever made the booking. Each person on an appointment gets their own message by email or text, written for their role, and confirms or cancels with one tap. Everybody else is told the moment they do.

No. You add them once as contacts, and from then on they only ever receive messages. Confirming or cancelling happens on a secure link in the reminder itself — there is nothing to install, no password, and no app to download.

Minutes. Name the roles you schedule — whatever you call them — add your people as contacts, and book the first appointment. Message templates come ready to send, so reminders start going out before you have written a word of copy.

Yes — this is the point of the product. Every role you define carries its own templates, so the person delivering the appointment and the person attending it receive completely different wording about the same booking, sent at the same moment.

Yes. Assign each role its own template and the two messages share nothing but the appointment. One can be a short confirmation with a cancel link; the other can carry preparation notes, an address, or anything else only that side needs.

Yes. An appointment holds as many participants as you need, each with their own role and their own template. A third or fourth party — a parent, an interpreter, a second interviewer — is added the same way as the first two.

Yes. Templates are addressed by event, channel and role, so the same person can get a detailed email and a short text about the same appointment, each written to suit the medium it is sent on.

Any roles you like. Nothing in the product is hard-wired to a particular trade — you name the parties you actually schedule, and each name you add becomes a set of templates you can write separately.

Leave the role-specific templates alone and write one that applies to every role. Anyone without their own template falls back to it, so you can start with a single message and split it by role later, only where it matters.

By default, 24 hours and 2 hours before the appointment starts. Both are settings — you choose how many reminders go out and how far ahead each one lands, and the schedule you set applies to every participant.

Yes. Any appointment has a send-now button that puts a reminder straight onto the queue for every participant, on top of whatever is already scheduled. It is what you reach for when someone has gone quiet the morning of.

Yes. A recurring schedule is defined once and generates its own appointments and reminders from then on. Everyone is told about the series a single time rather than being notified again for each occurrence.

Everyone else on the appointment is told straight away, and your team is alerted too. Any reminders still waiting to go out for that appointment are pulled from the queue, so nobody is reminded about something that is no longer happening.

Yes. A confirmation notifies the other participants immediately, so nobody has to ask whether the other side is coming. You can see the same thing at a glance in the dashboard.

Each organization sets its own time zone and appointments are scheduled against it, so a reminder timed for two hours before the start arrives two hours before the start — not two hours before the server thinks it starts.

Yes. Any template can be sent as an SMS instead of, or as well as, an email, and text messages carry the same one-tap confirm and cancel links that emails do.

Normally no — SMS runs on your own Twilio account, so you pay the carrier directly at cost and there’s no markup from us. On any paid plan we can send from our number instead if you’d rather not run a Twilio account: get in touch and we’ll enable it with a monthly message allowance agreed up front.

That number is opted out immediately and permanently, and no further texts go to it from anywhere on the platform. It is deliberately not undone by a later START message — putting someone back on a list they asked to leave has to be a decision a human makes.

SendGrid, Mailgun, Postmark, or any SMTP server you already have. You connect your own account, so reminders leave on your sending reputation and your costs go straight to your provider rather than through us.

Yes. Connect your provider and the messages are sent as you, from your domain, so recipients see a name they recognise rather than ours.

Every email carries a one-click unsubscribe link, and every text honours STOP. Both are handled for you: once somebody opts out, the app stops sending to them without you having to remember.

That depends on where you and your contacts are. The app can require it: switch the consent gate on and new contacts get a link asking them to opt in before anything else is sent to them.

Yes, including the free one where a free plan is on sale. Unsubscribe links, STOP handling and consent tracking are never an upsell — sending people messages they cannot escape is not a premium feature.

Yes. Connect a Google account, choose which calendar to write to, and appointments you create appear there automatically — and come off it again when they are cancelled.

Yes. Each organization has a private iCal feed you can subscribe to from Apple Calendar, Outlook, or anything else that reads iCal. It stays up to date on its own once added.

Normally no — SMS runs on your own Twilio account, so you pay the carrier directly at cost and there’s no markup from us. On any paid plan we can send from our number instead if you’d rather not run a Twilio account: get in touch and we’ll enable it with a monthly message allowance agreed up front.

Yes, at any time. Limits apply going forward — we never delete data you already have if you move down a tier.

Only your organization. Every contact, appointment and message belongs to the account that created it, and nothing is shared between organizations on the platform.

Yes. Every message is logged with what went out, to whom and what happened to it, so when somebody says they were never told, you can check rather than guess.