How agencies keep dozens of client forms working

Ask an agency who is responsible for a client’s contact form after launch, and you usually get a pause. Yet for a law firm, a dental practice or a local installer, that form is often the only way new business comes in. When it stops working, nothing visibly breaks: the page loads, the button looks clickable. The client assumes the agency is watching, the agency assumes the client would notice, and weeks pass before anyone asks why enquiries have dried up.

Why forms fail silently

• Updates: a CMS, theme or form plugin update changes the markup, removes a hook or breaks the JavaScript that submits the form.
• Hosting moves: the new server cannot send mail, the PHP mail function is disabled, or the SMTP credentials never made it across.
• Mail authentication: after a DNS change, SPF, DKIM or DMARC no longer match, and notification mails end up in spam or are rejected.
• New tracking tags: marketing adds a pixel or a consent tool, and suddenly a script error or an overlay blocks the submit button.
• CAPTCHA changes: a site key tied to the old domain, a test key left in place after staging, or a widget whose script is no longer loaded.
• Expiring certificates and domains: browsers warn visitors away from the form, or the domain behind the notification address lapses.

A routine that scales to dozens of sites

1. 1Make an inventory. List every client site and every form on it – contact, quote request, booking, newsletter – and where the messages are supposed to go.
2. 2Take a baseline. Check each site once from the outside and record the current state: protection, privacy notice at the form, accessibility basics, mail setup.
3. 3Automate the recurring check. Weekly is a sensible default for sites that live on enquiries; daily for those where a lost day really hurts.
4. 4Route alerts to one place. Send changes to a shared team channel rather than one person’s inbox, and alert only on changes, so nobody learns to ignore them.
5. 5Re-check after every change. Plugin updates, hosting moves, new tags and DNS edits should trigger a check instead of waiting for the next scheduled run.
6. 6Test the delivery path. Where the client agrees, send a clearly marked test submission and confirm it actually arrives – and watch for forms that suddenly go quiet.
7. 7Keep a monthly record. Note per site what was checked and what was fixed. That record becomes your report.

Make form checks a contract deliverable

Many maintenance contracts promise updates and backups and say nothing about whether the site still does its job. Writing form checks into the contract turns invisible care into a deliverable the client can see – and settles the question of who owns the form. Points worth defining:

• Scope: which sites and which forms are covered, including campaign landing pages.
• Frequency: how often each form is checked – and that a check follows every update or migration you carry out.
• What is checked: spam protection, privacy notice and tracking on the form page, accessibility basics, certificate and domain expiry, mail authentication.
• Active tests: whether test submissions may be sent, how they are marked and who receives them on the client’s side.
• Response times: how quickly you look at an alert and when the client is informed.
• Reporting: what the client receives each month and where they can look up the current state.
• Limits: what is not covered, such as the client’s own mail server or third-party tools the client added without you.

Report it so the client sees the value

Good maintenance is invisible by design, which makes it easy to cancel. A short monthly proof per site changes that: which forms were checked, how often, what changed and what was fixed. White-label reports let you send it under your own brand, and a client portal lets clients look up the current state themselves instead of asking. Keep the wording plain – “your quote form was checked every day this month; a problem after a plugin update was found and fixed the same morning” tells a client more than a page of technical findings.

Quick checks in pre-sales – used the right way

A passive outside check needs no access and no account, which makes it useful before there is a contract. In a discovery call, at a meeting or when a prospect asks you to look at their site, running a quick check together gives the conversation something concrete: a CAPTCHA running on a public test key, a missing privacy link at the form, a submit button hidden behind a cookie banner on a phone. It shows how you work without promising anything you have not yet seen from the inside.

If you would rather not build this tooling yourself: formexposed keeps many client sites in one account, with monitoring for verified domains, alerts to your team channel, white-label reports, a client portal and quick checks for prospects. Agencies that manage WordPress sites through MainWP can use the MainWP extension. The easiest start is a free check of one client site on formexposed.com – no account needed – to see your baseline.