One fix, no retainer — scope and price agreed before anything changes Incident desk: Mon–Fri, 08:00–21:00 TRT (UTC+3)

Bug fix request

Tell us what broke.

One incident, one form, about three minutes. We only ask what we need to decide whether we can take it. A human reads it and replies with the next step.

Never send us credentials

Do not enter passwords, API secrets, access tokens, private keys, card details, or exports of your customer data in this form. We do not need them here, and we will ask you to rotate anything sent by mistake.

When we need access, you invite our named account into your own systems — see our access and security process.

iWho you are

So we know who to reply to and can confirm you are authorised to request work on this application.

Please tell us your name.

Please enter a valid email address.

Please name the company or project.

iiThe app

Enough to place the work. We confirm the exact scope before anything begins.

A public URL, not a preview or localhost: the address where the failure happens.

Please give us the URL where the problem happens.

What kind of product is it?

Please choose the closest option.

Please choose an option.

iiiWhat broke

The more exact you are, the faster we narrow down where the failure actually is.

Please describe what should happen.

Please describe what happens instead.

Copy it as it appears — on screen, in the console or in logs. If there is none, write "no error shown".

Paste the error text, or write "no error shown".

What changed immediately before the failure? (tick all that apply)
Can the failure be reproduced? (optional)
Did this work correctly in production before?

Restoring a workflow that used to work is a different job from building one that never did. We tell you which one this is before you pay.

Please choose an option.

ivHow urgent is this?

These two answers decide how urgently we look, and whether this form is the right route at all.

What's affected right now? (select all that apply)

Please tick at least one. "Nothing critical yet" counts.

Do you suspect an active security breach?

Unauthorised access, data exposure or account takeover happening now. If yes, this intake is not the right route — we will show you the safe next step.

Please choose an option.

vAccess

How we'd get access, and your confirmation that we may.

Can you provide collaborator or supervised access?

You invite our named account into your own systems, at minimum privilege, and remove us at closure. We never ask for a password.

Please choose an option.

We can only work on applications you are authorised to change.

Nothing is charged here. We confirm scope and any price in writing first.

We have your incident.

A human reviews incidents within 15 minutes during desk hours (Mon–Fri, 08:00–21:00 TRT, UTC+3). Outside those hours you can submit now — review begins when the desk reopens.

Next, we confirm the access or evidence needed to start tracing the failure, and the $99 diagnosis step. The $99 is credited toward any repair you approve, and nothing in your app changes without your written approval.

The technical clock pauses while required access, your evidence or a third-party provider is unavailable. Do not email passwords, API keys or customer data — we request minimum-privilege access instead.

Reach us any time at hello@apprescuedesk.com.