Scattered customer communication
Requests, appointment updates and reports are spread across email, phone calls and chat.
Gib Kunden und Partnern einen kontrollierten Portalzugang fuer Anfragen, Termine, freigegebene Besuchsberichte, Anhaenge, Follow-ups und operative Statusinformationen, waehrend dein Ordinavo-Team Pruefung, Planung und Ausfuehrung steuert.
Many service, maintenance and field teams still handle customer requests, appointment updates and visit documentation through email, phone calls, PDFs or scattered messages.
Requests, appointment updates and reports are spread across email, phone calls and chat.
Customers do not know whether a request is submitted, reviewed, planned or completed.
Visit reports and attachments are often sent manually after internal approval.
Customers need visibility, but not access to internal notes, routing logic, billing details or integrations.
The Ordinavo Customer Portal gives external contacts a secure, limited view into the operational workflow without entering the internal Ordinavo app.
Customer portal users are invited explicitly and receive access only to the customer and location context that has been granted to them.
Invite customer contacts through a controlled portal invitation flow.
Portal users authenticate through a separate customer portal session, not the internal Ordinavo app.
Limit portal access to a full customer context or selected locations.
Portal users see shared operational information, not internal administration.
Kunden koennen Service-, Wartungs-, Termin- oder Supportanfragen im Portal einreichen. Ordinavo haelt diese Anfragen in Pruefung, bis dein internes Team sie annimmt, ablehnt oder in operative Arbeit ueberfuehrt.
Customers can describe what they need and select an accessible location.
Customers can provide preferred dates or time windows as input for dispatch.
Managers review incoming requests before they become Ordinavo targets.
Accepted requests can become planned internal work with customer, location and contact context attached.
Portalnutzer sehen kommende Termine und einen reduzierten Status offener Arbeit fuer ihren freigegebenen Kunden- oder Standortkontext. Routing-Scores, Abrechnung und Dispatch-Notizen bleiben intern.
Show planned work with date, time, status and location.
Give customers a reduced view of active operational items.
Restrict appointment visibility to locations a portal user is allowed to see.
Translate internal statuses into customer-friendly labels.
Genehmigte Besuchsberichte koennen im Portal veroeffentlicht werden, wenn sie kundensichtbar sein sollen. Anhaenge werden separat freigegeben, damit Teams genau entscheiden, was Kunden herunterladen koennen.
Only approved reports can be released to the portal.
Use portal-specific titles, summaries and messages instead of exposing internal notes.
Share only the files that are intended for the customer.
Attachments are downloaded through controlled portal endpoints, not public file links.
Die Portal-Timeline zeigt eine reduzierte, kundensichere Historie aus Anfragen, Terminen, freigegebenen Besuchsberichten und Follow-ups.
Customers can follow submitted requests from review to planned work.
Show customer-safe milestones without exposing internal operations.
Make follow-up requirements and planned follow-up work visible.
Webhook deliveries, billing triggers, mapping warnings and routing internals stay internal.
The Customer Portal is designed around explicit access, limited data exposure and role-based visibility.
Give customers a secure place to submit service requests and track shared status.
Share planned appointments, visit documentation and follow-up status with site contacts.
Keep property managers and location contacts informed without exposing internal planning.
Coordinate recurring store visits, reports and follow-ups with external location managers.
Let partners submit operational requests and receive status updates through a controlled portal.
Show customers what matters: requests, appointments, reports, attachments and follow-ups while your team keeps planning and execution under control.
No. The Customer Portal is a separate external access layer without the internal Ordinavo sidebar, admin features or operational views.
Customers can submit requests. These requests are reviewed internally before they become operational Ordinavo targets.
No. Approved visit reports must be explicitly published to the portal. Attachments also require separate release.
No. Access is controlled through customer and location grants. Portal users only see information made available to them.
Only if attachment access is enabled and the specific attachment has been released for portal visibility.
No. Billing triggers, webhook delivery logs, API keys, mapping warnings and internal integration details remain internal.