Case study · Businesses
LeadsBox: keeping an enquiry visible after the form is submitted
How I built LeadsBox around a business and its agency: a private website enquiry inbox, staff text alerts and a visible follow-up history.
In brief
A business owner needs to know what came through the website and what happened next. The agency looking after that website needs to answer the same question when a notification email goes missing. I developed LeadsBox around both needs: a private enquiry inbox on the business’s own site, text alerts for its staff and a record of follow-up.
The problem and context
A working form can still leave the business owner wondering whether an enquiry arrived. Its notification might be filtered, overlooked or lost among other email. The agency then has a support problem as well as a frustrated customer.
For my client Hues Agency, this is part of looking after customers’ websites. For those customers, it is part of running the business: noticing a request, replying and knowing what another member of staff has already done.
I started with the forms already in use. That is the practical craftsmanship behind this case: preserve the familiar customer experience and build the missing connection around it.
What I built and how it works
LeadsBox works with Fluent Forms on WordPress. A visitor submits the existing form, and the enquiry appears in a private inbox on that website. Fluent Forms keeps its original submission; LeadsBox adds the working view, statuses, notes and history.
The selected owners or staff receive a text alert with a route into the enquiry. Those alerts go to the business’s people. The person who filled in the form is not the recipient of that staff notification.
Inside the inbox, staff can open the details, record a note and move the enquiry through New, Contacted and Actioned. Someone returning to the enquiry can see its recorded history. A status reflects what staff recorded, so the quality of that record still matters.
Value for the business and the agency
The business gets a place to work through enquiries on its own site. Text alerts provide another way to notice incoming work, while notes help the next person pick up the conversation.
Hues Agency gets a more concrete basis for support. The recorded enquiry and messaging status help separate a missing form submission, a notification problem and a follow-up that still needs attention. The related operational tools also provide a scoped view across customer sites, with access appropriate to each operator.
AI assistance and human control
I used AI-assisted development to help build and refine the system. The core form capture, alerts and status history run through application rules. The actual customer conversation remains with the business’s people.
People choose recipients, manage access, review enquiries and make the actual customer contact. A delivery status alone does not establish that a person read an alert or replied.
The commercial result
The working system has become a managed commercial service offered through LeadsBox.ca by Hues Agency and Doorways Into Your Business. Its public site explains the product, offers plans and shows an inbox using fictional enquiries.
That is a concrete result: a recurring customer-support problem became a maintained product. This case makes no claim about increased sales, faster replies or recovered revenue without measurements.
Frequently asked questions
Does it replace the website’s form?
It works alongside Fluent Forms. The original form submissions remain there.
Who receives the text alert?
The business’s selected owners or staff receive it, so they can act on the enquiry.
Can I see the inbox?
The public screenshot tour uses fictional enquiries on the product’s own site.
See how it works
Explore LeadsBox.ca and see the enquiry inbox. Start with the record, the notes and the status history, then consider where an enquiry can lose its way in your own business.