Pylon is a B2B customer support platform for teams that manage customer requests across Slack Connect, email, and in-app channels. Support teams use Pylon to track issues from shared customer channels and keep ownership clear across fast-moving accounts.
Customer Success teams use Pylon data to see which accounts need support attention before those issues become renewal risk. Custify mirrors Pylon tickets into the customer view so CSMs can review support volume and history next to health scores, lifecycle stages, and renewal data.
What can I do with Pylon in Custify?
Custify + Pylon imports B2B support tickets and turns Pylon activity into customer success context inside Custify.
- Import Pylon tickets as Touchpoints on the matching person and company in Custify, including messages, tags, assignee, and state.
- Match Pylon issues to existing people in Custify by requester email, then roll them up to the company level.
- Track total ticket counts and a breakdown by Pylon state: new, waiting on you, waiting on customer, on hold, and closed.
- Review the full Pylon ticket history inside the Customer 360 Profile, with a link back to the original ticket in Pylon.
- Segment customers by Pylon activity, such as high open ticket count or tickets sitting in waiting on you for too long.
- Trigger Playbooks when ticket counts cross a threshold, so CSMs get a task or alert when support activity needs action.
- Feed Pylon ticket data into Health Scores to include support load in the customer health view.
Custify + Pylon attaches tickets only to people and companies that already exist in Custify, so it does not create new records.
Common use cases
- Catch SLA risk early. Segment accounts with tickets stuck in waiting on you for too long, then follow up before the customer escalates.
- Prioritize by support volume. Put accounts with a high number of open Pylon tickets at the top of the CSM list.
- Add support signal to health. Feed ticket counts and state into the health score, so heavy support load shows up as risk.
- Respond to spikes automatically. Fire a Playbook when an account crosses an open-ticket threshold.
- Review B2B support history in one place. See the Pylon ticket thread inside the Customer 360 Profile, with a link back to Pylon for detail.
How does Pylon work with Custify?
Custify + Pylon imports Pylon tickets, matches them to existing records in tiers, and keeps them current on an hourly sync.
How matching works
- The requester email is the primary identifier. Custify matches it to a person, then rolls the ticket up to the company.
- If no person matches, Custify matches by Pylon Account external_ids.
- If that does not match, Custify matches by Slack channel ID. This requires a slack_channel_id custom attribute on the company in Custify.
What gets added to the account
- Pylon tickets imported as Touchpoints with messages, tags, assignee, and state
- Total ticket counts per account, plus a breakdown by Pylon state
- Full Pylon ticket history inside the Customer 360 Profile
- Link back to the original ticket in Pylon
How it works, step by step
- You connect Pylon to Custify with an API token.
- Custify runs an initial backfill of your existing Pylon tickets.
- Custify matches each ticket to a person by requester email, then by Pylon Account external_ids, then by Slack channel ID.
- Tickets roll up to the company with a breakdown by state, and the full history appears in the Customer 360 Profile.
- Custify runs hourly incremental syncs to pull anything updated since the last run.
How do I activate this integration?
Custify + Pylon needs an API token from a Pylon admin account.
- Generate your Pylon API token
- In Pylon, go to Settings > API Tokens.
- Generate a new token and copy the value.
- Connect Pylon in Custify
- Sign in to Custify and go to Settings > Integrations.
- Find Pylon in the list and paste the token into the Pylon API Token field.
- Confirm matching and save
- Confirm the company matching toggles. Account external IDs and Slack channel fallback are on by default.
- Custify tries to match each ticket to a company by linked person, then by Pylon Account external_ids, then by Slack channel ID.
- Click Save settings. The initial backfill starts automatically, and Custify then runs hourly incremental syncs.
Integration settings in Custify
The initial backfill imports existing Pylon tickets, then Custify runs hourly incremental syncs to pull anything updated since the last run. Two matching toggles, Account external IDs and Slack channel fallback, are on by default. For Slack channel matching to work, your companies need a slack_channel_id custom attribute populated in Custify. If that attribute is not set, the email and external ID matching tiers still apply.
Notes and important information
- The requester email is the primary identifier for Pylon ticket matching.
- Custify + Pylon only attaches tickets to people and companies that already exist in Custify, so no new records are created.
- Slack channel matching requires a slack_channel_id custom attribute populated on the company in Custify.
- Pylon conversations, chat, surveys, knowledge base, and CSAT are not imported. Only Pylon Tickets are imported.
FAQs
Can Pylon tickets trigger Custify Playbooks?
Yes. Pylon ticket counts and states can trigger Custify Playbooks when support activity crosses a threshold.
Can Custify use Pylon ticket state in customer health scoring?
Yes. Pylon ticket states such as waiting on you, waiting on customer, on hold, and closed can feed customer health scoring.
How does Slack channel matching work with Pylon?
Slack channel matching links a Pylon ticket to a Custify company through the slack_channel_id custom attribute when email and external ID matching do not find a record.
Does Custify import Pylon conversations or only tickets?
Custify imports Pylon Tickets only. Pylon conversations, chat, surveys, knowledge base, and CSAT are not imported.
Why connect Pylon tickets to Customer Success data?
Pylon tickets help CSMs see support pressure next to renewals, health scores, lifecycle stages, and customer history, instead of treating support as a separate system.
