Support that understands your challenges

Have a question about incubation calculation, equipment setup or your subscription? We're here for you. Support is not an afterthought bolted onto QuailBreeder — it is part of the product. Our goal is to keep quailbreeder.net working for your success 24/7, and to make sure that when something does go wrong, you talk to a person who understands both the software and the birds.

Guaranteed help within 24 hours

We value your trust. Whether you're using the free trial month or have already subscribed for $5, we guarantee a first response to your request within 24 hours. Not an autoresponder — a real answer from the person who wrote the code.

Why it matters: in poultry farming there are no secondary questions. Eggs will not pause their incubation while a ticket waits in a queue. If your hatch is tomorrow and something looks wrong today, an answer that arrives in three business days is worth nothing — which is why fast, competent feedback is a core promise of this service, not a premium extra.

How it works

1

Create a ticket

Sign in and describe your problem, question or suggestion in your personal account. Attach as much context as you like — what you expected, what happened, which screen you were on. There is no wrong way to write a ticket.

2

Get notified

The moment the developer replies, you receive an email notification — no need to keep the site open or check back on a schedule. Every further reply in the conversation triggers an email too, so the dialogue never silently stalls.

3

Solve the issue

Continue the conversation until the issue is fully resolved — the ticket stays open as long as you need it. The complete correspondence history is saved forever, so you can return months later and everything is still there.

The life of a ticket, start to finish

Here is exactly what happens after you press “Create ticket”. Your message is stored in the system and the developer is notified immediately. You can see the ticket in your personal list at any time, together with its current status — so a question, once asked, can never quietly get lost.

When the developer answers, the reply appears in the ticket and an email notification lands in your inbox. You respond whenever it suits you — the conversation keeps its full context, and every message from either side extends the same thread: one question, one place, complete history.

A ticket is closed only when the problem is actually solved — not when a timer runs out. And “closed” never means “deleted”: the entire correspondence remains permanently in your account. If the same issue resurfaces half a year later, you reopen the conversation with all its context instead of explaining everything from scratch.

This permanence is also how QuailBreeder improves. Recurring questions turn into clearer screens and better documentation; good suggestions turn into features. Several of the app's current functions started their life as a ticket from a farmer who needed them.

Loading demo tickets...

Why tickets are better than email

Direct communication with the developer

You're talking to the project creator, not a call center operator.

No spam

Your requests won't get lost in email filters.

Community priority

The subscription allows us to allocate resources for individual case analysis and implement your ideas into program updates.

Questions people actually ask

A few examples of what lands in the ticket system — so you know that nothing is too small:

Is my question too basic for a ticket?

No. “Which incubator type should I pick in Settings for my machine?” is a perfectly good ticket. The system exists for exactly these questions — a two-minute answer can save you a whole batch.

I found a bug. What should I include?

Describe what you did, what you expected and what actually happened; the device model and app version help too, and screenshots are welcome. You do not need to write a formal bug report — plain words are enough.

Can I suggest a feature?

Please do. Feature suggestions are read by the developer personally, and subscriber ideas regularly make it into updates. If your workflow needs something the app doesn't do yet, that is precisely what a ticket is for.

What about billing and subscription questions?

Same channel. Trial extension, payment issues, cancellation — write a ticket and it will be sorted out. Billing questions get the same 24-hour first response as everything else.

Do I need to stay online after submitting?

No. Close the tab and go back to the farm — the email notification will find you when there is an answer, and the conversation continues at your pace.

In which language can I write?

Write in the language you are comfortable with. English usually gets the fastest answer, but tickets in other languages are welcome and will be understood.

Not with us yet?

Try all system features, including personal support, free for 30 days.