Dashboard
Active tickets, queue, work in progress, completed jobs, incoming website requests, unpaid balances, overdue work, and next-in-line information.
What each part of the service portal would do.
This page breaks the concept into the different experiences that could make up the project. The Admin Portal is the private staff side, the Client Portal is the customer-facing side, and optional components can be added around them as needed.
CORE • STAFF SIDE
Admin Portal
The private working side used by Mac PC Rescue staff. Staff could receive requests, create and manage tickets, keep customer and device history, control the repair queue, record diagnostics, manage invoices and payments, and configure how the system works.
Daily shop operationsCustomers → Devices → Tickets → Queue → Repair → Payment → History
Ticket Management
Create repair, diagnostic, support, order, or other admin-configured tickets with customer/device details, reported issue, services, pricing, intake, notes, estimated completion, status and warranty information.
Customers & Devices
Reusable customer profiles with saved devices, previous work, active tickets, payments, balances, credits, warranties and communication history.
Repair Queue & Status
Track jobs through Received, In Queue, In Progress and Completed, with additional shop-specific statuses configurable in Admin Settings.
Services & Pricing
Admins build service categories and sub-services instead of hard-coding them. Services can have default prices and tax settings, with permission-controlled price changes per ticket.
Intake & Diagnostics
Configurable intake checklist plus structured diagnostic results for tests, findings, recommendations, repair estimates and customer-approval requirements.
Protected Password / PIN
When device access is required, credentials can be protected, hidden by default and restricted by employee permission. They should stay off customer invoices, public pages and ordinary search results.
Timeline & Communications
Chronological status changes, internal notes, calls, emails, texts, approvals, repair progress and payments, with Internal Only or Customer Visible entries.
Invoices & Payments
Itemized work orders with tax, credits, deposits, partial payments and balances. Manual payment records and possible PayPal integration can be supported.
Warranty Tracking
Record warranty dates, covered work, the related original ticket and warranty notes so returning service can be checked against previous work.
Search, Staff & Permissions
Global search for appropriate records plus individual employee accounts and permissions controlling sensitive information and actions.
Audit Log & Printing
Record important administrative changes and print customer-safe work orders/tickets or blank intake forms for busy periods.
IMPORTANT DESIGN GOAL
Admin Settings keeps the system configurable.
Ticket types, statuses, service categories, sub-services, default prices, tax rate, ticket numbering, intake checklist items, employees, permissions, warranty options, payment configuration and other shop behavior should be adjustable without rewriting the program for every change.
CORE • CUSTOMER SIDE
Client Portal
The customer-facing side. It provides useful service information without exposing the private Admin Portal or internal shop information.
How this part fitsConnected to the same service-management system
Service Status Lookup
Customers could verify a service ticket using appropriate information such as ticket number together with phone number.
Current Status
Show customer-appropriate repair status and estimated completion information without exposing staff-only notes.
Customer-Visible Timeline
Updates intentionally marked Customer Visible on the Admin side could appear as meaningful progress updates.
Invoice & Balance
Show eligible invoice details, payments already recorded and any remaining balance associated with the ticket.
Online Payment
If enabled, provide an online payment option. The backend should securely verify payment before marking an invoice paid.
Privacy Separation
Internal notes, device credentials, employee-only information and audit records stay on the private Admin side.
PUBLIC CONNECTION
Public Website Requests
The public website can remain the first point of contact while feeding service inquiries into the management system.
How this part fitsConnected to the same service-management system
Request Information / Service
Collect contact details, device information, what help is needed and the customer description.
Admin Request Inbox
Online requests appear in Admin so staff can review and record follow-up instead of relying only on general email.
Convert to Customer + Ticket
When an inquiry becomes real work, convert the information into a customer profile and ticket without retyping everything.
OPTIONAL ADD-ON
In-Store Kiosk
If selected, a dedicated tablet, touchscreen or computer at the counter could provide a limited customer self-service experience.
How this part fitsConnected to the same service-management system
Device Check-In
Collect customer, device and problem information for staff review before an official ticket is created.
Repair Status
Allow an in-store customer to perform an appropriate ticket-status lookup.
Service Request
Collect a new request and send it to the Admin side for review.
Session Privacy
Clear the previous customer information and return home after completion or timeout.
SYSTEM FOUNDATION
Backend, SQL & Future Expansion
The different interfaces connect through one application backend and SQL database rather than operating as disconnected systems.
How this part fitsConnected to the same service-management system
Automatic Notifications — Later Phase
Future email and/or SMS updates could cover status changes, approvals, completion, pickup or payment events.
Mobile Web App — Possible
A later installable web experience could provide staff quick mobile access to commonly used functions.
Simple Status Site — Optional
A lighter status-only site could provide simple service information when a full Client Portal is not needed.
Admin Portal
Client Portal
Public Website
Optional Kiosk
Secure Application Backend
SQL / MariaDB Database
Concept Reminder
These features describe a proposed project direction rather than a finished system. Individual features, workflows, security requirements, integrations and development phases can be changed after review with Mac PC Rescue.