The use case: how Findigs deploys Pylon
Findigs moved its customer support from Salesforce Service Cloud to Pylon, using it for ticketing, AI runbooks that triage incoming issues, and workflow configuration done by non-technical staff. It is also consolidating support, underwriting support, pet verification support, customer success and implementation teams into shared workflows.
More reported results
Figures published in Pylon’s case study. They are not independently measured by usedby.
Pylon's AI eliminated 30% of ticket volume immediately by removing disconnected chats.
AI runbooks now triage 10 to 15% of issues before reaching human agents.
Configuration that previously required a full day in Salesforce now takes 30 minutes in Pylon.
In the customer’s words
Salesforce would have required linear headcount growth, essentially doubling our team in the next few years. Pylon's AI allowed us to break that model and make each agent significantly more efficient.Other AI tools used by Findigs
Other public relationships recorded on usedby.
Explore Findigs’s AI stackOther companies using Pylon
Customers across industries, with public evidence.
See all Pylon customersGo straight to the source
Based on Pylon’s published case study. We check the public evidence; the results are reported by the vendor.
usepylon.com- Last checked
- Nov 17, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 2xChecked
Printed word for word on the page, near the name of Findigs.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Findigs.
- Findigs uses PylonChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Maintaining our growth trajectory on Service Cloud would have required doubling our support team. In the age of AI and automation, that doesn't make sense.







