Why functionality breaks
Sites are living systems: a PHP update on the hosting breaks an old library; a plugin update conflicts with a script; the mail server changes its rules and letters start bouncing; a new widget duplicates an old one and kills the form. None of it shows on the homepage — everything shows in lost enquiries. The dangerous part is invisibility: a form can be dead for weeks while everyone assumes "it is quiet because it is summer". That is why fixes start with diagnostics, and why we always recommend monitoring for the forms that carry your sales.
Forms and mail: the most common case
"The form sends, but no letters arrive" — the classic. The chain from the submit button to the inbox is long: browser validation, the AJAX handler, the CMS mail layer, SMTP credentials, the hosting mail limits, the spam filters, the CRM or telegram-bot hook at the end. We test every link, find where the message dies and repair it — credentials, transport, templates, rate limits. Then the tests: a letter from every form, on desktop and mobile, checked in the real inbox. And a small but valuable extra: a fallback address so no enquiry ever has a single point of failure again.
Scripts and interactivity
Calculators, filters, sliders, pop-ups, map widgets — the layer where sites feel alive and where they break most. Causes vary: a jQuery update, a new script colliding with an old one, a caching plugin freezing dynamic blocks, a third-party API that changed its response. We localize the conflict in the console, fix it in your code where possible, and pin the dependencies so the next update cannot silently break it again. If the widget is beyond repair, we say so early and offer a replacement — rebuilt lighter and compatible with the rest of the page.
How the work runs
You describe the symptom — a form, a screenshot, "nothing happens on click". Diagnostics follows on a copy or in a maintenance window: the cause is usually clear within the first hour. You get a short verdict with the fix estimate before any work starts; approving it launches the repair. After the fix: scenario tests — every path a user can take through the repaired feature — plus a check that nothing nearby changed. You receive a report: what broke, why, what was changed, and how to avoid a repeat. Access to hosting and CMS makes the work faster; we sign an NDA on request.
Cost and timelines
A mini-task (one breakage, local cause) — from 8 000 RUB, 1 day. Standard (a form plus mail plus tests) — from 15 000 RUB, 1–2 days. Complex diagnostics (module conflicts, data loss after an update) — from 25 000 RUB, estimated after diagnosis. A monthly support subscription — from 15 000 RUB/mo — includes such tasks in a bundled-hour package plus 24/7 form monitoring: many breakages we catch before you do. Diagnostics is free when the fix is ordered; standalone it is 3 000 RUB, credited to later work.
Why ZXY
We fix what others built for fifteen years — every CMS, every framework, every "the developer left" story — so rare causes are our routine. The verdict comes before the invoice: you approve a priced fix, not an open-ended investigation. Tests after the repair are part of the definition of done, not an extra. And we look one step further: if the breakage revealed a systemic risk — an update policy, a missing backup, a single point of failure — the report says so, and the support plan can close it before it bites again.
