Form, email and WhatsApp.
With three entry points, it is easy to assume someone else has replied.
AI AND AUTOMATION / ENQUIRY HANDLING
From enquiry
to task.
A website message should reach the person who replies, complete and with a clear owner. This is the flow we run on our own site, and what a first pilot would look like for you.
THE SERVICE IN BRIEF
Website enquiry handling
The flow takes a message from the form, saves it unchanged with the contact, creates a task for the responsible person and sends the visitor an acknowledgement. It follows rules, without AI judgment. We have used it on our own website since 2 October 2026.
- Where it runs
- Our own website. This is not a results study for another client.
- Pricing
- A quote based on scope. Build, maintenance and external tool costs are kept separate.
- First step
- Describe one task through the form or WhatsApp. Then we agree what to review and propose.
THE PROBLEM
Where does an enquiry get lost?
Where a message arrives in several places and nobody is responsible for it.
Nobody is in charge.
Until an enquiry has an assigned person, the reply depends on who happens to see it.
Only a summary.
When a message is retyped into a spreadsheet, the original is lost.
What does the flow do, step by step?
It receives the enquiry, keeps the original, assigns a task and acknowledges receipt. A person replies.
| Step | What happens automatically | What a person does |
|---|---|---|
| 1. The enquiry arrives | The form receives the message in Bosnian or English. | The visitor describes their goal. |
| 2. The original is kept | The full text is saved unchanged in a note on the contact. | The person replying reads the original, not a summary. |
| 3. A task | A task with the enquiry details is assigned to Danijel. | Danijel reviews the goal, asks for more information and prepares the next step. |
| 4. Acknowledgement | The visitor receives an acknowledgement in the form's language. | Nothing. The acknowledgement promises no price, proposal or result. |
| 5. Repeat processing | Processing the same event again does not create a second task. | Nothing. |
| 6. A new reply | A reply by email or WhatsApp gets its own task. | Danijel reviews it and replies. |
Does this need AI?
No. The data transfer and the preparation of the task follow rules, without AI judgment.
An AI summary can be a separate add-on for human review, but it does not replace the original message. Danijel reviews the goal and replies. AI does not decide the proposal.
OUR OWN PROJECT / MIDAZ DIGITAL, BANJA LUKA
What did we check, and what did we not?
We checked that the flow delivers and behaves as agreed. We have not measured time saved, sales growth or client results.
Controlled checks.
Both form languages, the original message matching the task, receipt of email and WhatsApp replies, and repeated processing. A repeat created no second task, and a different message got its own.
No figures.
No time saving, sales growth or client result was measured. The checks establish delivery and behavior in the tested cases, nothing more.
Not a client project.
The flow has run on our own website since 2 October 2026. It is our own system in use, not a results study for another client.
Sample message, fictional data
“We run a service business in Banja Luka. We need a website explaining our services with an enquiry form. Could you suggest the next step?”
The flow keeps this text unchanged with the contact and in the task for Danijel, and sends an acknowledgement of receipt. This sample sends nothing and creates nothing.
Who does a flow like this suit?
A business whose enquiries arrive in several places or without a clear owner.
- enquiries arrive by form, email and WhatsApp, and nobody sees them in one place
- it is unclear who is responsible for which enquiry
- the original message is retyped or shortened before anyone reads it
- the acknowledgement to the visitor is sent by hand or not at all
If enquiries are rare and one person sees all of them, a well-organized inbox may be enough. Automation is then not the first step.
First project: one process.
Tell us where your enquiries arrive and who replies. We agree the scope and the price before work starts.
What does a first pilot look like?
One process, agreed inputs, a review with your team and a list of test cases. A pilot is agreed as separate work, with a written quote based on scope.
- Show us the work. We go through today's process, tools, how often the task occurs and where it gets stuck.
- Try the first flow. We agree the scope, build a first example and check it on representative tasks.
- Put it into use. We prepare instructions, training and agreed support, and track time, quality and the manual work that remains.
For each test case we write the expected result and who handles the exception: a complete enquiry, missing information, repeated processing, another message from the same contact and an unavailable service.
What do we need from you?
A description of the work and a few real examples. We aim to keep your tools and check the limits before we build.
- where your enquiries arrive today: form, email, WhatsApp, phone
- who replies and who covers for them
- which tools you already use
- what a good result looks like for you
- what must never be automated
- a few real example enquiries, including incomplete ones
- who has access to which data
What stays with a person?
The reply to the customer, the assessment of the goal and every decision about the proposal and the price.
Where a step needs a human decision, we build in a review or an approval. Before the build we decide what the system prepares, what a person checks and which actions need extra approval.
What can go wrong, and how is it caught?
Five cases we test. For two we have published no check from our own site, so every pilot must check them.
| Case | What the flow should do | Checked on our own site? |
|---|---|---|
| A complete enquiry | Keep the original, assign a task, acknowledge receipt. | Yes, in both form languages. |
| The same event processed again | Not create a second task. | Yes, in controlled repetitions. |
| A second message from the same contact | Give it its own task. | Yes. |
| Missing information | Show the original to the person who asks for the rest. | Not among the published checks. It goes on the test list of a first pilot. |
| A service temporarily unavailable | Leave a visible trace of the failure and give the task to a person. | Not among the published checks. It goes on the test list of a first pilot. |
BEFORE YOU START
Frequently asked questions.
What does enquiry automation mean?
A website enquiry is saved automatically and gets a responsible person and an acknowledgement. A person still writes the reply.
Do I need AI for this?
Not necessarily. For clear rules, ordinary automation is often enough, and our flow runs without AI judgment. AI makes sense where text must be understood or summarized, with human review.
Has this flow already run for clients?
No. It has run on our own website since 2 October 2026. We have no client project and no measured results, so read this page as a description of our own system.
What if the system stops?
Before going live we agree where a failure becomes visible, who gets the task and how work continues by hand.
Can I keep my own tools?
That is the aim. We check which integrations your tools support and where there are limits before the build.
How much does it cost?
It depends on the process, the integrations, the complexity and the support needed. The proposal separates the build from any subscriptions and external service costs.
Before you decide, clarify the basics.
YOUR NEXT BIG MOVE
Let's plan
your next move.
Tell us where you are now.
Let's see where you could go.
LET'S START WITH YOUR GOAL.
What would change things
for your business?
Show us a task that repeats. Let us see what we can connect, simplify or automate.
Or message Danijel on WhatsApp No obligation. Direct access to your specialist.