DispoHub Logo

Your systems. One workflow.

Connect what keeps
your business moving.

A map supports planning. A freight offer becomes an order. An AI agent prepares the next step. What matters is how each connection works in your daily operations.

Agree scope, access and setup for each connection

DispoHub design study: Dispatch workspace with orders, vehicles and delivery status; sample data.
DispoHub product worldDesign study · Sample data ↗

How the steps fit together

A clear path through the process.

01 —

Identify your systems

Which tools and accounts do you use today? Define which system supplies each type of information.

02 —

Define the data flow

Which information needs to be read, imported or created? An import and ongoing synchronisation are different requirements.

03 —

Try the workflow

Check a specific case with the intended access, roles and formats before relying on it in daily operations.

01

TomTom: maps in your dispatch context.

TomTom provides map and routing capabilities within DispoHub. Review stops and routes alongside your planning. Vehicle profiles, available data and settings determine the route information you use for your business.

  • Maps within the dispatch workspace
  • Review routes and stops together
  • Treat calculations as planning estimates
Explore the connection ↗
02

TIMOCOM: from freight offer to planning.

The TIMOCOM inbox places offers in the context of your working day. Your exchange account remains separate. We clarify permissions, setup and the transfer workflow; full synchronisation of every field is not assumed.

  • Account for your existing TIMOCOM access
  • Agree inbox setup and processing
  • Review offers against available capacity
Explore the connection ↗
03

ChatGPT: information and approved actions.

The private Business connection is designed for queries and supported actions with previews and confirmation. Explore the detail page for requirements and limitations. Other accounting or customer systems are discussed against your specific needs.

  • Confirm workspace and permissions
  • Choose supported actions
  • Discuss additional integrations
Explore the connection ↗
04

Outlook and Slack: collaboration for your operation.

Outlook is listed as an integration; Slack is planned on request. Define which messages should relate to an order and which information the team needs. Setup, permissions and actual synchronisation require review for each connection. A catalogue entry does not prove an operational end-to-end flow.

  • Discuss Microsoft 365 access and the intended workflow
  • Define the Slack workspace and channel
  • Clarify availability and provider prerequisites
05

Telematics: the next step for vehicle data.

Webfleet, Fleetboard and Samsara are listed as planned telematics providers in settings. The aim is to connect vehicle positions from GPS hardware. These provider connections are not offered as generally available. TomTom route planning, driver-app location and telematics are distinct sources and functions.

  • Planned: Webfleet, Fleetboard and Samsara
  • Make source and update time clear
  • Review provider access and operational release
06

PartnerConnect: connect orders across businesses.

The planned PartnerConnect flow should hand over an approved order directly to a connected carrier’s DispoHub. Both businesses retain their own workspace. Scope, permissions and the complete transfer need review before production use.

  • Direct handover as the development goal
  • Not a public freight exchange
  • Agree feedback and changes separately
Explore the connection ↗

Before you start

The right questions. Clear answers.

Review your workflow together ↗
Are all integrations included immediately?

No. Plans, access, setup and any third-party contracts vary by connection. We clarify these requirements before preparing an offer.

Does everything synchronise automatically?

That depends on the data flow. A map display, an import and an approved AI action are different capabilities. Scope is defined for each connection.

Can I connect another system?

Describe the system and required data exchange in the configurator. We review feasibility and scope before making a commitment.

The next step

Your business. Your DispoHub.

Show us how you work. Together we’ll explore the plan and modules that fit your day.