Werkborg Service Intake

Turn a service request into a controlled work-order draft

The tested local adapter structures entered report text, identifies the customer, location, asset and issue, flags missing information and creates a reply and work-order draft only. Email, form and target-system connectors are not yet proven.

Intended delivery

Pilot objective: reduce manual rekeying and standardise intake while scheduling, pricing and critical decisions stay with your people.

Evidence required before delivery

  • Clearly labelled sample text from local input to field extraction, missing-information questions and ticket draft.
  • Human approval before a material external or system action.
  • An audit log showing source, step, actor, timestamp and outcome.

Authority boundary

What this solution explicitly does not promise

  1. 01

    No autonomous decisions on urgency, safety, price, contracts or final appointments.

  2. 02

    A record is created or sent only within the agreed permission and approval rule.

Source control

From source to field, without hiding uncertainty

This is a fixed example scenario. No mailbox, CRM, ERP or field-service platform is connected.

FieldExample valueSourceState
CustomerExample Company NorthMessage · line 1Confirmed
LocationUtrechtMessage · line 1Confirmed
AssetHeat pump HPX-8Subject + messageConfirmed
Serial numberNot presentNo source foundMissing
UrgencyContact requested todaySender requestReview needed

Example scenario · Demo — no message sent and no external system changed.

Human direction

The boundary is part of the product

The operator may organise information and prepare a draft. The service coordinator keeps decision authority.

01

Prepare

Structure fields, show source references and draft questions for missing information.

02

Approve

The service coordinator confirms only the displayed draft within the agreed scope.

03

Adjust

An employee corrects fields or instructions; the change belongs in the control log.

04

Return or reject

Incomplete reports and safety signals do not proceed automatically.

Bounded pilot

A pilot takes five weeks — as a planning assumption

  1. Week 1

    Record the workflow, roles, sources, baseline and exclusions.

  2. Week 2

    Define the field contract, sample set and acceptance criteria together.

  3. Week 3

    Build a local observe-and-draft flow; write nothing externally.

  4. Week 4

    Test normal, incomplete and safety cases plus failure and stop routes.

  5. Week 5

    Document outcomes, open risks and the recommendation to continue or stop, then hand over.

Acceptance before production

  • Measurable thresholds are agreed in writing only after a real baseline exists.
  • A frozen test set covers normal cases, exceptions and stop scenarios.
  • The authorised employee can approve, edit, return and reject.
  • No external action is possible outside the agreed connector and permissions matrix.
  • Data export, access revocation, recovery after failure and handover must be demonstrably tested.

Transparent scope

What you buy — and what you do not

Werkborg Scan€950 one-off

Process map, baseline, data risk, integration check and pilot decision.

Service Intake Pilot€5,900 / five-week planning assumption after the Scan

One intake source, one intended target system, a local test set and a human decision gate.

Planning prices, excluding VAT. Final scope, licences, providers and connections are confirmed in writing only after the Scan.

Not included or not proven

  • No production connector or customer tenant in this demo.
  • No proven customer outcome, saving, ROI or error rate.
  • No autonomous decision on safety, urgency, price, contracts or appointments.
  • No certification, legal opinion or compliance guarantee.

FAQ

Frequently asked questions

Does Service Intake replace a planner?

No. It prepares recurring control work; a named employee keeps authority over exceptions and material actions.

Does it already work with my ERP or field-service system?

Not on the evidence of this local demo. Version, API rights, test tenant, error handling and acceptance must be proven for each implementation.

Will an incomplete report still be sent on?

Not through the current local adapter. Missing information produces a question draft; safety signals produce a human hand-off.

Are five weeks guaranteed?

No. Five weeks is a planning assumption for a bounded pilot; feasibility follows from the Werkborg Scan and written scope.

Next step

Start with one provable workflow.

No generic AI presentation. Bring volume, systems, exceptions and the human decision-maker.

Watch the Service Intake demo