Computer Repair Ticketing and Operations System
An automated repair-request and ticket-management workflow using Google Forms, Google Sheets, Zapier, Gmail, and Slack.


Business problem
Without a ticket workflow, repair requests can be difficult to identify, prioritize, update, and communicate across customers and internal teams.
What I built
A form-triggered Zapier workflow creates sequential ticket IDs, tracks repair stages, sends status-based email updates, posts Slack alerts, and stores operational records.
How I built the workflow
Submit request
A Google Form captures the repair request.
Create ticket
A sequential ticket ID is generated and stored.
Track stage
The repair moves through Pending, Diagnosing, Repairing, and Completed.
Send updates
Customers and internal teams receive status notifications.
Tools and integrations
Key features
- Automatic ticket creation
- Sequential ticket ID generation
- Request tracking
- Repair-stage tracking
- Status-based email notifications
- Internal Slack alerts
- Customer updates
- Centralized operational records
Intended impact
- Repair requests are easier to track.
- Customer updates are standardized.
- Team visibility is improved.
Project results
Pending, Diagnosing, Repairing, and Completed are handled in one flow.
Email and Slack updates are sent from status changes.
Need a reliable operations automation system?
Share the bottleneck, tools, and desired outcome. I’ll help map the right workflow and a practical implementation path.


