IT service providers
Keep the customer request connected to the implementation work.
Coordinate discovery, implementation tasks and customer follow-up without confusing a shared business workspace with infrastructure monitoring or a specialist service-management platform.
- 01Clarify the request
- 02Agree scope
- 03Implement
- 04Hand over
Separate what the customer needs from the technical solution.
An IT request may begin with a business problem rather than a technical specification. Record the customer contact, affected process and open questions in Tsumira before assigning implementation. The purpose is a clear commercial and delivery record, not an implied connection to devices, networks or telemetry.
A concrete workflow
Clarify the request
Record the business need and the customer contact who can answer questions.
Agree scope
Document prerequisites and the implementation boundary before promising a date.
Implement
Assign technical work, record effort and keep customer decisions traceable.
Hand over
Review instructions with the customer and capture remaining follow-up tasks.
Document the service boundary before work starts.
Keep the proposal and discovery notes alongside the customer relationship. State what is included, which prerequisites the customer supplies and who can approve a change. Use shared documents for implementation notes while specialist technical records stay in the systems that maintain them.
- CRM contacts and shared scope documents
Make dependencies visible in delivery tasks.
Plan preparation, implementation and customer acceptance as distinct tasks with owners. Track time spent on investigation separately from completed delivery work. If a colleague is waiting for customer access or a decision, record that blocker explicitly rather than leaving a deadline with no explanation.
- Project tasks, deadlines and time entries
Carry service knowledge into the next request.
Maintain handover instructions and customer-specific operating notes in Docs. Use the related conversation to explain what changed and what remains unresolved. Give access intentionally; a customer reference should not make sensitive technical material visible to everyone. Review AI drafts before applying or sending them.
- Shared knowledge with per-user access
An illustrative working example
Illustrative scenario: a workplace rollout
An IT provider organizes a customer rollout. Discovery captures the affected departments, project tasks cover preparation and handover, and the customer conversation records the agreed change window. The implementation team keeps technical tooling separate while Tsumira holds the commercial relationship, decisions and outstanding actions. The customer changes the available implementation window after preparation has begun. The project owner records that decision and checks which tasks need new dates. A technical colleague documents an unresolved access prerequisite without copying credentials into the project. The customer-facing handover explains what was delivered and which operational question remains. This tests the business handoff while monitoring and infrastructure records continue in their existing tools.
Questions about this topic
Does this include device monitoring or remote control?
No such capability is claimed here. Use the appropriate technical platform and treat Tsumira as the business coordination layer.
Is it a full ITSM replacement?
Check your incident, asset, escalation and service-level requirements individually. Shared tasks and communication do not establish those specialist processes.
Can we capture actual project effort?
Use time entries and the team's review process to record work. Agree how investigation, delivery and rework should be categorized.
Should credentials go into project notes?
Keep secrets in your approved credential-management system. Project records should describe ownership and required access rather than expose credentials.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
