Media breaks
Requests live in emails, forms or external systems instead of operational planning.
Ordinavo Connect
The interface between external requests and operational execution.
Receive appointment requests, service needs or partner data through API, web form, customer portal or terminal and turn them directly into plannable Ordinavo jobs.
External requests often land where operational planning does not happen
Service needs, visit requests or orders often arrive by email, phone, contact form, partner portal or external system. Before they become planned jobs, data must be transferred, reviewed and handed to dispatch manually.
Duplicate entry
Information must be copied manually into operational tools.
Unclear status
Customers, partners and internal teams often cannot see whether a request is reviewed, scheduled or completed.
Missing structure
Location, time window, priority and contact details do not always arrive in a consistent format.
Solution
A structured intake for operational requests
Ordinavo Connect receives external requests in a structured way and makes them ready for processing in Ordinavo. A request can become a reviewable case, a planned job, a route and finally a mobile task for the team on site.
Capture requests centrally
Validate and structure data
Reduce dispatch workload
Schedule jobs faster
Make status traceable
Connect partner and customer systems
Multiple intake channels. One operational process.
Ordinavo Connect is not limited to a technical API. It can become the controlled intake layer for portals, partner processes and self-service points.
API
External systems can submit appointment requests, service needs or order data to Ordinavo in a structured way.
Web form / customer portal
Customers or partners can capture requests through a portal or form without contacting dispatch directly.
Terminal / kiosk
Locations, info points or self-service terminals can send requests directly to Ordinavo.
Partner or ERP system
Existing business systems can hand over relevant jobs to Ordinavo and receive status information.
New: Customer-aware imports
Map incoming jobs to customers, locations and contacts
Ordinavo Connect can receive customer, location and contact data together with incoming jobs. External systems can provide customer IDs, site information and contact persons so Ordinavo can link imported targets to the right operational customer context.
Once mapped, the customer context stays available across scheduling, Smart Routing AI, MyDay, visit reports, customer timeline and outbound webhooks.
External request
Customer mapping
Target
Scheduling
Smart Routing AI
Mobile Execution
Visit Report
Webhook feedback
{
"externalId": "JOB-2026-000918",
"customer": {
"externalId": "CUST-10042",
"customerNumber": "RRM-001",
"name": "Rhein-Ruhr Medical Supply"
},
"location": {
"externalId": "LOC-ESSEN-01",
"name": "Essen Center",
"city": "Essen"
},
"contact": {
"externalId": "CONT-44",
"displayName": "Anna Weber"
}
}External IDs are the safest way to connect external systems with Ordinavo customer data.
Customer mapping
Match incoming jobs to existing customers using external IDs or customer numbers.
Location mapping
Reuse addresses, coordinates, access notes, work time defaults and routing context.
Contact mapping
Keep the right contact person visible for dispatchers and mobile teams.
CustomerContext webhooks
Return status, visit report, follow-up and billing events with customer, location and contact context.
From request intake to mobile execution
Receive request
A request enters Ordinavo Connect through API, web form, portal or terminal.
Review data
Required information such as contact, location, preferred time window or service type is captured in a structured way.
Classify case
The request is classified by use case, priority, region or service type.
Schedule work
Dispatch reviews the request and turns it into a planned job.
Build route
The job can be connected with other tasks and locations into a route.
Use Smart Routing AI
Smart Routing AI can support route suggestions, priorities and exclusion reasons.
Execute on mobile
The mobile team receives the task, works on site and documents the status.
Return status
The processing status remains traceable in Ordinavo and can be returned to external systems when needed.
Structured data
Structured data instead of incomplete messages
Ordinavo Connect can capture requests with the information needed for operational processing. Unstructured service needs become plannable cases.
external reference number
service type
priority
customer or site
contact person
address or job location
preferred time window
description
source system
metadata
Traceable status from start to finish
Each request can be followed along a clear status model. Teams can see whether a case has only been submitted, already reviewed, scheduled or completed on site.
Submitted
Validated
Pending Review
Accepted
Rejected
Scheduled
Assigned
In Progress
Completed
Cancelled
Connect is the intake layer for the Ordinavo workflow
Connect → Scheduling
An external request becomes a planned job with responsibility, location and time window.
Connect → Routing
Planned jobs can be connected with other tasks and locations into routes.
Connect → Smart Routing AI
Smart Routing AI can support evaluation, prioritization and route planning.
Connect → Mobile Execution
Employees receive the job on mobile and document execution directly on site.
Connect → Status & History
Request, planning, execution and status feedback remain traceable.
Integration
Integrable for portals, partners and external systems
Ordinavo Connect is prepared for structured integration with external systems. A documented interface can submit requests, retrieve status information and process feedback.
Go to API documentationAuthentication
Secure access through API keys or OAuth2 client credentials, depending on the integration model.
Appointment requests
External systems can submit new requests with contact, location and time-window data.
Webhooks
Status changes can be returned to connected systems.
Error codes
A clear error format simplifies integration, monitoring and support.
External intake with internal control
Ordinavo Connect is not uncontrolled direct access to internal planning. External systems can submit requests or receive status information while dispatch, permissions and operational approvals remain controlled inside Ordinavo.
Tenant context
Requests are assigned to the correct organizational context.
Permissions
External access can be limited to defined actions and data areas.
Review before planning
Requests can be reviewed and approved before they become scheduled jobs.
Traceability
Intake, changes, planning and status remain documentable.
Where Ordinavo Connect fits
Connect is useful whenever a request starts outside Ordinavo but needs to become part of operational planning.
Customer portal for service requests
A customer submits a service request through a portal. Ordinavo Connect receives the data, dispatch reviews the case and plans a job for a mobile team.
Terminal / kiosk on site
A request is captured at a location through a terminal. Ordinavo Connect turns it into a structured case that can be planned and assigned.
Partner or ERP system
An external system submits orders or visit requests through the API. Ordinavo connects the data with scheduling, routing and mobile execution.
Ordinavo Connect FAQ
What is Ordinavo Connect?
Ordinavo Connect is the interface for external requests, customer portals, terminals and partner systems. Requests can enter Ordinavo in a structured way and then be scheduled, routed and executed on mobile.
Is Ordinavo Connect only an API?
No. The API is one integration path. Ordinavo Connect can also be used as an intake layer for web forms, customer portals, terminals or internal request processes.
Who decides whether a request becomes a job?
The decision remains in Ordinavo. External systems can submit requests, but dispatch or management can review, adjust and approve them.
Can an external system receive status updates?
Yes. Ordinavo Connect is designed to make status information for requests and jobs available. Depending on the integration, this can happen through API queries or webhooks.
Can Ordinavo Connect be combined with Smart Routing AI?
Yes. After review, external requests can be moved into scheduling and then considered by Smart Routing AI during route planning.
Is on-premise deployment possible?
Depending on project requirements, Ordinavo can be operated as a cloud or on-premise variant. Integrations with specific data or infrastructure requirements can be discussed in a demo.
Turn external requests directly into operational jobs
See how Ordinavo Connect links customer portals, partner systems, terminals and operational planning.