Connect support@, billing@, customers@, or any other group email and have those messages flow straight into Pylon for unified tracking and faster responses. Connect as many addresses as you need.
Link a personal inbox like bob@company.com to pull both historical and future emails into account activity, so customer conversations live alongside the rest of the account record.
Synced email feeds Pylon's AI-generated context, improving notebooks and account summaries with the real substance of your customer communication.
Pylon backfills historical messages from Gmail or Outlook and keeps activity updated in near real time, automatically associating each email with the right account through domain matching and other context signals.
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. In your Pylon dashboard, go to the Settings page and open the Email tab.
Enter your support address — support@, billing@, customers@, or any other group inbox — in the Receiving Email field. Add as many addresses as you need.
On the config page, copy the email address Pylon generates for you. This is where your inbound mail will be routed.
Following your email provider’s forwarding instructions, configure your group inbox to automatically forward incoming mail to the Pylon address you copied.
Click Test to confirm forwarding is working correctly before going live.
Link your personal Gmail or Outlook account (e.g., bob@company.com) to Pylon to begin syncing email into account activity.
Once connected, Pylon backfills your historical messages and automatically associates each email with the correct account using domain matching and other context signals.
Relevant messages appear directly in account activity, and only emails tied to accounts you manage are surfaced.
Yes. Pylon lets you add as many group email addresses as needed. Each one forwards to a Pylon-generated address and flows into your support queue as tracked issues.
A group/support email (e.g., support@company.com) creates trackable issues from inbound customer messages. A personal email connection links your individual inbox, so one-on-one threads with customers are visible in Pylon, even if they never went through the support queue.
Yes. Connecting a personal inbox pulls in both historical and future emails into account activity in Pylon.
Pylon uses domain matching and other context signals to automatically associate each email with the right account, no manual tagging required.
Connecting a personal email (e.g., bob@company.com) automatically syncs your inbox and pulls your historical and future emails into account activity. Only emails relevant to accounts you manage will appear in Pylon.
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.
