Service businesses
Make the customer's request usable for the people doing the work.
Organize inquiries, services, appointments and follow-up tasks in one working environment, with a clear owner for the next customer step.
- 01Receive
- 02Clarify
- 03Deliver
- 04Follow up
The request is more than an appointment.
A service team needs the customer's requirements before arriving, and a record of what happened afterwards. Tsumira connects customer activities, project tasks and appointment organization. Start with a clearly bounded service rather than assuming every type of field operation fits the same process.
A concrete workflow
Receive
Record the service request, contact and essential preparation information.
Clarify
Resolve missing requirements before confirming the scope and appointment.
Deliver
Work from assigned tasks and record actual effort and observations.
Follow up
Assign remaining actions and communicate the agreed next step to the customer.
Collect enough detail to prepare the visit.
Use CRM to keep customer contacts and inquiry notes together. Describe the requested service and outstanding questions before assigning work. Relevant photos or documents can be kept in Drive, with access chosen for the people who need them. Recording an address does not by itself plan a route.
- Customer records and supporting files
Separate the appointment from the work plan.
A booking reserves a time; project tasks describe preparation, delivery and follow-up. Give each action an owner and a realistic deadline. The team can then see that a customer visit also needs a document check or an internal answer before the appointment takes place.
- Appointments, owners and preparation tasks
Capture the outcome while it is still clear.
Add service notes and actual time after the work. Discuss unresolved issues beside the customer or project record and assign the next action. Keep observations separate from promises: a follow-up request should be reviewed before becoming an additional commitment to the customer.
- Activities, time entries and follow-up
An illustrative working example
Illustrative scenario: a scheduled business service
A customer requests a site visit with specific access conditions. The coordinator records the conditions, assigns preparation and books the agreed time. After the visit, the responsible colleague documents what was completed and which issue needs another specialist. The next appointment is arranged after that review. Before the second visit, the coordinator checks whether the new work is part of the original agreement. The assigned colleague receives the current access instructions and a specific preparation task. Afterward, the team records what was actually done and which customer question remains. The pilot is successful when another colleague can understand that sequence from the record, rather than guessing that a second calendar entry means the first service was incomplete or approved for extra cost.
Questions about this topic
Is this a field-service dispatch system?
It supports customer work, tasks and appointments. Do not assume route optimization, vehicle dispatch or offline field applications are included.
Can we prepare files for a colleague?
Use Drive for supporting files and set access explicitly. Linking a customer record does not automatically share the file.
Does booking handle every local holiday?
The existing automatic holiday calendar is Japanese. Verify local opening rules before offering public bookings in another market.
Can we introduce only one service first?
Yes. Test intake, preparation and follow-up for one service before adding other teams or delivery models.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
