Before you ask for a repair
A few useful details can save a lot of guessing.
You do not need to diagnose the website. A clear example of the failure is more helpful than a long list of suspected causes.
Prepare a short repair brief
The website repair preparation guide walks through the affected page, recent changes, access ownership and the checks a repair should pass. Use it privately; it does not collect your answers.
Do I need a new website?
Not necessarily. A single broken feature can often be assessed without committing to a rebuild. Replacement may be sensible when the current software is unsupported, essential files are missing or the required change cannot be made responsibly. The recommendation should follow the review.
Can you work with the developer or host we already use?
The current code, hosting and provider relationships can be reviewed first. Some fixes need the existing provider’s access or cooperation. Tell us who currently maintains the site and which accounts your business controls.
Will the repair take the site offline?
That depends on the problem and hosting setup. A test copy, backup and narrow release can reduce disruption. If downtime is needed or the repair has a particular risk, it should be discussed before the work is released.
What should I send first?
A public page address, the steps that fail, what you expected, when it last worked and an important deadline. Do not send passwords, private customer records or account exports through the public inquiry form.
Tell us what stopped working
Share the affected page, what you expected to happen and what happened instead. Use Contact Us at the bottom right or email Faith Forge Labs. A short description is enough to start; leave out passwords and private customer information.
Prepare your inquiry