Register for our upcoming webinar → Introducing the Agentic Support Platform
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.
The installation requires pasting a
The installation requires pasting a <script> snippet into your app's HTML before the closing </body> tag and passing user details after login. If you don't have direct access to your codebase, you'll need to involve an engineer, but the implementation itself is lightweight and straightforward.
Yes. Pylon supports multiple separate chat widgets, each with its own colors, branding, and workflows, which are useful if your company manages more than one product or serves distinct customer segments.
Yes. Pylon supports multiple separate chat widgets, each with its own colors, branding, and workflows, which are useful if your company manages more than one product or serves distinct customer segments.
Incoming chat conversations appear in Pylon's Issue Tracker and if configured, also to a designated Slack channel (e.g., #chat-support).
Yes. The widget can surface embedded knowledge base search, quick links, and ticket forms, giving customers a self-service path to find answers or submit async requests before a live conversation starts.
All of Pylon's support workflows apply to chat conversations just like any other channel. Triggers, AI responses, CSAT surveys, and SLAs are all available for chat issues with no separate configuration needed.
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.
