OUR FIRST BUSINESS / OUR OWN WORKING SYSTEM

From website form
to business inbox.

Brightweft needed the same thing many small service businesses need: a reliable way to receive a project request and keep enough context to follow up.

Implementation walkthrough of Brightweft’s own system. No client results or revenue claims.

What is real here?

The contact form is connected to the website’s inquiry endpoint, private Cloudflare storage and business-inbox notification code. This page includes a verified live test and documents the implementation. The illustrative request below uses fictional details to explain the flow; viewing it does not submit a request or send email. The separate inquiry assistant demonstrates a possible review interface, not a connected AI system.

THE FLOW AT A GLANCE

Send it. Save it. See it in the inbox.

A customer describes the job once. The business keeps a private copy and receives an email with the details needed to reply.

1 / CUSTOMER

“I’d like an estimate.”

The visitor sends a website form and gets a reference confirming it was saved.

2 / YOUR RECORDS

The details are kept.

A private record holds the request. The same reference connects the record and notification.

3 / YOUR INBOX

You can follow up.

The business receives an email. A person reviews the request and replies.

Illustrated explanation, not a screen recording. The verified test and original database capture below document the real implementation.

VERIFIED ON THE LIVE WEBSITE · 7 OCTOBER 2026

One request. One matching reference.

We submitted a clearly labelled internal test through the live form, inspected its private database record and opened the matching notification in the business inbox. This is a real system check, not a customer result.

01 / WEBSITE

Request accepted

The live form displayed BW-17AC77A1 after the request was saved.

02 / PRIVATE RECORD

Saved at 09:09:14 UTC

The database contains the same reference, labelled Brightweft internal test.

03 / BUSINESS INBOX

Matching email received

The notification subject was Website enquiry BW-17AC77A1. Gmail showed receipt at 14:39 IST.

Actual Cloudflare database result for internal test BW-17AC77A1: saved on 7 October 2026 at 09:09:14 UTC; notification accepted at 09:09:15 UTC on its first attempt.
Actual database-console capture, cropped to the internal-test result. Open the image to inspect it. Notification acceptance is logged here; inbox receipt was verified separately in Gmail.

The test uses Brightweft’s own details. No customer data is shown. These timestamps document one check, not a delivery-time guarantee.

  1. Capture enough context to respond.

    A visitor chooses a service, enters their contact details and describes the problem. Company, budget and referral source are optional. This gives the business a useful starting point without demanding a finished technical brief.

    Illustrative request · fictional details

    Business
    Example Studio
    Service
    Automation & integrations
    Challenge
    We copy new inquiries from email into a spreadsheet and want one place to track them.
  2. Validate before accepting.

    The server checks required information, email format and request size. A hidden spam field and submission limits reduce abuse. If validation fails, the form explains the problem and keeps the visitor’s details so they can correct it.

    Why this matters

    A button click alone is not a successful inquiry. The website waits for a server response before showing confirmation.

  3. Save privately. Return a reference.

    The accepted request is written to private storage before the visitor sees a receipt. Repeating an unchanged submission reuses its existing reference rather than creating a second inquiry. There is no public page that lists submitted requests.

    The confirmation

    The visitor sees a reference beginning with BW- and the email address supplied for follow-up. If saving fails, the site does not claim success.

  4. Notify the business, with a retry path.

    The system queues an email to Brightweft’s business inbox containing the reference and project details. If the email provider fails, the saved inquiry remains available and a scheduled job retries pending notifications.

    What the receipt does—and doesn’t—confirm

    The receipt confirms that the inquiry was saved. Email-provider acceptance and delivery into an inbox are separate events; the website does not promise delivery based on the receipt alone.

  5. A person decides the next step.

    Brightweft reviews the request, replies to the visitor by email and clarifies the next step. The production flow does not use AI to send sales replies automatically. For another business, a CRM connection or draft-review step can be scoped separately.

    What to adapt for your business

    Your inquiry source, destination, owner, required fields, failure alerts and follow-up process. We agree on these before choosing the tools.

ENGINEERING CHECKS

Check the unhappy paths, too.

Local automated checks cover saved requests, duplicate retries, invalid submissions, storage failures, notification failures and scheduled recovery. Notification tests use a test email provider, so they verify the code’s behaviour rather than live inbox delivery.

Walkthrough reviewed against the application source on 7 October 2026. No measured time savings, client outcomes or revenue results are claimed.

A SIMILAR HANDOFF IN YOUR BUSINESS?

Start with one
repetitive step.

Tell us where inquiries arrive, where they should go and who should respond. We’ll reply by email within one business day, Monday–Friday, about a suitable next step.

Discuss my automationExplore the separate review simulation