Influx - Customer Support, Done.

Influx is a Melbourne, Australia-founded Customer Service as a Service (CSaaS) provider, established in 2013, built specifically around the idea that growing brands should be able to buy support capacity the way they buy cloud infrastructure, on demand, without long-term commitments or large setup costs.

The model is straightforward: Influx provides not just agents, but a complete support operation, agents, team managers, QA, automated training, and data reporting, packaged under a pay-as-you-go pricing structure. Clients can start with a part-time managed team from around $800/month, move to a pay-per-response plan, or scale to a dedicated 24/7 team from around $2,100/month. All plans run month-to-month with no setup fees, which is genuinely differentiated from traditional BPO contracts that lock you in for a year or more.

Influx operates as a fully remote, distributed company with localized leadership across Americas, APAC, and EU, covering 100+ cities. The follow-the-sun coverage model is central to their pitch, clients get consistent 24/7 coverage without managing multiple regional vendors. Service lines include general customer support, e-commerce support, SaaS technical support, back-office, and sales teams on demand. They also work with both human and AI agent workflows, which is increasingly relevant for teams looking to blend automation with live support.

The company has around 500 to 1,000 employees based on LinkedIn and independent headcount data as of mid-2026. Co-founders Leni Mayo (CEO) and Mikey De Wildt (COO) remain involved; De Wildt has a technical background including consulting work for NASA.

For the right buyer, Influx is a strong shortlist candidate. The month-to-month flexibility is genuinely useful for e-commerce brands with seasonal spikes, SaaS companies scaling post-launch, or any business that wants to test outsourced support before committing. I would ask specifically about QA depth, their model bundles management and QA, but I'd want to see what the actual quality scorecard looks like and how error patterns are escalated. I would also confirm language coverage for any non-English requirements before signing, since no specific supported language list is publicly documented.