Scheduling field teams across several branches in one tool

With a single branch, a shared calendar and a whiteboard last a long time. With several branches, scheduling becomes a collection of tools: one file per branch, individual calendars, phone calls to find out who is available, messages to confirm the appointment with the customer. Head office only sees the network’s workload by piecing the information together. And once the job is finally scheduled, the technician copies the address and the reason for the visit into another tool for the report.

The real issue is not the scheduling screen. It is whether scheduling is linked to everything else: the request, the quote, the technicians’ skills, the report and the invoice.

How does multi-branch scheduling work?

In internal software built by C-Esium, scheduling rests on a base shared by every branch:

1. The same data for the whole network: customers, addresses and the history of each address, technicians, skills and certifications. A piece of information is entered once and used everywhere.
2. The people actually available: the schedule is built on the people who are really available, not on a theoretical headcount. The hours logged on each job then feed payroll and working-time tracking.
3. A view per branch and a network view: each branch schedules its own teams; head office sees the overall workload and can arbitrate between branches.
4. Unassigned jobs are visible at all times, instead of sitting in a mailbox.
5. Confirmation to the customer: the appointment can be confirmed by SMS from the software, and the team calendar is synchronised.
6. The link with the field: the technician sees their day on their phone, with the case details. Their job report feeds the invoice directly (see automatic invoicing after each job).

You can also query the schedule in plain language, from the app’s chat, Claude or ChatGPT: “What is planned for tomorrow?” or “Which jobs are still unassigned?”. Access goes through a read-only MCP connector, restricted to authorised users and logged (how it works).

What does each profile see?

How do the options compare?

At Tech-O

Tech-O is a network of non-destructive water-leak detection companies, rooted in rope-access work and organised as a franchise network, with branches in Saint-Étienne, Ambérieu-en-Bugey, Annecy, Limoges, Bourg-en-Bresse and the Lyon area (France). It is a services company.

In the internal software built by C-Esium:

• sales, scheduling, technicians, head office and accounting work in a single tool;
• the team calendar is synchronised both ways with Google Calendar, and customer communication runs through built-in SMS and email;
• job reports are largely written by AI from voice notes, and invoicing is triggered by the job report;
• the MCP connector in production, with about 35 read-only tools, covers among other things today’s jobs, unassigned jobs, upcoming visits and the history of each address.

Across the whole software, the results are more than 3,000 hours saved per year, 30% operational gains and 20% fewer human errors. These are estimates made by C-Esium with Tech-O across field work, organisation, accounting, payroll, HR and management (figures published in October 2026).

What changes by sector?

• Services: short jobs, rounds, appointments to confirm with the customer, emergencies to fit in. This is the Tech-O case.
• Construction: teams assigned to projects over several days, with the skills and certifications each role requires.
• Industry: maintenance or after-sales technicians spread across several sites. Same approach, no published reference yet.
• Health and social care: scheduling staff across several facilities or services. If the tool holds health data, including in the details of a visit, the hosting arrangement and the scope of the AI are defined at scoping, in line with the applicable health-data rules; by default, AI assistants only access data that is not health data.

What can come after the V1?

These developments are not included by default. They rely on reliable scheduling data:

• AI-suggested team assignment, which the manager approves or corrects;
• staff management: certifications and checks to renew;
• cross-referenced recommendations, for example with the weather for outdoor jobs;
• automatic preparation of jobs and job reports.

How much does it cost and how long does it take?

Scheduling can start on its own, as a single module, and grow from there. Its full value comes from the link with the request, the report and the invoice.

• Price: as a focused project, from AED 40,000; inside a complete internal software, from AED 200,000 (excluding VAT; €10,000 / €50,000 in France). There is no per-user licence. The exact price is set after scoping in a firm quote, and payment is spread over the project milestones.
• Timeline: a V1 on a first focused scope is delivered in 1 to 2 months. Software covering every branch and every trade takes from 6 months to more than a year, delivered in batches, with a demo every two weeks.
• Switch-over: gradual. Your current tools stay in place in parallel, for safety, during the transition.

Budget benchmarks: page custom internal software.

When is it not the right option?

• You have a single branch and a small team. A well-kept shared calendar is often enough.
• Your scheduling rules are standard. A field service scheduling SaaS for your sector will do the job, faster.
• Your branches share no teams, customers or reporting. A common tool then has limited value.
• Branch managers are not involved in the project. This is the first risk: resistance and workarounds, with a parallel schedule still living in a spreadsheet. Change management, led at C-Esium by Cyrille Fantino, starts by meeting every profile.
• Nobody in-house can lead the project, or your budget is below AED 40,000.