See our recent webinar → Introducing Agentic Support
Choose exactly which tools Background Agent has access to — your knowledge base, connected integrations, codebase and logs, account data, internal APIs. Set the trigger conditions that determine when it runs. No hidden permissions, no surprises. Admins see everything.
Background Agent ships ready to investigate issues from day one. Tune it to your needs from there — check internal logs for specific error types, run different investigation playbooks for different issue categories, pull from different sources based on customer tier. Plain English configuration, no code required.
New information comes in after the agent already ran? Trigger a fresh investigation without starting over. Background Agent re-runs on demand and refreshes its findings — so your team always has the most current picture, not a snapshot from when the ticket first arrived.
Background Agent isn't only for pre-work. Set it up to auto-create Linear issues when feature requests come in, analyze response quality when tickets close, update knowledge base articles when new feature requests close, or kick off any background workflow your team repeats manually today.
A new issue, customer message, SLA risk, or incident triggers the right Background Agents automatically.
Humans or triggers kickoff agents that start investigating: reading the issue, pulling account history, searching your knowledge base, checking your codebase, logs, and connected tools.
Background Agents use the full context layer and approved tools to search support history, CRM data, Linear, logs, code, and internal systems.
Each agent posts its findings, evidence, and completed actions directly into the issue, organized and ready to review.
A Background Agent is a specialized support agent that runs automatically when a defined trigger occurs. It follows a skill, investigates across approved systems, and posts its findings or completed actions directly into the issue.
Background Agents can start when an issue arrives, a customer responds, an SLA approaches, an incident begins, or a scheduled event occurs. Teams choose the trigger that matches each support workflow.
Background Agents can investigate issues, triage and route requests, review quality, update records, monitor incidents, complete follow-up, and improve knowledge. Any repeatable support process that can be described as a skill can become a Background Agent workflow.
Background Agents run specialized support skills automatically when triggered. Assist Agent is the personal agent a teammate talks to directly when they want to ask a question, continue an investigation, or take action.
Yes. Pylon shows which agent is working, its current status, the systems it checked, and the results it produced. Each output is labeled and posted directly into the relevant issue.
Teams use natural language to define each agent’s trigger, instructions, tools, actions, and approval requirements. You can test an agent, review its output, change its instructions, rerun it, or require approval before it acts.
