AI for trades: connect enquiries, quotes and jobs

Scope. This guide focuses on office workflows in small and mid-sized trade businesses. Its examples are synthetic. They identify information, decisions and interfaces to clarify before implementation, without claiming a tested connection or guaranteed time saving.

Complete case. An enquiry may arrive by form, email or telephone. What matters is whether it becomes a complete, clearly assigned case. Summarising the message alone can leave the real work unresolved: checking the address, assigning the trade, requesting photos, arranging a callback and identifying an owner.

Required details. A bounded process might require contact details, site address, type of request, preferred period and available documents. Missing information remains visible. The system can prepare a clarification request, but should not invent measurements, material quantities or technical characteristics to make the record appear complete.

Customer and work location. Separate the customer from the work location. An existing customer may manage several buildings. The correct phone number with the wrong site address still produces the wrong visit. Store the relationship to the specific property or project and show it throughout handling.

The table shows, for four administrative workflows in a trades business, what can be prepared and what still needs explicit review.

These workflows can connect, but should not form one uncontrolled chain. If quotation preparation remains inconsistent, structured enquiry intake can already be a worthwhile first project.

Give each handoff a visible state. “Ready for technical review” differs from “quotation approved,” and neither means that the customer has accepted the work. Those distinctions help both people and automation avoid premature actions.

Pricing source. A language model can prepare readable quotation text from available information. Prices, items and quantities should come from the designated sources. An old quotation is not a reliable current price list, and a similar enquiry does not prove the same material requirement.

Existing software. Check existing trade-software features first. HERO, for example, documents interfaces and exchange formats for item data and office processes. Its page also distinguishes a DATEV file export from a direct interface. That distinction matters more to planning than a broad collection of product logos. HERO interfaces, checked on 26 September 2026.

Field contract. Implementation needs a field contract: which items may be used, which price version applies, how changes are highlighted and who approves the finished draft. Advance the quotation only after the intended business decision has been recorded.

A fictional installation business receives a maintenance request by email. The sender is known but manages two properties. The message includes a blurred photo and asks for an appointment next week. The specific equipment identifier is missing.

In this synthetic example, the maintenance enquiry passes through four steps:

1. Intake. The system matches the contact but does not decide the site unilaterally. It creates an internal case and a clarification draft listing the missing information. A person checks that message before it is sent. The photograph is not treated as a reliable technical diagnosis.
2. Clarification. After receiving the missing details, the property and equipment are confirmed. The responsible technician determines the intended scope.
3. Quotation draft. Office automation can then assemble approved items and suitable wording into a quotation draft. Unresolved assumptions about materials or time remain visible.
4. Job preparation. Following approval and the customer’s decision, the team prepares the job. Calendar status, technician availability and required materials are confirmed through the responsible systems or people. An automated email must not confirm an appointment before those prerequisites are satisfied.

The value of this process lies in traceable handoffs. Staff no longer need to infer the latest state from several messages. The time released in a particular business still needs measuring during a pilot.

Separate confirmation. A vendor may provide an interface for new enquiries while other operations need separate confirmation. HERO, for example, publishes a Lead API and a GraphQL integration overview. That does not establish automatic support for every custom quotation or scheduling process. Official API documentation.

Exact operation. Ask about the exact operation, required permission, plan prerequisites and returned result. Can the process only create a case or update one too? Where is the destination ID stored? How does it recognise an enquiry already received?

File exchange. With file exchange, inspect the import result. A file placed in a folder is not yet an accepted order. Identify the authoritative information at each handoff and the person who corrects rejected records.

Supplier changes. Include supplier changes in the operating plan. When an interface or field changes, somebody must check the representative enquiry and its downstream effects. The first successful connection is the beginning of operation, not its permanent completion.

Mobile updates. Trade work generates information away from the office. Photos may be uploaded later, messages forwarded and the same update reported again by telephone. Use a stable project or case identifier and preserve when the information originated.

Repeated intake. Repeated intake must not silently create another job or appointment. Changed information needs to be identified as an addition, correction or new request. Similar free text alone is not a dependable basis for that decision.

Fallback. Define a fallback for interrupted connectivity. People must still be able to work on site. When service returns, reconcile manual decisions made in the meantime before executing old automated proposals.

Choose one trade or a clearly defined enquiry type. Before starting a trades pilot, record four baseline values:

• active handling time
• clarification requests
• incorrect assignments
• unresolved enquiries

Afterwards, include review time, corrections and maintenance.

Acceptance of a trades pilot should include five cases:

• a new contact
• an existing customer with several properties
• missing equipment details
• duplicate intake
• a changed appointment preference

Add an expired connection and an uncertain sending result. Inspect the outcome: correct case, correct address, traceable approval and exactly the intended action.

Start where information is currently lost or repeatedly requested. Once enquiries and owners are reliably connected, quotation and scheduling steps can be added deliberately. The result is an office process whose limits staff understand and whose value can be assessed using the business’s own evidence.

These pages continue the planning of enquiry, quotation and job workflows in a trades business:

• AI automation: tasks, selection and implementation
• AI automation for skilled trades
• AI workflow approvals: who checks which action?
• AI automation costs: a first-year budget for SMEs
• Phone intake for trades: from request to callback
• AI phone assistant costs: software and integration
• Testing an AI phone assistant in Austria: acceptance guide
• Adapt n8n templates to real office processes