• About us
Log inDemo

Enobase Dispatch · Services

Make the next job clear before the team leaves.

One queue for the jobs to prepare.

Review the jobs by state and responsible person. Choose the record fields and views that suit your dispatch process.

See it on your own data

Prepare, assign, then follow the job.

Describe the job

Record the location, requested time and work to carry out.

Prepare, assign, then follow the job.

  1. Record the location, requested time and work to carry out.

  2. Associate the job with the person or resource responsible, using the fields your operation needs.

  3. Update the job state and record the information needed for the next team to act.

The details that make the record useful.

Choose the fields that explain the work and the next decision.

See it on your own data

A defined job

Give the work a reference, a site and a clear purpose.

Assignment context

Keep the responsible person and relevant resource beside the job.

Site instructions

Record access details and the document needed for the visit.

Completion context

Keep the outcome available for the person handling the follow-up.

The same starting point, shaped for different teams.

These illustrative configurations show how the unit of work changes with the operation.

See it on your own data

A caterer prepares an event delivery

The job needs a loading window, venue contact and equipment list. The return of equipment is a separate follow-up.

A maintenance team prepares a visit

The job needs the equipment reference, fault description and site access details. The report determines the next action.

Keep the hand-offs explicit.

Start from the records on each side, then agree which actions belong in the configured process.

See it on your own data

Prepare the assignment

Keep the scheduling context linked to the operational job.

Prepare the assignment

Carry the context into the visit

Use the job information to prepare the work performed on site.

Carry the context into the visit

Questions about Dispatch

Start with a defined process and its required records. Agree the configuration and connected actions before extending it to other teams.

PlanningExplore the connection with Planning.ExploreField ServiceExplore the connection with Field Service.ExploreFleetExplore the connection with Fleet.Explore

1WKttd0N3R Ro8tgjVSQ2

Discuss your processContact the team
Solutions
  • Finance
  • Quotes
  • E-Invoicing
  • HR & Payroll
Industries
  • Catering
  • Construction Company
  • Private Equity
  • All industries
Platform
  • Data Model
  • Knowledge & Collaboration
  • AI & Workflows
  • Analytics
  • Integrations
Company
  • About us
  • Hiring policy
  • Press & Brand
  • Download
  • Privacy
  • Terms
  • Subprocessors

© 2025 Enobase, Inc. All rights reserved.

  • LinkedIn
  • X
  • GitHub
marketing/screen-event-record
widget: marketing/screen-event-record family: screen kind: screen frame: desktop subject: One queue for the jobs to prepare. move: Highlight the relevant record or field; preserve the operational context neighbour: Other slots explain adjacent steps; this slot shows only the named subject content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare; adapt the record labels and fields to this module; keep the existing screen composition props: Record identifier, source, owner, state and the fields named in the sample not: A claim of universal integration support or an automatically completed business action static: yes
Open asset editor
marketing/widget-service-dispatch
family: widget; kind: record; frame: sticker; subject: A defined job; move: Highlight the relevant record or field; preserve the operational context; neighbour: Other slots explain adjacent steps; this slot shows only the named subject; content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare; show Give the work a reference, a site and a clear purpose.; props: Record identifier, source, owner, state and the fields named in the sample; not: A claim of universal integration support or an automatically completed business action; static: yes
Open asset editor
marketing/widget-service-dispatch
family: widget; kind: record; frame: sticker; subject: Assignment context; move: Highlight the relevant record or field; preserve the operational context; neighbour: Other slots explain adjacent steps; this slot shows only the named subject; content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare; show Keep the responsible person and relevant resource beside the job.; props: Record identifier, source, owner, state and the fields named in the sample; not: A claim of universal integration support or an automatically completed business action; static: yes
Open asset editor
marketing/widget-service-dispatch
family: widget; kind: record; frame: sticker; subject: Site instructions; move: Highlight the relevant record or field; preserve the operational context; neighbour: Other slots explain adjacent steps; this slot shows only the named subject; content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare; show Record access details and the document needed for the visit.; props: Record identifier, source, owner, state and the fields named in the sample; not: A claim of universal integration support or an automatically completed business action; static: yes
Open asset editor
marketing/widget-service-dispatch
family: widget; kind: record; frame: sticker; subject: Completion context; move: Highlight the relevant record or field; preserve the operational context; neighbour: Other slots explain adjacent steps; this slot shows only the named subject; content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare; show Keep the outcome available for the person handling the follow-up.; props: Record identifier, source, owner, state and the fields named in the sample; not: A claim of universal integration support or an automatically completed business action; static: yes
Open asset editor
marketing/widget-service-dispatch
widget: marketing/widget-service-dispatch family: widget kind: record frame: sticker subject: A caterer prepares an event delivery move: Highlight the relevant record or field; preserve the operational context neighbour: Other slots explain adjacent steps; this slot shows only the named subject content: Illustrative configuration: The job needs a loading window, venue contact and equipment list. The return of equipment is a separate follow-up.; use fictitious Belgian company Atelier Renard; label records consistently; do not present this as a customer testimonial props: Record identifier, source, owner, state and the fields named in the sample not: A claim of universal integration support or an automatically completed business action static: yes
Open asset editor
marketing/widget-service-dispatch
widget: marketing/widget-service-dispatch family: widget kind: record frame: sticker subject: A maintenance team prepares a visit move: Highlight the relevant record or field; preserve the operational context neighbour: Other slots explain adjacent steps; this slot shows only the named subject content: Illustrative configuration: The job needs the equipment reference, fault description and site access details. The report determines the next action.; use fictitious Belgian company Atelier Renard; label records consistently; do not present this as a customer testimonial props: Record identifier, source, owner, state and the fields named in the sample not: A claim of universal integration support or an automatically completed business action static: yes
Open asset editor
marketing/widget-service-dispatch
widget: marketing/widget-service-dispatch family: widget kind: record frame: sticker subject: The source and destination of a business hand-off move: Highlight the relevant record or field; preserve the operational context neighbour: Other slots explain adjacent steps; this slot shows only the named subject content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare props: Record identifier, source, owner, state and the fields named in the sample not: A claim of universal integration support or an automatically completed business action static: yes
Open asset editor
marketing/widget-service-dispatch
family: widget; kind: record; frame: sticker; subject: Prepare the assignment; move: Highlight the relevant record or field; preserve the operational context; neighbour: Other slots explain adjacent steps; this slot shows only the named subject; content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare; relationship to planning; props: Record identifier, source, owner, state and the fields named in the sample; not: A claim of universal integration support or an automatically completed business action; static: yes
Open asset editor
marketing/widget-service-dispatch
family: widget; kind: record; frame: sticker; subject: Carry the context into the visit; move: Highlight the relevant record or field; preserve the operational context; neighbour: Other slots explain adjacent steps; this slot shows only the named subject; content: JOB-2026-0042; Maison Delcourt, Namur; 18 Sep 2026 09:00; assigned to Mathilde Renard; loading entrance Rue du Moulin; state To prepare; relationship to field-service; props: Record identifier, source, owner, state and the fields named in the sample; not: A claim of universal integration support or an automatically completed business action; static: yes
Open asset editor

© 2026 Enobase, Inc. All rights reserved.

Log in
All systems normal