01 —Platform

Everything your service team needs, in one place.

From the first error code to the closed ticket — chat, documents, machines, service calls, automations, and notifications, all grounded in your own data and built for commercial laundry.

  • Grounded chat
  • Documents
  • Model families
  • Service & tickets
  • Automations
  • IoT webhooks
  • Analytics
  • Roles & isolation
02 —AI troubleshooting chat

Ask in plain language, get a cited answer.

Your technicians type the symptom the way they’d say it out loud. Technoschor reads your manuals, wiring diagrams, and past service calls, then answers in steps — and shows the exact page or call each step came from.

  • Grounded, never guessed — Answers come only from your ingested documents and history — with a citation on every claim.
  • The diagram pulled alongside — When an answer references a circuit, the matching wiring diagram surfaces with it.
  • Works the way techs talk — Error codes, part names, half-sentences — no rigid query syntax to learn.
Technoschor · live

Dryer keeps tripping the thermal fuse on long cycles. Where do I start?

E-41 E-41 points to restricted airflow before the fuse itself. Check the exhaust path first:

  1. Inspect the lint filter and exhaust duct for restriction or collapse.
  2. Verify the airflow / sail switch closes; clear the blower wheel of lint.
  3. Confirm the high-limit thermostat resets before replacing the thermal fuse.
Service Manual · p.88 Service call #2207

03 —Documents & knowledge

Every manual, diagram, and bulletin — searchable.

Upload the PDFs that live on shared drives and in inboxes. Technoschor reads every page — text, tables, and diagrams — and indexes it so the right reference comes back in seconds, not after a binder hunt.

  • Ingests what you already have — Service manuals, wiring diagrams, parts lists, and bulletins — no re-keying.
  • Read page by page — Each page is chunked and indexed so answers cite the precise location, not the whole file.
  • Keyword + meaning — Retrieval blends exact-term matching with semantic search, so acronyms and intent both land.
Knowledge base 4 documents · indexed
  • Front-load washer — Service Manual PDF · 214 pages indexed
  • Wiring diagrams — drain & heat PDF · 36 pages indexed
  • Technical bulletin — E-23 revision PDF · 4 pages indexed
  • Tumble dryer — parts catalog PDF · 92 pages indexing

04 —Machines & model families

A sibling unit’s docs back up the one you’re standing in front of.

Track every machine across every site, grouped by model. When two models share a platform, Technoschor links them into a family — so the documentation from one quietly supports a fix on the other.

  • Models vs. instances — Define a model once; every installed unit inherits its manuals and diagrams.
  • Model families — Group related models so a family’s documentation is the primary source, with siblings as fallback.
  • Fleet-wide, multi-site — See machines by site, model, and serial — the whole estate in one view.
Machines WX-series family · 3 sites
MachineSiteModelStatus
Washer · #A4 Frankfurt WX-110 ok
Washer · #B1 Munich WX-110 ok
Washer · #C7 Berlin WX-120 E-23
Dryer · #D2 Frankfurt DX-60 ok

05 —Service calls & tickets

From the error code to the closed ticket.

Log a service call against the exact machine, capture the symptom and the resolution, and turn follow-up work into tickets. The history you write becomes searchable context for the next call.

  • Tied to the machine — Every call and ticket is attached to a specific unit, model, and site.
  • Resolutions become knowledge — What fixed it this time is retrievable the next time the same fault appears.
  • Assign, scope, and track — Route work to the right tech, with “own” vs. account-wide visibility per role.
Service call #2189 Resolved

Washer #C7 · Berlin · WX-120

E-23 symptom

Stops draining mid-cycle, drain-timeout.

Resolution

Cleared drain pump filter — button lodged in impeller. Verified pressure-switch hose.

Service Manual · p.142

06 —Maintenance automations

Preventive work that never quietly slips.

Define a maintenance schedule once and Technoschor generates the tickets on cadence — descaling, filter changes, belt inspections — so the work that prevents the 2am call actually happens.

  • Schedule-driven tickets — Recurring jobs auto-generate as tickets, assigned and dated, on your cadence.
  • Timezone-aware — Schedules run in your account’s timezone, so “every Monday” means your Monday.
  • No one chasing — Preventive maintenance stays on the board without anyone keeping a side list.
Automation

Quarterly descale — front-load washers

Cadence
Every 90 days · 08:00 · Europe/Berlin
Next run
in 12 days
Generates
Ticket per machine · assigned to site lead

07 —IoT webhooks & field notifications

A machine reports a fault — a ticket opens itself.

Point your connected equipment or monitoring at an inbound webhook. When a machine reports a fault, Technoschor opens a ticket against that unit and notifies the field — no one re-typing an error code off a screen.

  • Inbound webhooks — Connected machines and monitoring systems can raise a fault straight into Technoschor.
  • Auto-tickets — An incoming fault opens a ticket on the right machine, ready for triage.
  • Field notifications — The on-call tech gets pinged where they already work — no inbox archaeology.
Inbound webhook
POST /hooks/machine-fault
  • machine #C7
  • code E-23
  • site Berlin
Ticket #1042 created Washer #C7 · drain-timeout
Field notified On-call tech · field notification sent

08 —Analytics

See where the time, faults, and machines really go.

Service calls, tickets, and resolutions roll up into views that show recurring faults, machines that keep coming back, and where preventive work would pay off — grounded in the records your team already creates.

  • Recurring-fault patterns — Spot the codes and units that keep reappearing across sites.
  • Workload and follow-up — See open work, what’s overdue, and where calls cluster.
  • From your own records — Built on the service calls and tickets your team logs — no separate data entry.
Top recurring faults last 90 days · relative
  1. E-23 drain-timeout
  2. E-41 airflow
  3. E-17 fill fault
  4. E-09 door lock

Illustrative shape — your data drives the real view.

09 —Roles & multi-tenancy

Your data stays yours — and only the right people see it.

Every account is strictly isolated: retrieval, documents, machines, and history are scoped to your data and never cross into another customer’s. Inside your account, granular roles and scopes decide who sees and changes what.

  • Per-account isolation — Strict tenant separation, enforced at the application layer on every query.
  • Granular roles — Built-in and custom roles map resources to actions — view, edit, delete.
  • “Own” vs. account-wide — Scope chat, service calls, visits, and tickets to a person’s own work or the whole account.
Roles & access resource × action
ViewEditDelete
Owner
Service manager
Technician
Viewer
Scope chat · service calls · tickets · visits
10 —In one place

The whole platform, on one page.

No bolted-on chatbot, no second system to keep in sync — diagnosis, documentation, and dispatch in a single account.

  • AI troubleshooting chat grounded · cited
  • Documents & knowledge ingest · index · search
  • Machines & model families fleet · siblings
  • Service calls & tickets log · resolve · track
  • Maintenance automations schedule · auto-ticket
  • IoT webhooks & notifications inbound · field alerts
  • Analytics faults · workload
  • Roles & multi-tenancy RBAC · isolation
Get started

See it answer your toughest faults

A 30-minute walkthrough on your own equipment and documents. We map your manuals and service history, then show your team asking the questions they hit every week.

A 30-minute walkthrough on your own equipment and documents · no credit card

Get started

Book a demo

A 30-minute walkthrough on your own equipment and documents. Tell us a little about your fleet and we’ll be in touch.

We’ll only use your details to arrange your demo.