IT OPS
Urgent voice-complaint detection and escalation
Transcribes inbound voice notes, scores sentiment and urgency with an LLM, files the request in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerNew voice note in Google Drive folderGoogle Drive
- ActionTranscribe voice note with ElevenLabsElevenLabs
- ActionScore sentiment, urgency, and churn riskOpenAI
- LogicBranch on urgent churn-risk flag
- ActionCreate prioritized Linear issueLinear
- OutputPage on-call via PagerDuty when urgentPagerDuty
What it does
Separates calm feature ideas from urgent complaints. Every voice note is transcribed and analyzed for sentiment and urgency. Routine requests become Linear issues for the backlog; high-urgency, negative notes that mention cancellation or breakage trigger an immediate page so a human responds fast.
When to use it
Use it when voice intake mixes nice-to-have ideas with fires. Catching an upset customer's recording within minutes instead of next sprint can save the account.
How it works
- 1A new file in the Google Drive intake folder triggers the run.
- 2ElevenLabs transcribes the audio.
- 3OpenAI classifies sentiment, urgency, and whether churn or an outage is implied, and drafts a structured summary.
- 4A logic branch checks the urgency and churn flags.
- 5The request is filed as a Linear issue with the right priority label; if flagged urgent, a PagerDuty incident is also opened for on-call.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Connect PagerDutyIncidents, on-call, escalations.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.