# Contact

> Describe what you need, with as much concrete detail as possible. I reply to messages myself, with no sales layer between you and the person who'll look at your request, whether it's a fault to deal with right now or a project still being scoped.

- Source canonique : [https://allaux.fr/en/contact](https://allaux.fr/en/contact)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## What to prepare before writing

1. **Describe the situation** — What isn't working, or what you're trying to build. The more concrete the description, the more concrete the reply can be.
2. **State the platform involved** — PrestaShop, WooCommerce, Shopify or custom development: it directly shapes how I approach the request and what I check first.
3. **Say if it's urgent** — A shop that's down isn't handled the same way as a project planned over several weeks. Say so clearly in your first message, with roughly when the problem started.
4. **Leave a way to reach you quickly** — Email and phone if possible, to avoid unnecessary back-and-forth on points that are simple to clarify.
5. **Attach access if you have it** — Read-only access to the admin or server often makes a situation clearer, faster, than a long written description.

## How to reach me

- **Email** — Suited to a detailed request, with screenshots, access details or documents to attach directly to your message.
- **Phone** — Suited to an emergency or a quick exchange, before putting the details in writing afterwards to keep a clear record.

## On response time

> I reply to messages within a reasonable time, with no set hours or contractual deadline stated on this page. If your shop is down, the emergency page explains what to do right away while you wait for a reply. A precise, complete message is still the fastest way to get a useful reply, rather than a round of clarifying questions.

## FAQ

### What's the best way to contact you?

Email or phone both work. For an emergency, a call is more direct than a message that might take a while to be read.

### Do I need a spec document already?

No, a description of the situation or need is enough to start the conversation. The precise scope gets built afterwards, with you, once I understand the request.

### Do you respond to requests from agencies?

Yes, I also work as an occasional technical subcontractor for agencies that need specific expertise on an e-commerce platform.

### What happens after my first message?

I come back to you with questions if needed, then a first take on the situation, before discussing price or committing to anything.

### Can I contact you for a simple question, without a specific project?

Yes. If I can't help, or if the request falls outside my area of expertise, I'll tell you directly rather than let the conversation drag on.

### Do I need to already know which service I need before writing?

No, that's not necessary. Describing the situation is enough; it's often through discussion that we work out together which service actually fits the need, rather than guessing upfront. A call or a short video chat can also help clarify a complex situation faster than writing back and forth.