How it works: 1. Create each participating system once (name + address). 2.–5. Tick in the “Workflows” table which system is involved in which event. 6. Press “Test connection”. Green ticks show what is already done.
A “system” is another program with which Dispo exchanges data – e.g. the customer data system or a fault system.
| System | Type | Address (endpoint) | Login | Status | |
|---|---|---|---|---|---|
| Customer data system Supplies appointment and service jobs; receives appointments and feedback back. |
Customer data / source system | https://kundendaten.example.invalid/api | Bearer-Token | ● active | edit |
| Fault system 1 Supplies faults; receives appointments and feedback. |
Fault/ticket system | https://stoerung1.example.invalid/api | Bearer-Token | ● active | edit |
| Fault system 2 Second target for fault feedback. |
Fault/ticket system | https://stoerung2.example.invalid/api | Bearer-Token | ● active | edit |
| Billing system Receives billed items (end-customer invoice). |
Billing | https://abrechnung.example.invalid/api | Bearer-Token | ● active | edit |
| Ticket system (placeholder) | Fault/ticket system | https://ticket.example.invalid/api/tickets | Bearer-Token | ○ off | edit |
| CRM (placeholder) | CRM | https://crm.example.invalid/api/notes | Bearer-Token | ○ off | edit |
| Source system (placeholder) | Customer data / source system | https://quellsystem.example.invalid/api/status | Bearer-Token | ○ off | edit |
✓ No failed hand-overs.
The systems send new jobs to this address (JSON via POST):
https://<ihre-adresse>/software/dispo/demo/api/orders
Authenticate with the API token in the request header: Authorization: Bearer <Token> · Token: demo••••••••ffcc (full value under Admin › API).
{"system":"Störungssystem 1","type":"MSTOE","customer_no":"K4100001","customer":"Max Muster",
"plz":"30159","city":"Hannover","street":"Musterweg 1","description":"Internet weg seit heute früh"}
“system” = name as above under Systems (optional – otherwise the intake as per workflows applies). Response: 201 + new job ID.
Tradespeople' feedback can be passed on to other systems automatically. Demo mode: No data is sent – every hand-over is only filed in the log (status “Demo – not sent”).
| Name | Type | Endpoint (placeholder) | Mode | Rules | Log | Active | |
|---|---|---|---|---|---|---|---|
| Ticket system (placeholder) | Fault/ticket system | https://ticket.example.invalid/api/tickets | Demo (log only) | 0 | 0 | no | edit |
| CRM (placeholder) | CRM | https://crm.example.invalid/api/notes | Demo (log only) | 1 | 0 | no | edit |
| Source system (placeholder) | Customer data / source system | https://quellsystem.example.invalid/api/status | Demo (log only) | 4 | 0 | no | edit |
| Customer notification SMS/email (placeholder) | Customer (SMS/email) | https://notify.example.invalid/api/messages | Demo (log only) | 2 | 0 | yes | edit |
| Customer data system | Customer data / source system | https://kundendaten.example.invalid/api | Demo (log only) | 0 | 0 | yes | edit |
| Fault system 1 | Fault/ticket system | https://stoerung1.example.invalid/api | Demo (log only) | 0 | 0 | yes | edit |
| Fault system 2 | Fault/ticket system | https://stoerung2.example.invalid/api | Demo (log only) | 0 | 0 | yes | edit |
| Billing system | Billing | https://abrechnung.example.invalid/api | Demo (log only) | 0 | 0 | yes | edit |
Several rules are possible per feedback reason. Empty sub-item = applies to all sub-items; empty service area = all. Events: feedback (tradesperson), appointment assigned (dispatch = appointment confirmation), appointment changed (rescheduling/withdrawal). Placeholders: {auftragsnummer} {kundennummer} {kunde} {adresse} {leistungsart} {grund} {unterpunkt} {notiz} {tradespeople} {datum} {status} {artikel} {summe} {termin} {uhrzeit} {termin_alt} {fixtermin} {storno_grund} {info} {einsatzadresse} {email} {mobil} {kundenadresse} {rueckrufnummer} {ansprechpartner} {produkt} {objektbereich} {leistungsumfang} {einsatzstandort} {pt} {wt} {frist} {abteilung} {rueckmeldung} {quelle} {referenz}
| Event | Feedback reason | Sub-item | Service area | Target | Action | Text template | Active | |
|---|---|---|---|---|---|---|---|---|
| Feedback | all reasons only with items | all sub-items | all | CRM (placeholder) | Billing to customer | Billing to customer {kunde} ({kundennummer}) for job {auftragsnummer}: ⏎ {artikel} ⏎ Total gross: {summe} ⏎ {tradespeople}, {datum} | yes | edit |
| Appointment cancelled (customer) | – | all sub-items | all | Source system (placeholder) | CRM note | Customer {kunde} cancelled the appointment {termin} {uhrzeit} (job {auftragsnummer}): {info} | yes | edit |
| Appointment changed | – | all sub-items | all | Source system (placeholder) | Report appointment | Appointment change job {auftragsnummer}: new {termin} {uhrzeit} (previously {termin_alt}), tradesperson {tradespeople}. | yes | edit |
| Appointment changed | – | all sub-items | all | Customer notification SMS/email (placeholder) | Inform customer | Hello {kunde}, your appointment has been moved: now on {termin}{uhrzeit_text} (previously {termin_alt}). Job {auftragsnummer}. | yes | edit |
| Assign appointment | – | all sub-items | all | Source system (placeholder) | Report appointment | Appointment for job {auftragsnummer}: {termin} {uhrzeit}, tradesperson {tradespeople}.{fixhinweis} | yes | edit |
| Assign appointment | – | all sub-items | all | Customer notification SMS/email (placeholder) | Inform customer | Hello {kunde}, your tradesperson will visit you on {termin}{uhrzeit_text} ({adresse}). Job {auftragsnummer}. Questions: 020 7946 0000 (demo). | yes | edit |
| Cancellation | – | all sub-items | all | Source system (placeholder) | Report status | Job {auftragsnummer} cancelled by customer service. Reason: {storno_grund}. | yes | edit |
Status: Off · 0 appointments mirrored in Outlook · 0 Outlook blockers on the board · last synchronisation: never. Demo: nothing is sent to Microsoft – every request is in the log below, Outlook appointments (e.g. doctor, holiday) are simulated. Blockers are treated like absences on the board, in Auto-Dispo, “Fetch jobs” and drag & drop; only “busy”/“away” is taken over, no subject (data protection).
| Point in time | Order | Target | Action | Payload | Status | |
|---|---|---|---|---|---|---|
| No hand-overs logged yet. | ||||||
| Time | Direction | Action | Mailbox | Order | Request | Status |
|---|---|---|---|---|---|---|
| No synchronisation yet. | ||||||