AI Act disclosure for a construction chatbot: identify the system and preserve human handoff

Disclose the system at the point of interaction

A customer should not have to infer from tone or response speed that a construction chatbot is automated. Place a short disclosure where the conversation starts and repeat it when a person joins an older thread without the original context. Name the business responsible for the channel and explain what the assistant can do: answer bounded questions, collect information or prepare a request. Avoid implying that it can make contractual, safety or payment decisions when those remain with authorised staff.

Define the handoff triggers before launch

Human handoff is not a generic button added after testing. List the situations that require it: a safety incident, disputed variation, cancellation, legal complaint, payment arrangement, unclear identity or repeated failure to understand. The handoff record should carry the project, customer, recent messages, unresolved question and any document referenced. It should not silently carry unrelated personal data from other jobs. Give the customer a realistic next step and avoid promising an immediate response when the team is unavailable.

Keep generated text separate from business action

A useful construction assistant can interpret a request and prepare structured context, but the business system must enforce permissions and confirmation. A message saying that a visit is rescheduled is not the same as an approved planning change. A payment question is not authorisation to alter an invoice. Show the proposed action, affected record and consequence to the authorised user. If values change before confirmation, refresh the proposal instead of applying an old decision.

Test transparency as part of operations

The European Commission's current AI transparency guidance should be reviewed against the actual deployment. Test a new conversation, a returning customer, a language switch, a minor asking a question, a hostile prompt and a handoff outside office hours. Keep evidence of the wording, deployment date and escalation result. Review again when the channel, audience or capabilities change.

Turn the decision into a controlled workflow

Do not leave this control in an isolated note. Record who checks the inputs, which source supports the decision, which exception requires human review and who confirms the final action. Enfin can bring customer, project, quote and invoice context together, while Alfie can prepare or execute actions within verified permissions. That is not a substitute for legal or tax advice, but it makes the contractor's control repeatable. Explore Enfin, review pricing, or discuss the workflow.