Automation kit
Service Visit Kit
Planned: every request gets one record, an engineer, a visit due date, a check-in and check-out log, and a service report the customer signs.
Everything below describes the planned kit. The demo shows these ideas with a simulation. Nothing in this kit has yet been installed and tested in a real business; that is the next step.
The problem
Service requests, visit plans and reports live in different chats and notebooks, so nobody knows which customer is still waiting.
Who it is for
Companies that send engineers to customer sites for repairs and maintenance
Designed for (to be confirmed in pilot)
- Google Sheets
- Google Apps Script
- Google Forms on the engineer's phone
- PDF service report
The phone form is a simple Google Form. GPS tracking and offline apps are not part of the planned kit.
Planned first-release scope
- Request register with a unique ID, logged from calls, email or WhatsApp by your coordinator
- Engineer assignment by region, product or a list you set
- Visit due date from your service rule, and a past-due list
- Visit confirmation message prepared for the coordinator to send
- Engineer check-in and check-out from a phone form
- Work notes, spare-part needs and a second visit when required
- Service report generated from the visit log, for the customer to sign
- Manager summary: open requests, past-due visits, waiting for spares, unsigned reports
Not planned for the first release
- GPS tracking of engineers
- Automatic WhatsApp messages to customers
- Spare-part stock management (see the Store & Inventory Kit)
- Electronic signing or identity verification (a person collects the sign-off on paper or as a photo)
- Invoicing for service visits
Planned setup steps
- 1.Copy the Sheet template into your business Google account.
- 2.Fill in your engineers, regions and visit due rule.
- 3.Share the check-in form link with each engineer.
- 4.Authorise the script once with your own Google account.
- 5.Log a test request and run one visit end to end.
You need
- • A Google account owned by your business
- • Someone comfortable following a step-by-step setup guide
- • Engineers with a smartphone that can open a form link
Support
Support terms will be published with the first installable release.
Questions
- Is this available to buy today?
- Not yet. Today you can try the interactive demo. The installable kit is being prepared and will be tested in a supervised pilot before it is sold.
- Where is my data stored?
- The plan: in your own Google account and Sheet, with Google processing it as your service provider. Saran Labs AI would not receive your service records. This will be confirmed in the pilot.
- Does it track where engineers are?
- No. The engineer checks in and out on a phone form. There is no GPS tracking in the planned kit.
- Can customers sign on the phone?
- The planned kit records that a person collected the customer's sign-off, on paper or as a photo. It does not provide an electronic-signing or identity-verification service.
- Is this AI?
- The core kit is rule-based automation: checks, routing and reminders you configure. Optional AI features would be separate, clearly labelled add-ons.
Pending
What the pilot will confirm
These points are not decided or proven yet. They will be settled with a supervised pilot in a real business before the kit is offered.
Package contents
Which Sheet tabs, forms, report layout and guides are delivered.
Engineer forms
Whether engineers can check in and record work quickly on site, including with a weak mobile signal.
Due-date rules
How visit due dates work with working hours, holidays and contract types.
Report format
Which details the service report must show for your customers.
Use on phones
Whether engineers can comfortably update records from a phone.
Backup and export
How data is backed up, exported and restored.
Support terms
Support period, response times and what setup help includes. Pending founder decision.
For larger teams and organisations
Need multiple departments, approval levels or connections to existing systems?
We can assess a tailored implementation. Scope, security requirements and integrations are agreed before delivery.
Path 1
Standard kit
A planned, customer-owned Google Sheet configuration with documented limits, for small teams.
Path 2
Tailored implementation
Discovery first: we map your process, systems and requirements, then agree scope in writing before any build.
| Demonstrated in this simulation | Planned for the standard kit | Needs assessment / custom development |
|---|---|---|
|
|
|
Items in the last column are discovery topics, not available features. Nothing here claims enterprise readiness, certification or existing integrations.
Want it set up for your team?
Tell us how service requests reach you today and how engineers report back. We will tell you honestly whether this kit fits.