Skip to content
Help

When a Tokiawase link arrives

This is for people who have been sent a Tokiawase link. Neither answering nor booking needs an account.

Help category
Getting started

Answering and booking both work without an account. What you are asked to type, and what the other people can see, depends on which kind of link you were sent.

What tells them apart is the /quick/, /poll/, or /p/ part of the URL.

  • /quick/{public token} — Quick schedule. See Using Quick schedule without an account for what it is.
  • /poll/{public slug} — the response page for a poll. From an invitation email it arrives as /poll/{public slug}/{member id} instead.
  • /p/{public handle}/{booking type} and /p/group/{booking type} — booking links.

Either you mark each proposed time "Yes", "Maybe", or "No", or you paint a timeline with "Available", "Tentative", and "Unavailable". Either way the only things you fill in are "Name", which is required, and "Comment (optional)".

  1. Answer the proposed times — "Yes", "Maybe", "No", or add your time ranges
  2. Fill in "Name"
  3. Send it

In that first mode every proposed time starts on "Yes". Send without touching anything and all of them go in as "Yes", so change the ones that do not suit you to "Maybe" or "No". In the timeline mode you cannot send until at least one time range has been added. Once the organiser confirms a time, neither a new response nor an edit is accepted.

The page says "You can respond without creating an account." If you came from the personal URL in an invitation email, a response of your own is already set aside for you.

From a shared URL you answer under "Respond as a guest" instead. The first time, you set a name and a password of at least 8 characters, and the same pair lets you change your answer afterwards. The "Response edit password" field notes that "It is never shown or sent to the organizer."

Each candidate is answered with ○, △, or ×, and "Save draft" keeps a partly finished answer. Where responses are closed, the page gives the reason.

  • "This scheduling event has already been confirmed, so responses are closed."
  • "This scheduling event has been cancelled and no longer accepts responses."
  • "The response deadline has passed, so responses are closed."
  • "This scheduling event does not allow changing a submitted response. Contact the organizer if you need to change it."
  • "This scheduling event has not been published yet."

"Choose a time", then "Your details", then "Done" — three steps. You are asked for "Name *" and "Email address *"; "Company (optional)" and "Note (optional)" can be left blank.

Which clock the times are shown in depends on the page

PageTime zone used for displayTime zone name shown
Quick scheduleThe single one detected from the browser of the organiser who created itNo
Poll response pageThe browser of whoever is lookingNo
Booking pageThe one the host set on the booking typeYes, after the time

No public page has a control for switching it. Where time zones differ, ask whoever sent you the link which one the times are in.

Your name and your comment are visible to the other participants

What is stored is the name, the comment, and the answer itself. There is no field for an email address and no column for one either. Public pages are left out of analytics, and pages that carry a token are kept out of search engines as well. How access logs are handled is set out in the Privacy policy.

Notification emails carry no unsubscribe link, and there is no setting on the participant side for stopping them.

Changing an answer once it is sent

A Quick schedule answer can be edited only from the browser on the device you answered from. From another device it goes in as a second, separate answer. When a Quick schedule URL will not open covers this.

In a poll, a personal URL is simply opened again. As a guest, the same name and password load what you sent before. Neither route offers a way to delete the response itself.

Cancelling a booking or moving it means contacting the host

All the public booking page can do is show itself, fetch the open slots, and create a booking. Notification emails carry no cancellation link either. Contact the host named in the email.

  • "This schedule wasn't found" — a wrong URL, a page past its 90-day retention, and a deleted one all produce the same wording. When a Quick schedule URL will not open tells them apart.
  • "Availability cannot be checked right now. Please try again shortly." — that one sentence is all the person booking is given.
  • "Booking page not found" — either the URL is wrong, or the host has stopped publishing that booking page.
  • "This one-time link has already been used or is no longer valid. Ask the organizer to issue a new link." — the link was good for a single use.
  • A raw message such as "slotStartsAt is outside of the booking window" — the slot lies outside the booking window, or its deadline has passed.

Common questions

Do I need an account?
No. Answering and booking both finish without one. With Quick schedule the person creating the schedule needs no account either. An account is required for the four methods used once you sign in, polls and booking links among them. What Tokiawase does sets out the differences.
Can I withdraw my answer?
There is no delete action on the participant side. A Quick schedule answer is overwritten from the device you answered on, a poll answer from the personal URL or with the same name and password.
I want to cancel a booking.
The booking page cannot cancel it. Contact the host named in the notification email.
Are the times shown in my own time zone?
It depends on the page. Only the poll response page follows the browser of whoever is looking. Quick schedule uses the time zone of the organiser, and a booking page the one the host set.
No slots are shown at all.
Nothing on the screen the person booking sees says why. Contact the host.
I have forgotten my response password.
It cannot be reissued. What you get is "The name or password is incorrect." Try repeatedly and that turns into "Too many attempts. Please wait and try again." — 10 attempts per 60 seconds.
Back to the list