14-day free pilot · with your own jobs
AUTOMATIC ROUTING · FIELD SERVICE MANAGEMENT
Assign jobs to eligible teams and put visits in order automatically. Your office follows the day in one dashboard; technicians see their next address on their phones.
or leave your details and we will call youWeb dashboard for the office · Android app for the field
SOUND FAMILIAR?
In field service, money is usually lost between jobs rather than in them: in planning, on the road and in missing information.
The first hour of the day goes on “who goes where”.
Rotaris builds the plan in seconds from appointments, job durations and team availability.
Teams criss-cross the city and visit the same district twice a day.
Visits are ordered automatically to shorten the route; when an urgent job comes in, the plan updates itself.
When a customer asks “where is the team?”, you have no answer.
The live map shows each team’s position, next job and estimated arrival.
At the end of the day, finished work is pieced together from paper, messages and photos.
The team fills in the service form on the phone; the signed PDF and the end-of-day report are produced automatically.
ROUTE CALCULATION
Nine jobs are ordered area by area, the way an office does it by eye. Rotaris orders the same jobs to shorten the route; see the difference yourself and try again with new addresses.
Sample day · 9 jobs
Square: the team’s starting point. Numbers show the visit order.
Manual order: area by area as seen from the starting point, nearest first. Calculated on sample addresses as straight-line distance × a road factor of 1.3. Rotaris builds the real plan with appointments, job durations, team availability and the real road network.
Want to see it with your own jobs?In a free 14-day pilot we build the plan together with your own job list.
THE COST OF A SCATTERED ROUTE
Every extra kilometre means fuel, vehicle wear and paid team time that never turns into work. Enter your own figures and see the monthly and yearly cost.
02 · Recovered
Recovered per month in this scenarioPer year
Monthly km = vehicles × daily km reduction × days. Fuel = km × consumption ÷ 100 × price per litre. Team time = km ÷ average speed × hourly cost. Wear = km × maintenance per km. Yearly = monthly × 12.
This is a scenario, not a savings guarantee. The result depends only on the values you enter; subscription costs are not included.
Want to see it with your own jobs?In a free 14-day pilot we build the plan together with your own job list.
IN THE FIELD
The field team opens the next job, fills in the form, adds photos and a signature and sends it. Without internet the record waits on the phone and is sent when the connection returns.
Location is collected only while a shift is open; staff consent is collected in the app.
END OF THE DAY
14-DAY FREE PILOT
Use it for 14 days with one team and your own job list. We set it up together; no commitment, and the decision is yours at the end of the pilot.
Ask for a pilot on WhatsApp ↗Call +90 552 520 78 00Enter your name, phone number and company; we will call you and plan the pilot together.
The 14-day pilot is free and needs no commitment. If you want to continue, we make an offer based on your teams and vehicles; if not, the pilot account is closed.
In the field app the team only sees the next job: set off, start, fill in the form, send. We show the team together during setup; the pilot is there to try exactly this.
The price depends on the number of vehicles and users in the field. At the end of the pilot you get a clear offer for your own team setup.
The field app is currently for Android. The office panel works in current browsers on computers, tablets and phones.
No. Your company needs a Rotaris account and you need an assigned user. Office staff sign in to the web panel; field staff use the Android app.
Previously synchronised assigned jobs and related information can be viewed. Forms and results are saved on the device and pending records are sent when the connection returns. The first sign-in and receiving new data require a connection.
Fields and reusable sections can be defined for each job type. Forms are versioned and published changes synchronise to the app. The service PDF is generated according to company and document settings.
Branches work with their own teams, settings and daily plans. Managers can see company-wide information, operators see their assigned branches, and field staff see their own team's jobs.
The dashboard supports Excel job imports. Before starting, we review a sample file’s columns and customer and address matches with you to agree the import scope.
Prepare your team and branch structure, a blank service form, job types and a sample job list if available. These inform form fields, access permissions and routing rules. You do not need to share real customer data in the first discussion.
Location tracking is limited to active shifts. Company administrators see their company; operators see assigned branches; field staff see their own team's jobs. The phone setup includes disclosure and permission steps. Appropriate company texts and settings are reviewed during setup.
DETAILED PRODUCT TOUR
Route examples, a service job step by step, reports, customer and device history, stock, documents and setup.
ROUTING IN DETAIL
Route examples from real demo days, the urgent-job flow and the hand-over from office to field.
The address, appointment and estimated service duration are added to each job.
Jobs are assigned to suitable teams, with visit sequences and estimated arrivals calculated together.
Teams follow the current sequence on their phones. New jobs or team changes prompt a review of the plan.
Jobs already under way stay in place. On busy days jobs remain on the route and on the team's phones, while the office can review the plan.
A SMALL PRODUCT TOUR
Try reading the location, stop duration and result together across three example visits.
Interactive teaching example · names, durations and the diagram were created for this tour. Actual demo reports follow below.
EXAMPLE VISIT · 01
45 minutes describes time at the location. Work performed, parts used and the signed service record belong to the job detail.
Explore the actual service record ↗EXAMPLE VISIT · 02
The checklist, technician's note and maintenance result remain linked to equipment history. The next maintenance is evaluated using the configured rule.
Explore equipment history ↗EXAMPLE VISIT · 03
Being at the location does not mean the job was completed successfully. The reason and any note are recorded as part of the result.
What happens in this situation? ↗Exceptions leave a record too. These explanations describe the workflow without changing any live job.
The technician records an appropriate unsuccessful result and any required note. Reasons and possible charges depend on company definitions. The office uses that record to decide the next action.
The operator chooses a new planned date. A postponed job stays out of routing until that date, when it returns to the planning pool.
Previously synced jobs can be viewed and results can wait on the device. A record is not considered delivered until the server acknowledges it. First login and fetching new jobs require a connection.
From an open job, the team uses “Notify office” to leave a note and can mark it urgent. The office reply appears in that job’s conversation.
Example note: “The customer wants extra maintenance. Should we do it during this visit?”
Example reply: “Finish the current repair first; we will create a separate maintenance job.”
An “Office reply available” badge takes the team to the job conversation. A note sent offline is synchronised when connectivity returns.
An illustrative conversation between office staff and a field technician.
Example: the planned team changes before a visit has started. The office updates the existing job’s assignment rather than creating a copy.
The visit is assigned to Team A. Customer, address and job description belong to one work order.
The office assigns an eligible job to Team B. The relevant teams’ job lists update through synchronisation.
The job number and existing records remain. The assignment change can be followed in the job history.
Illustrative planning example. Jobs in progress or worked on while offline follow additional rules; this does not imply unrestricted reassignment in every state.
IN YOUR WORKDAY
Follow the job list, appointments and team status in one panel. When a new request comes in, review the plan and make the changes you need.
Open the address, equipment history and service form for the same visit in the Android app.
Find the detail you need, from completed jobs and daily routes to stop durations and collections.
DIFFERENT SERVICE ROUTINES
A door motor fault is linked to the customer, the entrance address and the equipment record.
Bring together the equipment's maintenance date, its checklist and previous work.
Different customer addresses and devices remain distinct as they join the teams' daily plan.
These examples explain existing capabilities; form fields and maintenance rules depend on company settings.
ONE JOB, START TO FINISH
Explore the plan, field progress and service result in three steps using a demo job.
The same job record: #1198
Screenshots show the Turkish product interface.
DEMO JOB #1198
Choose the customer, location and equipment. Add the visit to an eligible team’s daily plan.
DEMO JOB #1198
Follow departure, work start and completion on the same job timeline.
DEMO JOB #1198
Work notes, materials, signatures and payments come together in the service record.
Demo record · #1198
What to look forCustomer, team and planned date in one row.
What to look forA timestamped history from departure to completion.
What to look forWork, amounts and signatures in one service document.
Recorded in the admin panel
Review job #1198's history and collections. Then open the personal daily detail, stop map and day playback.
A short selection from the actual demo recording: planning, job history, collections and stops. Open a chapter below for the detailed tour.
Swipe sideways to see the other topics.
23 October demo plan: ordered team stops and their routes on the map.
#1198: a completed service job for Konya Plaza AVM.
Job history: departure, arrival, work and completion are linked to one record.
Materials used and the service fee are stored against the job.
This demo job totals TRY 5,940: TRY 2,970 collected and TRY 2,970 outstanding.
Daily report: review job and team results for the selected date.
Open Emre Karaca's daily row: metrics, GPS trail, jobs and stops.
Review Team A's stops together on the map and in the list; filter by type and duration.
Focus on stop #1198: Konya Plaza AVM, 10:03–10:57, 55 minutes.
Replay the day; select a stop to move the time slider to that moment.
A CLEAR VIEW FOR MANAGERS
Bring completed jobs, working hours and payments into one report. See where a team stopped, how long they stayed and which jobs were deferred.
Review results and points that need attention for your chosen period. Look at the team, staff and daily records behind the summary.
Review actual travel, visit order and travel outside the expected route. The shortest order uses the same start and end points but excludes appointments and urgency, so the difference alone is not a measure of performance.
Turkish demo interface · Period: 3 November 2026 · Captured on 4 November.
Use the job report to review why work was deferred, how often it was deferred and which jobs were paused.
THE DAY'S TRAIL, INSIDE THE REPORT
Open an employee’s daily record to review the addresses visited, stop times and job outcomes together.
23 October 2026 · Team A · Emre Karaca · Actual demo records
Reports → Daily staff summary → Emre Karaca
Job #1198: 10:03:11–10:57:49 is approximately 54 minutes 38 seconds. Rounding to the nearest minute produces 55 minutes; the time labels omit seconds.
23 October 2026 · Team A. Only the route layer changes on the same panel map. Position, zoom and job pins stay the same. The plan view shows a dotted line; the recorded journey view shows the solid GPS trail.
These are demo records. The images show how the plan and recorded journey can be reviewed; the difference between the lines alone does not demonstrate fuel or time savings.
Three views of the same day: the full shift, time spent travelling and time at one selected location.
55 minutes belongs to one stop. Travel and this single stop do not add up to the whole shift; other jobs and intervals also exist. Stop duration alone is not a measure of labour time.
Swipe sideways to see the other topics.
Open a person's row to see daily metrics, the GPS trail, jobs and stops. The team summary shows team totals; the personal detail shows that person's trail.
Filter by team, person, stop type and minimum duration. Select a stop in the list to focus the map on its location. This demo day has 13 Team A stops and no unplanned stops.
Emre Karaca's stop at the Konya Plaza AVM job location: 10:03–10:57. The map's 55 label is a duration in minutes, not the visit order.
Select marker 1 or 2 on the map to inspect the corresponding field.
Choose a date, play the trail or move along the time slider. Selecting a stop moves playback to that moment and shows the person's position on the map.
Play the demo video ↗GPS loss and offline intervals are shown separately in reports. This demo day has zero minutes of recorded GPS gaps. Location tracking operates only during an active shift.
Want to see it with your own jobs?In a free 14-day pilot we build the plan together with your own job list.
READY FOR THE NEXT VISIT
Keep customers, service addresses and equipment connected. Previous repairs, parts and maintenance dates are ready when the next visit begins.
Every visit is linked to the right address and device.
Find customer, address and equipment history in the same record. Review earlier service visits and parts before the next job.
Set equipment maintenance dates. When automatic maintenance is enabled, a job opens when it is due; an existing open maintenance job is not duplicated.
Track materials in central and team warehouses. Review the stock movement linked to a part used on a job.
What to look forPrevious visits stay linked to the customer.
#1198 · two control boards used on the job
What to look forA purchase / receipt movement: item, quantity, warehouse and date.
What to look forReview job outcomes by person and day.
The warranty expiry date is stored on the equipment record. Warranty information on the service form is considered together with the scope of that job.
A warranty date does not automatically make all parts and labour free. Scope and charges are assessed through the service record.
A test record prepared to demonstrate the stock connection. It is separate from demo job #1198.
In this rehearsal, one catalogued item was issued from the team's warehouse for this job. The job record, stock movement and remaining quantity were verified together.
Stock linkage depends on the catalogue item and selected warehouse. Typing a material name in a description alone is not stock consumption.
25 Oct 2026THE SERVICE RECORD
Keep the work performed, parts and customer signature together. Create the service document and track payments and the remaining balance from the job record.
Konya Plaza AVM
A readable summary of fields from the demo record, not an interactive data-entry form.
THE SAME JOB'S FINANCIAL RECORD
A partial payment does not hide the remaining balance when the job closes. The office can track the amount outstanding and its due date.
The total is 5,940 TRY, recorded payments are 2,970 TRY and the outstanding balance is 2,970 TRY. Completing the job does not mean the remaining payment has been collected.
Change the fault type to see how the form adapts. Choosing Motor reveals the serial number field. Your company’s form can use different fields and rules.
Use a sample value rather than a real equipment number.
The motor serial number field is hidden for this selection.
These fields only run this page’s example. Your entry is not sent to a server or saved in browser storage.
See how a partial payment changes the remaining balance. The amounts here are illustrative.
Illustrative breakdown: the first 2,000 TRY is 1,000 in cash plus 1,000 by card. A later 4,000 TRY transfer brings the total to 6,000 TRY. No actual demo job payments are changed.
After the first payment, collected money and the outstanding balance are shown separately.
ON THE TECHNICIAN'S PHONE
Addresses, equipment history and service forms are ready in the field. Prepare records for previously synced jobs offline; pending records are sent when the connection returns.
Try the sync states · illustrative example
Waiting to send. The record stays in the device queue until the server confirms receipt.
Follow a maintenance job on the phone: the form, photo, customer approval and submission. These images come from test job #5.
The technician fills in the maintenance checklist. Sections and fields depend on the schema published by the company.
The work note and photo attach to the same service record. Gallery selection is available when the company allows it.
The customer reviews the work summary and terms, then enters their name and signature. The screen shows a test stroke in the signature area.
An approved record waits on the phone while offline. This screen shows a pending submission, not a server acknowledgement. The queue retries when connectivity returns.
Android 1.0.14 rehearsal · separate from #1198.About the images and examples
Let's discuss our service form ↗Move to the app once your company account is ready. Permission screens can look different across Android versions.
Use the download link on this page. Android may request installation approval and permission for your browser to install an app; you approve the installation yourself.
Use the user account and password provided by your company. First login and fetching initial data require an internet connection.
Review the disclosure, location, notifications and battery settings in the order shown by the app. Location tracking is limited to active shifts; Android does not install silently.
Check that assigned jobs have arrived and review sync status. A pending submission and a server-acknowledged record are different states.
Want to see it with your own jobs?In a free 14-day pilot we build the plan together with your own job list.
SETUP
Product workflow, use cases and a getting-started checklist in a two-page overview.
Excel import on the work orders page uses customers, locations and job types already defined in the system. The check examines the file without creating jobs.
Download the panel template. Match columns such as customer reference or name, location label, job type and planned date to existing records.
Choose the file and run the check. Review total, valid and failed row counts and the reasons listed for individual rows.
Fix errors in the file, select it again and repeat the check. The panel enables import after a successful check with no errors.
| Customer ref | Job type | Planned date | Check |
|---|---|---|---|
| M-1001 | ARIZA | 26.10.2026 | Valid if existing records match |
| M-1001 | ARIZA | 32.10.2026 | Invalid date: correct the day |
These sample rows have not been imported. The customer and location must already exist. This is not an automatic migration service for every CRM.
Anonymous setup note · door and access systems service · based on product and setup records
THE STARTING POINT
The setup referenced a paper technical service form containing product and customer details, work performed, materials, amounts and handover signatures.
THE CONFIGURED WORKFLOW
Form sections for job types, result codes, company document settings and the signature workflow were configured. Output was arranged as a service PDF with document code and revision details.
This example shows the topics covered during setup.
We’ll agree the setup scope based on your existing files and workflow.
The company account, branches, roles and teams are configured.
Your service fields and materials are adapted to the way you work.
The Android app is installed and the first jobs synchronise with the assigned account.
FOR TEAMS WITH AN ACCOUNT
Sign in to the dashboard or Android app with the account provided by your company.
The Android app requires an existing company account. The web panel is available in your browser.
Checking the current release…
Android APK · A company account is required. Your browser may ask for permission to install the app.
