Pylon

Pylon is the first support support system ever to offer a swimlane layout. This is insanely powerful for B2B companies. This video demonstrates how easy it is to setup a swimlanes for priority, to better visualize critical vs non-critical issues.

Want an integration we don't support yet? Leverage Webhooks in Triggers. You could... - Send an alert to Rootly - Pipe product feedback into Productboard - Start a Zapier flow Happy building!

We're hiring for an Ops Manager at Pylon! You'd be the first generalist working directly with Marty Kausas, Advith Chelikani, and Robert Eng to execute on all types of work including... - Finance - HR - Events - Legal - Office - Our upcoming Korea offsite 🇰🇷 👀 ...and so much more. It's a catch-all role. What we're looking for in any applicants: - Self-starter - Fast learner - Super diligent

You can set a custom Opengraph image previews for your Knowledge Base. These images will expand when you send your KB to your customers over Slack, Teams, and more! Example link image expansion: https://lnkd.in/gsUMFyzs

I love Spam Masubi, but I hate SPAM if you know what I mean. You can now mark emails as spam from Pylon. After marking as spam, emails from that domain will no longer pollute your issues board. So now you can focus on the spam that matters.

The Next Gen of GTM Tech is Here 🚀 The past few months I have been absolutely stunned by the brand awareness, hype and growth that early stage companies in the sales enablement space have been able to create (RB2B announced hitting $1M ARR in just 16 weeks). It almost seems as if they are paying all their customers and random people all over the internet to post raving reviews about them on LI, (which for the sake of this post I hope they aren’t!) Many of these companies are filling gaps left behind by the legacy lead database companies like ZoomInfo, Salesloft, or even Apollo.io. 🪨  In case you’ve been under a rock, some of these are: Clay - Data Enrichment RB2B - Identity level website visitor data Unify - Intent-based sequences for warm outbound Sendspark - Personalized dynamic videos at scale Warmly, - Identity level website visitor data Instantly.ai - Email sending and engagement Ocean.io - ICP lookalike data Honorable non-sales mention: Pylon - Unified customer support 🐶 Sales Enablement companies have a distinct advantage of being able to “eat their own dog food” using their own products to find customers, but these companies have been killing it with PLG and LinkedIn hype, despite not having raised much capital if at all, and most not having the massive followings of Adam Robinson. 🤔 Interestingly none of these companies are branding themselves as an “AI SDR/BDR” company, and instead focused on a subset of the sales contact/outreach workflow that will someday fall under the AI SDR umbrella, but they are foregoing that messaging to avoid skepticism from the mid market and above. Also strong trend of these founders “building in public” Who am I missing? Kareem Amin, Adam Robinson, Austin Hughes, Bethany Stachenfeld, maximus greenwald, Reio Suun, Michael Heiberg, Marty Kausas

We're hiring a Founding Marketer at Pylon! Your job? Feed our growing sales team qualified leads. How? We're going to run a LOT of experiments. Like... 1. Host events at the Pylon office 2. Create LinkedIn/X/YouTube content 3. Paid ads Maybe we'll even host a Pylon Conference 🎉 You and I will work together to figure it out. Requirements: 1. Must be based in SF and excited about fully in-person 2. 1.5+ years experience in a growth or marketing role at a SaaS startup Link in comments 👇

Come see one of my Co-Founders Marty Kausas speak at YC's Startup School on July 27th!

Migrating your Knowledge Base to Pylon just got easier. Introducing: Route Redirects ⤴️ If you're migrating from an existing Knowledge Base or deprecating an article in favor of a new one, you can create a redirect. For example /old-article-name → /new-article-name

We pride ourselves in stellar customer support at Unify, and feel grateful that our customers recognize us for it. Here's how we run customer support: We manage 90%+ of support over Slack. We love how personal this feels, but managing so many Slack channels can be painful. On top of that, our engineering team runs support. Engineering time is expensive, but there's no better way to align incentives than to have those who build the product fix the issues with it. We recently started using Pylon to solve this issue, which has been a huge unlock (s/o to our good friend Marty). Pylon is built specifically to solve customer support over Slack. We get 3 types of requests that require different treatment: bugs, feature requests, and product questions. 1) Bugs: the solution to a bug is to ship new code that fixes the root cause of the issue. Straight forward enough. 2) Feature Requests: we keep tabs on feature requests on our roadmap. We prioritize them based on the size of the customer(s) requesting, the number of requests, etc. 3) Product Questions: the root cause of product questions is giving users the right resources and making them easily accessible. This means great product documentation, which Mintlify helps us with. How do you manage customer support?