Why We Chose Slack-First Support (And Ditched the Ticket Portal)

When we started Foliox, we did what every SaaS company does — we set up a traditional support system. Ticket portal, knowledge base, and a "submit a request" form.

It lasted about three months.

The Problem with Tickets

Here's what we noticed: our customers are fuel dispatchers. They're managing deliveries, monitoring inventory, and coordinating with drivers all day. Asking them to go to a separate portal, log in, and write a formal support ticket was adding friction to an already high-pressure job.

Response times were decent, but the conversations were fragmented. Context was lost between tickets. And customers felt like they were talking to a system, not a team.

The Slack Experiment

We started small. For our first customer, we created a shared Slack channel using Slack Connect. Instead of tickets, they just messaged us.

The results were immediate:

Response time dropped to under 2 hours on average during business hours

Resolution time improved significantly — real-time conversation eliminates back-and-forth

Customer satisfaction went through the roof — dispatchers loved the direct access

Enter Pylon

The challenge with Slack-based support is tracking. How do you ensure nothing falls through the cracks? How do you measure response times?

That's where Pylon came in. Pylon sits on top of our Slack support channels and gives us:

Automatic issue tracking from Slack messages

SLA monitoring and alerts

Analytics on response times and resolution rates

Escalation workflows for critical issues

Integration with our internal tools

It gave us the best of both worlds: the speed and intimacy of Slack with the accountability of a ticketing system.

How It Works Now

Every Foliox customer gets a shared Slack channel with our team, set up automatically during onboarding. Fast async support outside business hours. Direct access to the team that built the product.

We'll never go back to tickets.

Learn more about our support →