How Spendesk consolidated its customer data into Forest for customer success and support

With Maylis Amram, Customer Success at Spendesk

Since its inception, Spendesk hasn’t had a real back-office solution. Like many growing companies, the admin wasn’t a priority as the customer-facing product needed continuous improvement. But with the increasing amount of users and operations, the need for advanced customer-management, support, data visualization and related questions arose.

A better way to access customer information

Guilhem Bellion - lead developer at Spendesk - started implementing Forest as Spendesk’s back-office last summer giving employees insight into customers’ in-app activity.

This new back-office solution made Maylis Amram - customer success at Spendesk - forget about old SQL queries she had to perform directly into the raw database to access customers’ information. This process used to require a lot of back and forth with the dev team and created frustration within the success team as they weren’t autonomous for more complex queries. It wasn’t scalable at all and they couldn’t see the Forest for the 🌲🌲🌲.

“It took me literally 1 min to set up Forest on Spendesk and I don’t have to worry about maintaining my admin anymore. The absence of a DSL makes Forest really easy to use with literally no learning curve.”

Guilhem Bellion, Lead developer at Spendesk

How Maylis had to access customer’s information
Spendesk main KPIs are accessible through their Forest’s dashboard (data misrepresentations) Onboarding workflow:
Waiting for KYB -> Waiting for KYB approval -> Waiting for funds -> Funds added

Before Forest, the data was split into different services (Full story, Intercom,, SQL queries, etc.) and getting access to basic information such as the number of users or recent payments would take dozens of minutes. With Forest’s dashboard it’s a matter of seconds and all the KPIs are aggregated in one place.

Managing customer workflow now easy as pie with segments

It usually takes a week for a company to be fully onboarded on Spendesk. An audit from a bank (Know Your Bank) is required to make sure the company is solvent. If the company is approved, it can transfer funds to its Spendesk account and employees can start making requests.

To better keep track of this onboarding workflow, Maylis created different segments into Forest. In the “Companies” collection, without any code, she selected filters (ex: ‘Companies’ is ‘Waiting for funds’) and saved the resulting view into a segment. In a single click, the support team can now have an overview of all users stuck in these different steps and be more proactive in their follow-up.

Powerful search combined with smart views and custom actions

When it comes to fixing an issue on a payment request, Spendesk’s support team must be highly responsive.

They needed to visualize in no time all the information related to a customer while being on the phone with them. Thanks to Forest’s flexibility and customization Guilhem created a smart view of each company profile. By typing the company name in the search bar, Maylis has access to the data she needs to serenely engage conversation with users. She can also extend their free trial, set up a discount, order a physical credit card, etc. in the blink of an eye as those specific actions are directly implemented in the account smart view.

Smart view of customer information with custom actions (discount, refund, etc.)
“With Forest I no longer have to leave my admin to answer customer emails or refund payments. Everything is performed in the same place. It’s truly helpful to me, keeping the same context throughout all my customer success operations.”

Maylis Amram, Customer Success at Spendesk


Forest saved a considerable amount of time to the development team. They were able to allocate their technical resources on the product without dealing with support’s matters.

Thanks to its easy customisation, Forest has given more autonomy to sales and support teams. It helps them to keep the same context throughout all the customer success operations as they can smoothly navigate through the relationship tables (from a user, to its card number, to its card activity, etc.).