You can't answer everything instantly. You can make sure no enquiry gets lost and every person hears something useful quickly. Here's a practical setup, in the order I'd check it.

Step 1: Test your own site like a customer

Open your website on your phone, on mobile data, not office Wi-Fi.

• Tap the phone button. Does it open the dialler with the right number? It should be a tel: link, for example <a href="tel:+15551234567">Call us</a>, with the country code included.
• Fill in the contact form with a personal email address that isn't connected to the business. Note the time you pressed Send.
• Check where it arrived, including the spam folder of the inbox that should receive it. If it's in spam or missing, fix that first (check SPF, DKIM and DMARC under Gmail's Show original).
• Call during a busy time and let it ring out. What does the caller hear? Is the voicemail greeting current, and does it say when they'll get a call back?

Write down what you found. Most businesses discover at least one broken link in this chain.

Step 2: Send an instant acknowledgement that says what happens next

An auto-reply that says only "Thanks for your message" doesn't help much. A good one answers the question the customer is actually asking: when will I hear back, and from whom?

Example:

Thanks, we've got your request. Sam will call or email you by 4pm today (or by 10am tomorrow if you wrote after 5pm). If it's an emergency, call 555-123-4567 and choose option 1.

Where to set it up:

• Form plugins (Gravity Forms, WPForms, Contact Form 7 with an add-on, Jotform, Typeform) all support a confirmation email to the person who submitted.
• Missed calls: many business phone apps and carriers can send an automatic text after a missed call. Check your provider's settings for "missed call text" or "auto-reply". Keep it short and give a time.

Only promise a reply time you can actually keep.

Step 3: Route everything into one inbox with a named owner

Enquiries scattered across a website inbox, a personal mobile, voicemail and Facebook messages are how things fall through the cracks. Pick one place:

• A shared inbox (for example a Google Group or a shared mailbox in Microsoft 365) that receives form submissions, voicemail-to-email and missed-call notifications.
• Or a simple CRM or job management tool if you already use one.

Then give each day a named owner. "Whoever sees it" means nobody. A single line on a whiteboard ("Today: Sam") is enough.

Also keep a copy of every form entry outside email, such as in the form plugin's entries list or a Google Sheet, so a mail outage never loses a lead.

Step 4: Check your reply time once a week

You don't need software for this. Once a week, take the last 10 enquiries and write down two times for each: when it came in and when a human first replied. In a spreadsheet:

=TEXT(C2-B2, "[h]:mm")

where B2 is the received time and C2 is the first-reply time. Look at the slowest few. Were they after hours, on weekends, or when one person was off? That tells you where to change the rota or the auto-reply wording.

Step 5: Use booking links and reminders to cut no-shows

If the next step is a visit, consultation or viewing, let people book a slot themselves instead of trading messages:

• Put a booking link (Calendly, Google Calendar appointment schedules, or the booking tool your industry uses) in the auto-reply and on the website.
• Turn on reminder messages: one the day before and one a couple of hours before, with a reschedule link.
• Ask for the address or the specific concern in the booking form so the first conversation is useful.

Step 6: If AI drafts replies, keep a human approval step

AI can help write a fast, polite first reply from a form submission. It can also get prices, availability or medical details wrong. A safe pattern:

1. The AI writes a draft reply in the shared inbox.
2. The day's owner reads it, edits it, and presses Send.
3. Nothing goes out automatically except the fixed acknowledgement from Step 2.

This keeps the speed benefit without letting software make promises on your behalf.

A 20-minute checklist

• Phone button opens the dialler with the correct number
• Form submission arrives in the inbox, not spam
• Auto-acknowledgement states who replies and by when
• Missed calls trigger a text or a clear voicemail promise
• All enquiries land in one inbox with a named owner
• Weekly reply-time check on the last 10 enquiries
• Booking link and reminders for appointments
• AI drafts, humans send

I write short, practical fixes for small-business websites and enquiry handling. If you'd like help setting up a single inbox with draft-then-approve replies, there's more at DeskStack.

This is one of the most expensive invisible bugs on a small-business site, because every lost message is a lost enquiry. Here's how to find out whether it's happening to you, and what usually fixes it.

Step 1: Test it like a customer

Send yourself a message through your own form, using a Gmail address that isn't yours. Then check the inbox that should receive it, including the spam folder.

If it landed in spam, or not at all, keep reading.

In Gmail, open the message, click the three dots, and choose Show original. Near the top you'll see three lines: SPF, DKIM and DMARC, each with PASS or FAIL. Those three tell you almost everything.

Step 2: Why it fails

Most website forms send mail from your domain (say hello@yourbusiness.com) but through your web host's server. Mail providers check whether that server is allowed to send for your domain. If your DNS doesn't say so, the mail looks forged.

• SPF is a DNS record listing which servers may send mail for your domain.
• DKIM is a signature that proves the message wasn't altered and came from an authorised sender.
• DMARC tells receivers what to do when SPF or DKIM fail.

Check what your domain publishes:

dig +short TXT yourbusiness.com | grep spf
dig +short TXT _dmarc.yourbusiness.com

No SPF record, or one that doesn't include the service your form sends through, is the most common cause.

Step 3: The usual fixes

1. Send form mail through a proper email service. On WordPress, an SMTP plugin connected to your real mailbox provider (Google Workspace, Microsoft 365, or a transactional service like Postmark, Mailgun or Brevo) is far more reliable than the host's default PHP mail.
2. Add that service to your SPF record. Each provider documents the exact include: value. Keep a single SPF record per domain. Two separate SPF records is itself an error.
3. Turn on DKIM in your email provider's settings and add the DNS record it gives you.
4. Add a basic DMARC record to start monitoring, for example v=DMARC1; p=none; rua=mailto:you@yourbusiness.com.
5. Set the form's "From" to your domain and put the customer's address in "Reply-To". Sending "from" the customer's Gmail address will fail every check.

Then repeat Step 1. You want PASS on SPF and DKIM.

Step 4: Add a safety net

Even with everything passing, keep a copy of every form submission somewhere other than email. Most form plugins can store entries in the site's dashboard or send them to a Google Sheet. If email ever breaks again, no enquiry is lost.

I write short, practical fixes for small-business websites. If you'd like someone to check your site's forms, mobile layout and the other usual problems, there's more at DeskStack.

This is one of the most common problems on small-business sites, and it's almost always one of three things.

1. The certificate only covers one name

An SSL certificate lists the exact hostnames it is valid for. example.com and www.example.com are two different names. If the certificate was issued for just one of them, the other one fails.

Check which names your certificate covers:

openssl s_client -connect www.example.com:443 -servername www.example.com </dev/null 2>/dev/null \
  | openssl x509 -noout -ext subjectAltName

If you don't see both DNS:example.com and DNS:www.example.com, that's your problem.

Fix: reissue the certificate for both names.

• Let's Encrypt with certbot: sudo certbot --nginx -d example.com -d www.example.com (or --apache).
• Managed hosts (Netlify, Vercel, Cloudflare Pages, Squarespace, Wix, Shopify): add both domains in the domain settings. The host then issues a certificate that covers both.

2. www points somewhere else in DNS

Sometimes the apex domain points at your current host, but www still points at an old host, a parking page, or the registrar's default server. That server shows its own certificate, which doesn't match your name.

Check it:

dig +short example.com
dig +short www.example.com

Fix: point www at the same host as the main domain, usually with a CNAME record to the hostname your host gives you. Wait for DNS to update, and then make sure the host has issued a certificate for www (see step 1).

3. The redirect is in the wrong place

Many sites redirect www to the bare domain, or the reverse. That's good practice, but a browser checks the certificate before it ever sees the redirect. A redirect on a hostname with no valid certificate still shows the warning.

Fix: make sure the certificate covers both names (step 1), then add one permanent 301 redirect to your preferred version. For example, in nginx:

server {
    listen 443 ssl;
    server_name www.example.com;
    # same ssl_certificate lines as your main site
    return 301 https://example.com$request_uri;
}

The 5-minute check

1. Open https://www.yourdomain and https://yourdomain in a private window.
2. Also try both with http://. All four should end up on one https:// address with no warning.
3. If any of them fails, run the two commands above. That tells you whether it's the certificate (step 1) or DNS (step 2).

That's it. Nine times out of ten this takes one setting change in your host's dashboard.

I write about small, practical fixes for small-business websites. If you'd rather have someone check yours for this and the other usual problems (mobile layout, broken buttons, slow images), there's more at DeskStack.

1. Productize the scope, not just the price. "Website help" doesn't sell. "20 researched companies matching your criteria, each fact with a source link, €90" does, because the buyer knows exactly what arrives.

2. Agree scope in writing before any money moves. A one-paragraph scope email ("you'll get X, by Y, not including Z") prevents 90% of disputes. Bigger jobs: half after the scope is accepted, half on handover.

3. Show a sample instead of a portfolio. One real sample deliverable answers more questions than a page of claims.

4. Async filters for serious buyers. People willing to write two clear sentences about what they need are usually the ones who pay.

5. Keep a human in the loop for anything customer-facing. E.g. for an enquiry assistant I build, the system only drafts replies, and a person approves every one before it's sent.

Still early (no big numbers to share yet), so I'd love to hear from anyone running a no-calls service: how do you handle buyers who insist on a call?

For reference, my shop is here: https://payhip.com/DeskStackStore (Bjarni, DeskStack)