FS-DOC-01Operations
Launch Plan
Support Reporting and Insights
[YourCompany.com] · Customer Support Department · Prepared by FullSpec · [Today's Date]
This Launch Plan gives you a clear picture of what is being built, how the build is structured, what FullSpec needs from you to get started, and what your day-to-day role looks like once the automation is live. FullSpec handles every technical step from configuration through to go-live. Your role is to provide access to your existing tools, confirm one key decision before build begins, and review the monthly deep-dive commentary once the system is running.
01What you're launching
Right now, someone on your support team spends up to two and a half hours per report cycle manually exporting ticket data from Zendesk, cleaning it in Google Sheets, calculating metrics, writing a summary, and distributing the result by email and Slack. When that person is unavailable, the report simply does not happen. This automation replaces that entire manual pipeline with three connected agents that run on a schedule, calculate metrics consistently, generate a plain-English commentary, and deliver the finished report to every configured channel without anyone needing to lift a finger for daily and weekly cycles. The monthly deep-dive retains a short human review step so your Support Manager can read and approve the commentary before it goes out.
Process
Support Reporting and Insights
Trigger
Scheduled report time is reached (daily, weekly, or monthly cadence) or a manager requests an ad-hoc metrics snapshot
Final output
Report email via Gmail, Slack summary post, live Looker Studio dashboard, and a new Notion log entry, all delivered within 5 minutes of the schedule firing
Agents being built
3 agents: Data Fetch Agent, Reporting Agent, Distribution Agent
Tools involved
Zendesk, Google Sheets, Looker Studio, Gmail, Slack, Notion
Volume
Approximately 4 reports per week across daily, weekly, and monthly cadences (approximately 280 runs per month)
Launch PlanPage 1 of 4
FS-DOC-01Operations
02How the build works
FullSpec builds this automation in four sequential stages spanning four weeks. Each stage has a defined set of actions for the FullSpec team and a small set of inputs or confirmations required from you. The stages are designed so that nothing blocks unnecessarily: FullSpec begins work the moment Connect closes and credentials are confirmed. You do not need to be available throughout the build, only at the points flagged below.
Complexity level: Moderate. Estimated delivery: 4 weeks (approximately 20 business days) from the close of Connect. The delivery clock starts at the close of Connect, not payment.
1Connect
Business days 1 to 2
FullSpec
Reviews your existing Zendesk configuration and API access tier, maps the current report templates and metric definitions, confirms distribution recipients and cadence schedules, and documents all findings before build begins.
You
Share API credentials and tool access for Zendesk, Google Sheets, Gmail, Slack, and Notion. Confirm the list of metrics that matter most to your leadership team and the recipients for each report type. Approve the agreed metric definitions before build starts.
2Build
Business days 3 to 16
FullSpec
Builds and tests the scheduled Zendesk API query and Google Sheets write step (Data Fetch Agent, days 3 to 5). Builds the metric calculation logic, Looker Studio connection, and AI commentary generation (Reporting Agent, days 6 to 10). Configures Gmail templates, Slack message format, and Notion log append for all three cadences (Distribution Agent, days 11 to 16).
You
Available to answer questions if a metric definition is ambiguous or a report format needs clarification. No active tasks are required from you during this stage unless FullSpec flags a blocker.
3Test
Business days 17 to 18
FullSpec
Runs two full simulated reporting cycles across daily, weekly, and monthly cadences. Validates metric outputs against a manual benchmark. Tests the monthly human review step and all delivery channels. Documents any discrepancies and resolves them before handoff.
You
Review the test report outputs and confirm that figures match your expectations. Flag any metric or format issues to FullSpec within one business day so they can be resolved before go-live.
4Launch
Business days 19 to 20
FullSpec
Activates the live schedule, confirms the first real report fires correctly across all channels, briefs the Support Manager on the monthly review step, and hands over the full documentation suite including the SOP, Integration Spec, and Developer Handoff Pack.
You
Confirm the first live report looks correct and notify FullSpec if anything is missing. Brief any stakeholders who will receive reports so they know to expect automated delivery going forward.
Launch PlanPage 2 of 4
FS-DOC-01Operations
03What FullSpec needs from you
FullSpec only needs access to your existing tools. No technical knowledge is required on your side. The table below lists exactly what is needed for each tool and when to have it ready. Everything in this list should be in place before Connect closes so the build can start without delay.
Zendesk
An API token generated from your Zendesk Admin panel, your subdomain URL, and confirmation of your current Zendesk plan (to verify API rate limits).
Before Connect closes
Google Sheets
Access to the existing reporting spreadsheet (or confirmation that a new one should be created), plus Editor-level sharing with the FullSpec service account email provided at Connect.
Before Connect closes
Looker Studio
Editor access to the existing Looker Studio report, or confirmation that a new report should be created. The Google account used must have permission to connect to the Google Sheet.
Before Connect closes
Gmail
OAuth authorisation from the Google account that should send report emails, plus the confirmed distribution list (names and email addresses) for each report cadence.
Before Connect closes
Slack
A Slack bot token with permission to post to the designated support channel, and the exact channel name or ID for each report type.
Before Connect closes
Notion
An internal integration token from your Notion workspace with access to the reporting log database, and the database ID for the log page.
Before Connect closes
Key decision to confirm before Connect closes: For the monthly deep-dive report, a human review step is built into the pipeline. The Support Manager must confirm whether they want the review notification sent by email, by Slack direct message, or both, and what the approval timeout window should be before the report is held or escalated. This is the one configuration choice that cannot be set by FullSpec without your input, and it must be agreed at Connect so the Distribution Agent is built correctly from day one.
04Your role once live
Role
Ongoing responsibilities
What you no longer touch
You (business owner / Support Manager)
Review and approve the AI-drafted commentary for the monthly deep-dive report (approximately 5 minutes per month). Add or remove report recipients by notifying support@gofullspec.com. Adjust the metric list or report cadence if your team's needs change. Flag anything unexpected in a live report to FullSpec.
Manual Zendesk CSV exports, spreadsheet formula maintenance, report template updates, PDF exports, manual email or Slack sends, and Notion log entries. All of these are handled by the automation on schedule.
FullSpec
Monitors the automation for failures or unexpected outputs. Applies fixes if a Zendesk API change, Google Sheets schema change, or tool update breaks any part of the pipeline. Handles re-authorisation of OAuth connections when tokens expire. Responds to support requests at support@gofullspec.com.
Not applicable. FullSpec is responsible for the technical layer in its entirety.
Launch PlanPage 3 of 4
FS-DOC-01Operations
05What success looks like
Timeframe
What to expect
Sign of success
Week 1
The automation fires on schedule for the first live daily and weekly reports. Metrics land in the Google Sheet, the Looker Studio dashboard refreshes automatically, and the Gmail and Slack outputs are received by all configured recipients. The monthly review step notification reaches the Support Manager via the agreed channel.
Every report arrives within 5 minutes of the scheduled time with no manual action from your team. Recipients confirm they can see figures in the email and Slack message.
Month 1
Approximately 4 reports per week run without incident. The Support Manager completes the monthly review step in under 5 minutes. No formula errors occur. The team notices that the report no longer depends on any single person being available.
Zero missed reports across all cadences. The Support Team Lead has reclaimed roughly 20 hours of their month. Stakeholders receive consistent, correctly formatted outputs every cycle.
Month 3
The pipeline is running reliably across all three cadences. Your team has visibility of support performance through Looker Studio at any time, not just when a report is sent. The Notion log contains a complete historical record of all reporting periods. Any metric definition adjustments requested during month 1 or 2 have been applied by FullSpec.
Approximately 63 hours of staff time saved since go-live, consistent with the projected savings of 5 hours per week. Leadership has access to support data on demand rather than waiting for a weekly email. The process no longer stalls when any team member is away.
Next step: share this plan with your Support Manager and confirm the monthly review step preference (email notification, Slack direct message, or both) and the approval timeout window. Once those are agreed, book your Connect session with the FullSpec team and have your tool credentials ready. The build clock starts the moment Connect closes. Reach out at any point to support@gofullspec.com.
Launch PlanPage 4 of 4