Chainsaw Helpdesk
Admin Panel
12
Open tickets
3 unassigned
1.8h
Avg first response
Target <24h ✓
94%
Closed in 5 days
Target 80% ✓
0
Missed requests
Since launch ✓
All open tickets
IDRequestSource TypeStatus OwnerReceived
Content Library Support
Helpdesk
Requests
Submit requests, check status, and find answers. If you need something, start here.
Instant
Auto acknowledgement
<24h
Named owner
5 days
Most closed
Zero
Missed, always
Submit a request
Content, access, technical issue, or anything else.
Check request status
Every ticket you’ve raised, with current status and owner.
Find the answer yourself
BrandIn not loading? New laptop? Most issues answered here.
Escalate urgently
Flag it urgent and we’ll treat it as the top priority.
Your recent requests
RequestSourceStatusOwnerRaised
BrandIn not showing in PowerPoint toolbar
Technical · Compass One
Portal In progress
AP
Ash Phoenix
Today
System template — South County Health
Content · Crothall
Done
AP
Ash Phoenix
3 days
Configuration
Ticket intake methods
Client portalLive
Direct form submission. Client selects request type, adds context and deadline. Auto-acknowledged on submit, auto-routed to admin panel.
Email → ticketConfiguring
Emails to the designated address are parsed and converted into tickets automatically. Subject becomes the title; body the description.
helpdesk@wearechainsaw.com
Slack → ticketConfiguring
Any Slack message — channel or DM — flagged with the designated emoji is captured, parsed, and dropped into the admin panel as a draft ticket.
React ✂ to flag
S
Slack task parser — live demo
Flag any message with ✂ and the system breaks it down
Incoming flagged message
AP
Ash Phoenix#helpdesk-requests · 11:42am
Hey can someone sort a new slide for the Crothall EVS team at Baptist Health? Need a QBR summary slide matching their brand colours — aiming to use it by end of next week.
↓ Parsed automatically into draft ticket
Draft ticket created
TitleNew QBR summary slide — Crothall EVS / Baptist Health
TypeContent request
CompanyCrothall Healthcare
DetailQBR summary slide, Baptist Health brand colours
Deadline~End of next week
SourceSlack · #helpdesk-requests
Raised byAsh Phoenix
OwnerUnassigned — needs owner within 24h
Email → ticket — how it works
Parsed email — auto ticket
From: matthew.ratcliff@iammorrison.com → helpdesk@wearechainsaw.com
SubjectRE: System template for Ochsner Health System
TitleSystem template — Ochsner Health System (Morrison)
RequesterMatthew Ratcliff · Morrison Healthcare
TypeContent
Source
Any email sent or forwarded to helpdesk@wearechainsaw.com converts automatically to a draft ticket. Nothing waits in an inbox.
Client portal
Submit a request
Your details
Request details
Request received
Someone from the team will own this within 24 hours. You’ll get a confirmation email now with your reference.
REF: T-0049
T-0041
BrandIn not showing in PowerPoint toolbar
After syncing the content folder via OneDrive, the BrandIn tab does not appear in the PowerPoint toolbar. Files show as fully synced. Restarting PowerPoint made no difference.
Activity
Details
Actions
4
My open tasks
11
Team tasks this week
3
Due in 24h
Needs attention
100%
Tasks logged
Target met ✓
Internal task log
TaskTypeStatusOwnerDue
Wire Zapier email-to-ticket for helpdesk inbox
Automation
BuildIn progress
AP
Ash
Tomorrow
UX review — admin panel filter logic
Test + iterate
UXOpen
LT
Laura
Friday
Set up Fireflies call task capture trial
Automation
BuildOpen
AP
Ash
Week 3
Milestone 1 presentation — Billy review
Milestone
MilestoneOpen
AP
+
LT
End Wk 3
Document onboarding for Compass walkthrough
Launch docs
DocsOpen
AP
Ash
Week 6
Self-serve
Common questions
Just ask us a question
Every answer below comes from a question real users have already asked through the helpdesk
Can’t find the answer?
Standard
Tone of voice
The Chainsaw principle
“How you say something matters as much as what you say. This brief is about us holding to the same standard.”
Core principles

Write like this

Clear & directWarm, not corporateSpecific over vagueAction-firstAcknowledge then solve
“We’ve got your request — someone from the team will own this within 24 hours.”
“BrandIn not showing usually means the sync didn’t complete. Here’s how to fix it.”

Avoid this

Corporate jargonVague timelinesPassive voiceOver-formal greetings
“Your request has been received and will be reviewed in due course.”
“Dear Valued Client, We are writing to acknowledge receipt of your recent enquiry.”
Auto-acknowledgement
Hi [Name],

We’ve got your request — reference [T-XXXX]. Someone from the team will pick this up within 24 hours.

You can check status any time at [portal link].

Chainsaw
Status update
Hi [Name],

Quick update on [T-XXXX]: [one clear sentence — what’s happening, what to expect next].

If anything changes, we’ll let you know.

[Name], Chainsaw
Request closed
Hi [Name],

[T-XXXX] is done — [one sentence: what was delivered].

If anything else comes up, you know where we are.

[Name], Chainsaw
Client voice
Minimal. First sentence gets to the point.
Confirmatory. Tell them it landed and what’s next.
Reassuring. Someone real is handling it.
No jargon. No system internals, no tech language.