Phone intake for trades: from request to callback

Separate new enquiries, questions about existing jobs, appointment changes, supplier calls and urgent reports. Each category needs different information. An open question can start the conversation, but the assistant should then follow a relevant intake path instead of asking every caller the same long questionnaire.

For a new plumbing enquiry, the office may need the proposed work, location, approximate scope and callback availability. For an existing job, a reference number and a precise question can be more useful than repeating the original enquiry. A delivery call needs a site, delivery window and site contact.

The table lists five call types in a trades business with the useful information and the permitted outcome for each.

Adapt these fields to the trade. A joinery business needs different information from an electrical contractor. HalloPetra explicitly markets telephone and office assistance for trades businesses. That establishes a product category; it does not establish that a particular product supports your job-management software or your exact process.

Synthetic scenario: A caller wants two taps replaced in a rented flat and phones while the team is installing equipment elsewhere. The assistant identifies itself as an AI assistant, collects the location and request, and offers to record a callback. It does not confirm a price or installation date.

Summary. An actionable summary would say: “Enquiry to replace two taps in a flat in Linz. Access must be arranged with the tenant. Caller available Tuesday, 14:00–16:00. Photographs not yet supplied. Assigned to plumbing quotation review.” Recording “access not confirmed” is better than assuming the customer has a key. Recording a missing photograph is better than guessing the existing fixture.

Callback number. Before finishing, the assistant reads the callback number in manageable groups and asks whether it is suitable for the return call. Network caller ID is a useful clue, but it does not prove identity or confirm the preferred contact number. A caller with a withheld number must still be able to provide an alternative contact method.

Delivery to the office. The office should receive the information in its working system. Staff should not need to listen to the entire call to discover whether a photograph or site address is missing. The summary should distinguish what the caller actually said from any unconfirmed interpretation.

No emergency assessment. An AI receptionist is not a technical emergency assessment service. Agree with the qualified person in your business which statements must trigger immediate escalation. An assistant should not improvise repair instructions, decide that a situation is safe or reassure a caller when the consequences are unclear.

Escalation route. The escalation route needs a destination, operating hours and a fallback. A knowledge entry saying “we provide emergency service” is insufficient unless someone is responsible for answering that line at the relevant time. An automatic email to an inbox checked the following morning is not an immediate escalation.

No on-call service. If you do not provide an on-call service, the assistant should say so clearly. Any wording about appropriate public emergency services must be checked for the country and situation by the responsible people. Do not ask the model to decide independently which external service would be sufficient for an uncertain hazard.

One working location. Choose one operational home for telephone work: your job-management application, CRM or a deliberately managed task list. Every item needs an owner, a status and a time reference. A transcript delivered somewhere in the organisation is not the same as an accepted work item.

Useful statuses for a callback task include:

• new
• assigned
• callback attempted
• awaiting information
• completed

Also distinguish successful delivery into the destination system from a failed transfer. Failed writes need a monitored exception queue so that a technical error cannot silently become a lost enquiry.

Repeat callers. Repeat callers should not automatically create multiple independent jobs. Link requests using a confirmed reference or human review. A property manager's switchboard number may represent many buildings, while a family telephone number may be shared by several people. Telephone-number matching alone is a weak basis for merging records.

Appointments. An empty calendar slot does not establish that materials, travel time and skills are available. Capturing a preferred appointment is often a sensible first scope. Direct booking requires service duration, territory, buffers, equipment and staff requirements to be represented in the booking process.

Prices. The assistant can communicate an approved published fixed price if the scope, validity and possible additions are clear. Bespoke jobs need quotation intake, not an estimate invented from apparently similar work. Even “that should take an hour” can create an expectation the business cannot fulfil.

Three separate outcomes. itellicoAI's product description distinguishes appointment intake from direct calendar booking scoped to a customer integration. Make the same distinction in your specification: recording a request, proposing a slot and successfully storing a confirmed appointment are separate outcomes. Ask the supplier to demonstrate the one you intend to buy.

Speech and noise. Include local street names, house numbers, personal names and trade vocabulary. Test mobile calls with site noise, interruptions and switches between dialect and standard German. Begin with synthetic information so that the test does not unnecessarily expose customer data. Score the saved task, not just the quality of the spoken exchange.

The acceptance set for a trades phone assistant should include these cases:

• an address outside your service area
• an unknown job reference
• a busy transfer destination
• a caller without a callback number
• an unavailable job-management system

Repeat these cases after changing the knowledge source or routing rules.

AI transparency. The European Commission explains the transparency obligations applying to certain AI systems from August 2026. An understandable AI introduction should therefore be part of the design. Recording permissions and privacy information require their own assessment. European Commission guidance

Synthetic calculation: 100 calls averaging three minutes produce 300 call minutes. They do not automatically save 300 staff minutes. If the office still makes 60 callbacks and corrects 20 records, include that work in the cost and capacity calculation.

Track complete enquiries, missing required fields, duplicate tasks and callbacks actually completed. Compare staff handling time for similar call categories before and after introduction. Start the project with a list of frequent requests, the fields each one needs and a named owner for every possible outcome. That gives an assistant a defined job and gives the business a practical way to judge whether it is helping.

These pages cover the service overview, the industry page for skilled trades and the related decisions for a trades phone assistant:

• AI phone assistants: functions and boundaries
• AI automation for skilled trades
• Trade-business automation: a call-to-callback workflow
• Turn AI phone calls into usable CRM tasks
• Human handover and callbacks for AI phone assistants

For a workflow review, start with the task, systems involved and typical exceptions. Discuss it with modernagents.