Contact · Whenly.software
One email address that reaches a person.
There is no lead-capture form on this page and no billing relationship starts by getting in touch. whenly.software is early access, so the honest way to reach us is a plain email.
What to write about
Whatever you need — it all reaches the same inbox.
✓Early access
Tell us what you keep scheduling and we will add you to the waitlist for the find-a-time poll. Write to [email protected].
✓How it works
Questions about the poll, the three answers, the overlap finder, or the one-tap lock onto the shared booking floor — ask, and we will tell you what is built and what is not.
✓Privacy & data
Questions about opaque handles, the zero-PII feed, consent, or minor safety. The privacy page is the long answer; a person will take the rest.
✓Press
For press and partnership, the same address reaches us: [email protected].
A small fictional example can explain a large recurring problem.
A contact note is easier to understand when it names the decision the organiser cannot finish. Consider an invented adult workshop group comparing a morning and an afternoon window. Three colleagues prefer the afternoon, but one of those preferences applies only if the activity is shortened. The organiser is unsure whether to count that mark as availability for the original activity. That is a precise question about response meaning; it does not require a participant list or a copy of anyone's calendar.
A suitable manual specimen reads: Our group compares two windows for the same activity. One reply is conditional on a shorter duration. I need to keep that condition visible while deciding whether to ask a revised timing question. Does the described Whenly design distinguish those states? The note states its purpose and avoids claiming that a poll exists, that a response has been stored or that the product already makes this decision.
Keep a feature inquiry separate from an operational request. Asking how a future design is described does not create an appointment, hold a room or confirm workshop attendance. This page provides contact information, not a dispatch form or a polling endpoint. There is no case number, response-time promise or delivery confirmation attached to the specimen. The actual correspondence remains a separate action through the contact channel the reader chooses.
Name the unknown instead of asking the reader to reconstruct it.
A message saying the scheduling does not work can refer to several different problems: the candidate windows have different durations, one adult has not answered, the counts tie, or the preferred time conflicts with a resource arrangement. Name the one that applies to the example. If the product question concerns the boundary between a preference and a booking, say so directly. A recipient can then address the intended distinction without guessing which part of the workflow the writer means.
The contact can also be a correction to this site's explanation. Quote the short phrase at issue, identify the page and explain which result it appears to imply. For instance, an instruction that reads as though a static grid reserves a room deserves clarification. Keep the correction about the public wording rather than attaching a live group's details. An inquiry can be useful while remaining narrow and non-personal.
Does such a careful note take more time than a quick question? The specimen is only a few sentences. Its usefulness comes from including the decision, the specific uncertainty and the requested clarification. It does not need a complete account of every scheduling exchange. The result is correspondence someone can interpret, not evidence that the question has been answered. The page's lack of a live poll, booking action or purchase remains unchanged by making contact.
Separate an explanation request from an arrangement you need now.
A single contact note can contain two different needs: understanding the Whenly concept and arranging an imminent adult meeting. Those needs should be named separately. The first can be discussed through the public explanation. The second needs a process capable of actually establishing the meeting. A question about how a poll-to-booking design is intended to work does not give the site the ability to hold that meeting's time or resource.
For a fictional example, an organiser is preparing a materials discussion and also evaluating a better way to coordinate future group choices. A precise note says that the current discussion is being arranged through the organiser's established process, while the inquiry concerns how conditional answers are represented in the described concept. The inquiry does not ask the recipient to infer an urgent booking request from a general product question. It also avoids treating the product conversation as a reason to stop the arrangement already in progress.
If the note receives an answer about the concept, the organiser should read it within that scope. An explanation of candidate windows is not confirmation of the fictional discussion. A request for more context is not an account being opened. The page offers no response-time commitment, booking receipt or delivery status to erase those distinctions. Keeping them visible lets a reader ask a useful question without assigning an operational meaning to an ordinary exchange.
No form, no charge, no commitment.
There is no live checkout on this site, and getting in touch does not start a billing relationship or provision an account — whenly.software is not live yet, and this page does not pretend otherwise. Reminders and any future notifications are opt-in.