Inseln
Problem melden
Zuletzt aktualisiert:
If a time, a stop or a fare here is wrong, we want to know. If you have a timetable for an island we do not cover, we want that more. Both go to the same place and both get read by a person.
This form is switched off in this build
What you can see below is the real form, with real fields and real wording, and none of it works. It is disabled rather than hidden so that the shape of the thing is reviewable, and so that nobody fills it in and waits for a reply that will never come.
Before launch it posts to a form handler that forwards the contents to a maintained address and stores nothing. Reports are not published, quoted or listed anywhere unless the person who sent one asks us to, by name or anonymously as they prefer. The one exception is a confirmed correction to a published figure, which goes into the public changelog by default — that page describes changes to the dataset, not people.
For now, use the e-mail fallback below. It reaches the same inbox the form will reach.
E-mail fallback, working now
Send the island, the problem and what you saw to
hello@cycladesgo.com
with Timetable report in the subject line. In the current build
that address is a placeholder; the real one is published in the
imprint before
launch.
What happens to a report
- 1
You report it
Island, what kind of problem, and what you actually saw. A photo of the printed timetable or the operator's page is worth more than a description of it.
- 2
We check against the operator
Before anything changes, the report goes back to the source. If the operator still says what we published, we do not change it on a second-hand account.
- 3
It enters the changelog
If the published figure is wrong, the fix is dated and written up in the public changelog with what changed and what caused it. Not every report becomes a changelog entry; a confirmed correction always does.
- 4
We tell you
If you gave us an address, you get a reply saying what we did, including "we checked and the operator is right, you were right, and nothing changed", which is a real answer and not a brush-off.
Turnaround. Two working days to acknowledge, and five working days to say what we found. A confirmed correction ships in the next build rather than at the end of the week, and it carries the date it was confirmed. If a fix needs an adapter to be rewritten because an operator has redesigned their website, that is longer, and we will say so instead of going quiet.
We publish the correction even when it makes us look bad. That is the whole point of a public changelog: the Naxos outage of 26 September and the Paros coordinate collision of 19 September are on that page with their dates and their causes. A site that quietly fixes things and says nothing about them is asking for trust it has not earned.
What we cannot do. We cannot tell you whether a bus is running today, and a report saying a service was late will not change a published schedule, because the schedule is the operator's and it does not record lateness. We cannot change a fare an operator has set. And we cannot put an island in the planner on the strength of a screenshot — it needs a source we can re-read, which is exactly what the "I have a timetable source" option is for.
Reports are handled as correspondence, not as a support ticket queue. We are one small project and we answer our own e-mail. For a specific bus on a specific afternoon, the operator's telephone number is on every island page and is faster than any of this.