FS-DOC-01Operations
Launch Plan
IT Helpdesk Request Handling
[YourCompany.com] · IT Department · Prepared by FullSpec · [Today's Date]
This Launch Plan gives you a clear picture of what is being built, how the build unfolds, and exactly what FullSpec needs from you at each stage. It is written for the business owner or IT manager overseeing this project, not for a technical audience. FullSpec handles every step of the build, testing, and go-live. Your role is to provide tool access, confirm one configuration decision before work begins, and monitor the results once the automation is live.
01What you're launching
Right now your IT team receives support requests across email, Slack, and web forms, reads each one manually, decides on priority by feel, copies details into a tracker, and then chases stalled tickets themselves. This takes roughly 90 minutes of productive staff time every day. The automation being built replaces the intake, triage, assignment, notification, SLA escalation, and knowledge base logging steps entirely. When a request comes in it is classified and prioritised in seconds, routed to the right technician automatically, and both the requester and the technician are notified straight away. If a high-priority ticket stalls, PagerDuty fires an alert without anyone scanning the queue. Every resolved ticket writes itself to the Notion knowledge base. The two steps that stay human are working the ticket itself and approving genuine escalations.
Process
IT Helpdesk Request Handling
Trigger
An employee submits an IT support request via email, web form, or Slack command
Final output
Ticket resolved, requester notified, and resolution summary written to the Notion knowledge base automatically
Agents being built
3 agents: Triage and Priority Agent, Assignment and Notification Agent, Escalation and Resolution Logger
Tools involved
Freshdesk, Slack, Google Workspace, PagerDuty, Notion
Volume
~90 requests/month (312 workflow runs this month across all steps)
Launch PlanPage 1 of 4
FS-DOC-01Operations
02How the build works
FullSpec runs the build across four sequential stages: Connect, Build, Test, and Launch. Each stage has a clear owner for every action so nothing falls through the gaps. The FullSpec team handles all technical configuration, agent training, and integration work. Your involvement is focused on providing access and giving timely feedback during testing. The four stages below map directly to the delivery timeline for this process.
Complexity level: Moderate. Estimated delivery: 15 to 18 business days total. The delivery clock starts at the close of Connect, not payment. Delays in providing tool credentials or historical ticket data will extend the timeline accordingly.
1Connect
Business days 1 to 3
FullSpec
Reviews the mapped process, confirms agent scope and tool connection list, sets up the shared project workspace, and sends you a credential checklist with step-by-step instructions for each tool
You
Complete the credential checklist for Freshdesk, Slack, Google Workspace, PagerDuty, and Notion; confirm your SLA thresholds and business hours; provide at least two weeks of historical ticket data for agent training
2Build
Business days 4 to 13
FullSpec
Builds and trains the Triage and Priority Agent against historical ticket examples; configures category rules and P1 to P4 priority logic; builds load-balanced assignment logic in Freshdesk; connects Slack notification steps for requesters and technicians; configures PagerDuty SLA escalation rules; builds the Notion knowledge base writer triggered on ticket resolution
You
Remain available to answer questions about edge-case ticket categories or unusual priority scenarios; no technical action required during this stage
3Test
Business days 14 to 16
FullSpec
Runs end-to-end tests across all ticket categories and priority levels; verifies Slack notifications fire correctly for both requesters and technicians; confirms PagerDuty alerts trigger on SLA breach; checks Notion knowledge base entries are structured correctly; documents any failures and fixes them before handover
You
Review a set of sample test tickets and confirm the triage outcomes look correct for your business; flag any category or priority result that does not match your expectations so FullSpec can tune the rules before go-live
4Launch
Business days 17 to 18
FullSpec
Switches the automation live on the confirmed go-live date; monitors the first batch of real tickets through the full workflow; delivers the SOP and Runbook to your IT manager; confirms all alerts and notifications are firing in production
You
Brief your IT team that the new process is live; redirect any lingering manual intake channels to the new structured intake path; confirm with FullSpec that the first day of live traffic looks correct
Launch PlanPage 2 of 4
FS-DOC-01Operations
03What FullSpec needs from you
FullSpec needs only access to your existing tools. No technical knowledge is required from you or your team. FullSpec will send you a step-by-step credential guide for each tool listed below so you can complete this in under 30 minutes. All credentials are stored securely in the project environment and are not shared beyond the build team.
Freshdesk
Admin API key and confirmation of your SLA time targets for P1 to P4 tickets
Before Connect closes
Slack
Workspace admin approval to install the automation platform's Slack app; names of the channels to receive requester and technician notifications
Before Connect closes
Google Workspace
OAuth authorisation for the shared support inbox so the automation can read incoming emails; admin consent may be required
Before Connect closes
PagerDuty
API key with full access and the name or email of the escalation target for P1 and P2 SLA breach alerts
Before Connect closes
Notion
Integration token with write access to the knowledge base page or database where resolved ticket summaries will be stored
Before Connect closes
Historical ticket data
At least two weeks of past ticket examples (category, description, and priority) used to train the Triage and Priority Agent
Before Connect closes
The one decision you must confirm before Connect closes: What are your SLA time thresholds for P1 and P2 tickets, and do those thresholds apply 24/7 or only during defined business hours? The PagerDuty escalation rules and the Freshdesk SLA policy are both built from this single answer. If it is not confirmed before Connect closes, the Build stage cannot begin on schedule.
Launch PlanPage 3 of 4
FS-DOC-01Operations
04Your role once live
Role
Ongoing responsibilities
What you no longer touch
You (business owner / IT manager)
Review the Freshdesk queue for genuine P1 escalations that require your judgement; update triage category rules in Freshdesk if new request types emerge; add or remove technicians from the assignment pool when your team changes; check the Notion knowledge base periodically to confirm resolution quality
Manual inbox monitoring, copy-pasting requests into a tracker, setting priority by gut feel, sending assignment and confirmation messages, chasing stalled tickets, writing knowledge base entries after resolution
FullSpec
Monitors automation health and alert firing accuracy; responds to support requests at support@gofullspec.com; applies fixes if any agent logic produces unexpected outputs; provides updated documentation when triage rules are adjusted
Not applicable: FullSpec does not touch day-to-day ticket work or IT operations decisions
05What success looks like
Timeframe
What to expect
Sign of success
Week 1
The automation handles all incoming requests through the structured intake channel. Early triage classifications may need minor rule adjustments as real-world ticket language varies from the training data. FullSpec monitors this closely and applies fixes without interruption to your team.
Every request that comes in creates a Freshdesk ticket automatically, with a category and priority assigned, and both the requester and technician receive a Slack notification within minutes of submission
Month 1
Triage accuracy stabilises as the agent has processed a full month of live tickets. The IT manager's time spent on queue management and stalled ticket follow-up drops noticeably. PagerDuty escalations fire only for genuine SLA breaches, not noise.
Average ticket response time is under 10 minutes; triage accuracy is above 90%; zero tickets are missed or sitting unassigned; knowledge base entries are being created for every resolved ticket
Month 3
The team is saving approximately 7 hours per week compared to the manual process. The knowledge base has accumulated three months of structured resolution data, making recurring issues faster to solve. The IT manager's daily queue management time is under 5 minutes.
Annualised staff time savings are on track toward $18,200/year; the Notion knowledge base is actively reducing repeat resolution time; staff and requesters are reporting a noticeably faster and more consistent experience
Next step: FullSpec will send you the credential checklist and project workspace link within one business day. Complete the credential checklist and confirm your SLA thresholds so the Connect stage can close on schedule and the build clock can start. If you have any questions before then, reach out to the FullSpec team at support@gofullspec.com.
Launch PlanPage 4 of 4