Embed live chat directly in your application so customers can get help in the context of your product without switching tabs or hunting for a support email.
Surface embedded knowledge base search, quick links, and ticket forms inside the chat so customers can find answers and submit async requests on their own.
Apply Pylon's Triggers, AI responses, and support workflows like CSAT and SLAs to every chat conversation, the same way you would across all your issues.
Fully customize colors, branding, light and dark themes, and workflows. Run multiple separate widgets with different branding for different products or audiences.
Open the Chat Widget settings in your Pylon dashboard and copy your APP_ID. You'll need it to connect the widget to your workspace.
Paste the Pylon <script> snippet just before the closing </body> tag in your index.html, replacing the placeholder with your APP_ID. Installing on your frontend may require an engineer if you don't have access to the codebase.
Set the window.pylon chat settings with the logged-in user's email and name (avatar, email hash, and account ID are optional). Add this wherever those details become available after login.
Create a Slack channel like #chat-support, add the Pylon bot if it's private, and set it as your Chat Support Channel so incoming conversations land somewhere your team can respond.
Toggle Enable Chat Widget on, then set your colors, branding, and workflows from the settings page to match your product.
In the ChatGPT Apps tab, search for Pylon and install the native Pylon app. Then navigate to Settings, then Connectors, and click Connect next to the Pylon MCP to authenticate via OAuth using your Pylon account.
A common use case is asking a question about a specific customer in ChatGPT and leveraging Pylon data alongside other connected tools like Notion or Linear for ad-hoc analysis.
No. Access is scoped to your own account permissions. The MCP cannot return data that the authenticated user cannot already see in the Pylon dashboard and cannot perform writes that the authenticated user cannot already make in the UI. Each team member who wants to use ChatGPT with Pylon can connect with their own account, so everyone operates within their own data scope.
OAuth sessions expire periodically. Some last a few hours. Others several days depending on the MCP client. When a session expires, you may see authentication errors or tools may stop returning results. This is normal behavior and not a bug. To reconnect, go to Settings, then Connectors in Pylon, and click Connect next to the Pylon MCP.
Yes, both use the same Pylon MCP server. The Pylon MCP Server exposes Pylon data to any AI tool that supports the Model Context Protocol, including both Claude and ChatGPT. Authentication uses OAuth 2.0, and the transport is Streamable HTTP.
Pylon connects with the tools your team lives in — Slack, email, CRMs, ticketing systems,and more. Meet your customers where they are and streamline every support workflow.
Receive and respond to customer messages from Telegram
Manage B2B support directly in Slack channels alongside your team.
Connect Pylon to Granola to ingest call recordings
Sync Outlook Calendar meetings to customer records in Pylon
Automatically capture and log Google Meet call notes to Pylon
Automcatically link active incidents to affected customer conversations.
Enrich customer records with usage data from Amazon Redshift.
Create Shortcut stories from customer conversations automatically
Trigger PagerDuty incidents from critical customer-reported issues.
