












Every account shows a Last Meeting Date field, so your team always knows how recently they've connected with a customer without digging through calendars.
A Next Meeting Date field keeps the next scheduled meeting visible right where you work, so no account slips between calls.
Both meeting fields behave like any other custom field, so you can filter views, drive triggers, and build automations around when meetings happen.
Meeting dates appear in account activity and in the account and issue sidebars, giving your team timing context without leaving the ticket.


A Pylon Admin opens the Apps Directory, selects the Google Calendar tile, and clicks Connect to enable it for the workspace.
Once the workspace integration is enabled, each user navigates to the Apps Directory and selects "Connect Google Calendar" to link their own calendar.
After connecting, calendar events begin to backfill automatically and the Next Meeting Date and Last Meeting Date fields populate across the product.
It adds two custom fields, Next Meeting Date and Last Meeting Date, populated from your connected calendar events.
They appear in account activity and are viewable in both the account and issue sidebars.
Yes. The fields work anywhere custom fields are supported, including views and triggers.
A Pylon Admin must enable it for the workspace first; individual users then connect their own calendars.
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.