Contact

Write to us

A form that tells you what it does with your message: where it goes, what comes back to you straight away, and what it shows you when it does not get through.

Write directly
julien@roddier.pro
Straight after you send
An acknowledgement goes out to the address you gave.
Where the reply comes back
To that same address: it is the one set as the reply-to address on the message received.
If the message does not get through
The form says so and gives you the direct address again. Nothing is swallowed in silence.
What the form asks for — a first name, a surname, a valid email address and a message. If one of the four is missing, the message is refused and the reason appears under the button. Beyond five messages an hour from the same connection, you have to wait: that is what keeps automated sending at arm's length.

After you send

What becomes of your message

A contact form is a black box most of the time. Here is what is inside this one.

You get an acknowledgement

It goes out to the address you have just entered, with no waiting. It is the first signal, and it depends on nobody: your message did arrive.

The reply comes back to you

Your address is set as the reply-to address on the message received. A plain “Reply” is enough: nothing to copy out, nothing to hunt down.

A failure stays visible

A network outage or a mail server that is down: the form writes it under the button and gives you the direct address again. It never pretends to have sent something.

Your address is only used to answer you

It goes on no mailing list and opens no account. It is used for the acknowledgement, then for the reply.

Response time, once it can be published — a figure on display has to have been measured, otherwise it is a slogan. The time that counts is not the time to resolve: it is the time before the first reply from a person. That is the one being measured, as a median and as a worst case, never as an average — a reassuring average can hide the request that was never answered. It will appear here once it covers enough requests to mean something.

Already set up

Help belongs where the work is followed

This form is for getting to know each other. Once the support is under way, a driving school goes through its own direct contact rather than through here.

A request opens from your own account

A subject, a category — question, fault, suggestion, invoicing — and the request is on its way. It is not lost in a mailbox: it has a number and a place of its own.

It is followed in a thread

Every request keeps its history, its state and the last person to have written. So at any moment you know whether the ball is in your court or in ours.

Answers written once stay readable

Help articles filed by topic — learners, schedule, accounts, vehicles, tests, team, settings — can be read straight from your own account, without writing to anyone.

A question that keeps coming back is a gap in the product

Requests are grouped by category. A question asked twenty times is not a question: it is a gap in the product, and that is where it has to be filled.

Before you write, if something is not answering — the service status page queries the service live and says what is still working during an incident. It is hosted separately: it stays readable even when the service has stopped answering.

Your question may already be written down

Retention, portability, network outages, price, backups: the straight answers are gathered in one place.

Read the answers →