mosman.ai Case study · 02 / 04 All projects

Case 02 · Scheduling

One job.
One continuous journey.

Scheduling, field service, photo evidence, customer portal, invoicing and payment all work with the same job — without interrupting operations.

Web & mobileCustomer portalCross-system
4interfaces for office, field teams and customers
1shared job record
Reviewbefore delivery and invoicing

The system is in production; the people, jobs and figures shown here are anonymised sample data.

JSJavaScript CFCloudflare Telegram NNocoDB GGoogle Drive LxLexoffice PyPython Docker
Job scheduling · Service businessProduct view
ASSIGNMENTS · SERVICE
DayWeekStatusPortal
Thursday, 23 JulyToday
All teams12 scheduled3 openDeliveryCustomers
Team07080910111213141516
TNTeam North3 jobs
Garden work08:00 · Berlin MitteConfirmed
TSTeam South2 jobs
Fence installation10:30 · PankowMaterials ready
TWTeam West3 jobs
Service13:15 · KreuzbergCustomer informed
TodayThursday, 23 July•••
22°sunny · Berlin
by 12:00
JOB #248Garden maintenance · Mitte

Lawn · Hedge · Disposal

Confirmed
RouteStart assignment
Office and field teams in sync From appointment to invoice

The existing system was replaced without stopping operations. No big-bang migration and no downtime.

OfficeField teamCustomer

The starting point

Every handover invited another follow-up question.

A date was scheduled — but the team, customer, documentation and invoice were still far from sharing the same status.

Scheduling without context

Calendar entries and customer data had to be reconciled across different interfaces.

Information passed by word of mouth

Addresses, tasks and changes were passed to field teams separately.

Closing with broken handovers

Photos, service data and invoice items had to be collected again after the job.

Three workspaces, one job

Each role sees exactly
what it needs right now.

The data remains the same — only the interface changes between office, field team and customer.

01 · Office

Schedule with complete context.

Customer, service, team, status and billing stay connected to one job.

02 · Field team

The job arrives on the phone.

Address, tasks and questions are ready. Photos go straight back into the job.

03 · Customer

Results and documents without follow-ups.

A passwordless portal shows appointments, reports, photos and invoices for the right job.

Web SPA · Scheduling
Job scheduling · Day view4 teams
ASSIGNMENTS · SERVICE
DayWeekStatusPortal
Thursday, 23 JulyToday
All teams12 scheduled3 openDeliveryCustomers
Team07080910111213141516
TNTeam North3 jobs
Garden work08:00 · Berlin MitteConfirmed
TSTeam South2 jobs
Fence installation10:30 · PankowMaterials ready
TWTeam West3 jobs
Service13:15 · KreuzbergCustomer informed
JOB #248Garden maintenance · MitteConfirmed
CustomerPrivate customerTeamTeam NorthTime08:00–12:00

Mow lawn · Trim hedge · Remove green waste

MessageRouteOpen job
Telegram Mini App · Field team
TodayThursday, 23 July•••
Today
22°dry · Berlin
by 12:00
JOB #248Garden maintenance · Mitte

Lawn · Hedge · Disposal

Confirmed
by 15:30
JOB #251Service · Charlottenburg

Review · Photo report

Up next
RouteStart assignment
ROUTE18 MinOpen navigation
FOTOBERICHT4 / 4complete ✓
KUNDENotifiedMessage sent
AUFTRAGSSTATUSWhat is happening now?On site Work completedQuestion
Customer portal · Demo mode
Service portalMy appointments

GOOD TO SEE YOU

Hello!

YOUR NEXT APPOINTMENT

Saturday, 25 July

8:00–12:00 Uhr

Team North will visit you.

● Changeable weatherWe are monitoring the forecast.🌦 12–19°C
Mow lawnTrim hedgeDispose of green waste

System views

The job evolves.
Its history stays together.

Four views show the workflow from scheduling to a paid invoice.

One continuous process

Several specialised systems.
One clear interface.

Technical complexity stays in the background. In daily work, the job simply moves from one status to the next.

CustomerRequest & portal
SchedulingDate & team
Field teamTelegram & PWA
ReportPhotos & service
LexofficeInvoice
PaymentReconciliation & status

Rollout without downtime

Built new.
Proven safely in parallel.

The existing planner remained in place as a reference throughout the transition.

No big-bang change in daily operations.

New and existing workflows were compared throughout the transition. The switch happened only after reliable agreement was proven.

Delivery remains traceable.

Preview, approval and delivery tracking prevent duplicate or incorrect customer messages.

Next project · 03 / 04

From a scan to a deadline and the right response.

View document automation