Files
smoothschedule/activepieces-fork/docs/handbook/customer-support/pylon.mdx
poduck 3aa7199503 Add Activepieces integration for workflow automation
- Add Activepieces fork with SmoothSchedule custom piece
- Create integrations app with Activepieces service layer
- Add embed token endpoint for iframe integration
- Create Automations page with embedded workflow builder
- Add sidebar visibility fix for embed mode
- Add list inactive customers endpoint to Public API
- Include SmoothSchedule triggers: event created/updated/cancelled
- Include SmoothSchedule actions: create/update/cancel events, list resources/services/customers

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-18 22:59:37 -05:00

51 lines
1.7 KiB
Plaintext

---
title: "How to use Pylon"
description: "Guide for using Pylon to manage customer support tickets"
icon: "hexagon"
---
At Activepieces, we use Pylon to manage Slack-based customer support requests through a Kanban board.
Learn more about Pylon's features: https://docs.usepylon.com/pylon-docs
![Pylon board showing different columns for ticket management](/resources/pylon-board.png)
### New Column
Contains new support requests that haven't been reviewed yet
- Action Items:
- Respond fast even if you don't have an answer, the important thing here is to reply that you will take a look into it, the key to winning the customer's heart.
### On You Column
Contains active tickets that require your attention and response. These tickets need immediate review and action.
- Action items:
- Set ticket fields (status and priority) according to the guide below
- Check the [handle request page](./handle-requests) on how to handle tickets
<Tip>
The goal as a support engineer is to keep the "New" and "On You" columns empty.
</Tip>
### On Hold
Contains only tickets that have a linked Linear issue.
- Place tickets here after:
- You have identified the customer's issue
- You have created a Linear issue (if one doesn't exist - avoid duplicates!)
- You have linked the issue in Pylon
- You have assigned it to a team member (for urgent cases only)
<Warning>
Please do not place tickets on hold without a ticket.
</Warning>
<Note>
Tickets will automatically move back to the "On You" column when the linked GitHub issue is closed.
</Note>
### Closed Column
This means you did awesome job and the ticket reached it's Final destination for resolved tickets and no further attention required.