Pylon now lets admins control read and edit access to individual custom fields by user role. The 5 October changelog lists 41 updates in total.
Custom field value history now covers opportunities, projects, tasks and custom objects. Product-data syncs also merge repeated writes to the same object, which reduces noise in that history.
Admins can create triggers that fire once a meeting transcript is ingested. Custom roles can set different access by issue status. Macros have separate view and edit permissions, and Mark as Spam is now a configurable permission.
Support teams get ticket forms in Microsoft Teams, matching the Slack forms. Customers can reopen resolved tickets from Slack. Agents can pin issues above their inbox and drag them into order.
Source: usepylon.com