Automate Customer Enquiries: From Website Form to Human Follow-Up

Choose a repeated task with a clear trigger and outcome. For example, a complete form submission should be recorded in an appropriate spreadsheet and reported to the responsible person. That person still needs to know what follow-up they own.

If every request involves a different judgement or a system cannot be accessed, clarify that before implementation. The first workflow should be small enough to describe and test against your real needs. Expansion can follow once you understand how it works in practice.

• What event starts the workflow?
• Which fields does the responsible person need?
• What confirms a successful handoff?
• Who receives a notification when a run fails?

A service business in Germany might capture agreed fields from an existing website form, record them in a suitable spreadsheet and email the responsible person. Reviewing the job, asking follow-up questions and preparing the final quote remain human tasks.

This is an illustrative process, not a promise that any combination of tools fits the entry package. We check the actual trigger, steps, integrations and access before agreeing on the scope. Building a new website or form is not automatically included.

When information is already in defined fields, it can often be moved or passed on using straightforward rules. Copying a customer name and enquiry number does not automatically require a language model.

If you want a free-text message interpreted or a draft reply prepared, we assess an AI step separately. That includes its data, running costs and the human checks needed for its output. A standard workflow price does not include every possible AI task.

The entry offer from €790 covers one workflow with up to three steps and two available standard integrations. Setup, failure notification, functional tests, documentation and a handover explanation are included. We define how steps are counted and which systems are involved in the written quote.

Multiple branches, approval chains, many data sources or an interface that must be developed from scratch may exceed that scope. We do not promise a connection to a closed CRM or booking platform without checking suitable access.

• Where an interface is unavailable, an email, CSV or manual handoff may be worth assessing.
• The offered website assistant already includes its agreed handoff to one email address; that feature is not charged again as a separate workflow.
• Extensions and later changes require a separate agreement.

Before launch, establish which fields make a request complete and which cases need manual review. Decide who notices a failed run and who checks it before another attempt. During assessment, also consider whether the same request can arrive twice and how it should be treated.

A failure notification does not mean every incident will be resolved automatically. Ask to see a successful run, a failure and incomplete input. Understand the boundaries and the situations where your team needs to intervene.

Optional monitoring starts from €79 per month within an agreed scope. Hosting and tool licences are separate. Monitoring does not promise unlimited development, changes or handling of every incident.

Before handover, clarify who owns the accounts, manages access and pays external service fees. Changes to a form, a tool or your internal process may require workflow changes. Clear responsibilities make it easier to budget for operation after setup.

Record the enquiry volume, the time spent transferring each request and the effort needed for corrections before the change. After a practical trial, compare actual handling time. Include the human review that remains and the time spent dealing with failures.

This is an evaluation method, not a guaranteed saving. Sometimes clearer form fields or an explicit owner improve the process enough on their own. Start with the business problem, then choose an implementation that fits it.