Receipt acknowledgement
The customer receives an approved message confirming that the request or booking arrived. It should not promise a response time the business cannot reliably meet.
Routine work for automation
What can enquiry and booking automation handle?
Good automation moves agreed information, sends an approved acknowledgement and reminds someone about a missing step. It does not negotiate, resolve exceptions or replace the person responsible for the customer.
Short answer
Automate repeatable movement and reminders — not judgement.
Suitable stages include receipt acknowledgement, saving data in an agreed place, internal notifications, booking confirmations and reminders. Pricing, contract terms, complaints, ambiguous requests and sensitive situations should be routed to a person.
Written by AI net. Updated 3 October 2026.
Suitable tasks
What can be automated?
Define the trigger, required data, destination and failure state for every stage.
Internal task or notification
The agreed person is notified. The request may be saved in a task list, spreadsheet, protected custom view or CRM.
Booking confirmation and reminder
The system can send the time, service, location and approved change instructions. The effect of reminders varies, so measure the actual outcome instead of promising a fixed reduction in no-shows.
Follow-up on a missing stage
If an agreed status or deadline has not been updated, the responsible person receives a reminder. A person decides the next action.
Keep a person responsible
What should automation not decide?
The greater the impact on a customer, payment or rights, the clearer the human approval stage should be.
Price and contract terms
Automation may collect the starting information, but a person confirms the final proposal, exceptions and contract terms in writing.
Complaints and dissatisfaction
An automatic message may confirm receipt. A named person handles the substance, any refund and responsibility assessment.
Ambiguous and exceptional requests
If information is missing or the request falls outside agreed rules, the system should flag it for review rather than inventing an answer.
Special-category personal data
A solution handling health data or other special categories requires a separate privacy and system assessment before a proposal.
Data protection in practice
Collect only what is needed and state the purpose.
This is general design guidance, not a legal assessment. The business remains responsible for the lawful basis, transparency and retention rules of its processing.
Purpose
Document why the data is collected and where it is used in the workflow.
Minimisation
Do not ask for information the workflow or service delivery does not need.
Retention and deletion
Define how long requests, bookings and logs are needed and who can remove them.
Service providers
Identify where data moves, who processes it and which agreements or settings are required.
Official source
EU data-protection principles
The European Commission explains lawfulness, purpose limitation and data minimisation for businesses.
What data may be processed?
The amount and type of data depend on the purpose and legal basis. People must be told the purpose, and only the necessary data should be collected.
Open the European Commission guidance ↗Legal basis is assessed for the real purpose
Consent is not the only possible basis and is not automatically the correct one for every workflow. The basis must match the real processing purpose.
Open the legal-basis overview ↗AI net automation
One defined workflow from €890 + VAT.
The base package includes one trigger, an approved customer message, an internal task or notification, one reminder rule, testing, two revision rounds and 30 days of technical support. The final scope is confirmed in writing.
Describe your workflow →