LoginSign Up
← Back to all sparks
P

Pylon

SUPPORT
Velocity0.0

Pylon is wrapping intelligence layers around customer support and feedback.

customer-supportproduct-intelligenceai-agentsautomationintegrations
◆Current state
Pylon ships weekly bundles across four pillars: Support System, Product Intelligence, Account Intelligence, and AI Agents. November introduced Product Intelligence (auto-extraction of feature requests from interactions) and Google Meet ingestion. January and February layered Salesforce/HubSpot contact sync, Linear bidirectional comments, account-notebook time filters, and dashboard drill-downs. March added event-driven task creation, customer-notification tracking on closed feature requests, reusable knowledge-base blocks, and native video. April brought bulk project actions, contact phone numbers in issues, and task/project triggers.
◆Where it's heading
Pylon is positioning as a customer-support-plus-intelligence platform that closes the loop from incoming signal to product action. Bidirectional ties to Linear, Jira, Salesforce, and HubSpot make it the connective tissue between support and the rest of the org. Expect AI Agents and trigger automation to absorb more of the manual routing work, and Account Intelligence to keep deepening its analytics surface.
◆Prediction
The next directional move likely connects AI Agents and triggers into multi-step autonomous flows that route, escalate, and close issues. The intelligence layer is likely to add more data sources (Zoom, Gong, intercom logs) and surface predictive metrics like churn risk on accounts.

◆Recent moves

  1. 1mo ago

    Bulk Actions on Projects

    April release adds bulk actions across projects, contact phone numbers in the issue sidebar, and task/project triggers that fire on custom-field changes. Sharpens the project and automation layers.

    View source ↗
  2. 1mo ago

    Bulk Actions on Projects

    Duplicate publish of the April bulk-actions release, one day earlier. No new content.

    View source ↗
  3. 1mo ago

    Event-Driven Task Creation

    Event-driven task creation joins reusable knowledge-base blocks, native video playback, and a soft-delete-and-restore flow for issues and articles. Operational maturity across Support System and automation.

    View source ↗
  4. 1mo ago

    Event-Driven Task Creation

    Duplicate publish of the March 30 release notes one day earlier. No additional content.

    View source ↗
  5. 2mo ago

    Closing the Loop: Customer Notification Tracking

    ⚡ SPARK

    Customer Notification Tracking automatically scans issue messages, calls, and broadcasts to identify which accounts have been told a feature request is Done. Closes a loop the support-to-product handoff has historically dropped.

    View source ↗
  6. 2mo ago

    Product IntelligenceLeave comments in external systems (Linear, Jira, etc.) directly from a Pylon issueProduct IntelligenceRicher context on Linear ticket completion — see more detail on issues when linked Linear tickets are marked doneAccount IntelligenceConfigurable time and source filters on account notebooks — narrow insights to specific timeframes and data sourcesAccount IntelligenceDashboard

    Comments to external systems land directly from Pylon issues, Linear ticket completion shows richer context, and account notebooks gain time and source filters plus dashboard drill-down. Tightens the bidirectional integrations and analytics surface.

    View source ↗