For SaaS providers
Your product reports new users to 5sDesk via the API, and your website sends enquiries through an embedded form. Customer, company and deal are created without retyping, and your sales team sees at once who is trialling. When the customer pays or cancels, the card moves with them. When they write to support, it becomes a ticket on the same customer.
Life after launch
Whoever registered is in your own database. They only show up in the CRM once someone exports a list and imports it.
Which company is trialling right now, when the trial ends and who is already paying: the sales team finds out from one-off queries or not at all.
A trial customer's support request lands in a different tool from their deal. Nobody in support knows they are about to sign.
How it runs
This is how we run 5sDesk ourselves: our product writes every sign-up to our own sales board via the API, and enquiries from the website come in through a 5sDesk form.
Anyone who wants to talk to you before trialling submits the form on your website. Customer, company and deal sit in the "Contacted" column, and your Google Tag Manager counts the conversion.
Your backend calls the 5sDesk API and creates the customer with email, name and company. If the address already exists, from the form for example, the API returns the existing customer instead of creating a second one.
In the same run a card appears on the sales board, with deal value, probability, expected close date and custom fields such as plan and trial end. The history shows that it came in via the API.
The sales team assigns the card, plans the next action and writes to the trial customer straight from 5sDesk. Replies land on the same customer, and the sales pipeline shows totals per stage.
When the trial customer writes to your support mailbox, it becomes a ticket with a number and an owner. The customer record and deal sit alongside, so support can see that a deal is about to close.
When your payment system reports the first charge, your backend moves the card to "Paying". The deal counts as won and shows up in the reporting.
When a customer cancels, the card lands in "Cancelled", with a close reason such as "Too expensive" or "Feature missing". A webhook reports the move back to your system.
The features behind it
Create and update customers and companies, put cards with deal fields on the sales board and move them between columns. If your system repeats a call because a response got lost on the way, there is still only one entry. In the other direction, 5sDesk reports new customers, moved cards and new tickets by signed webhook.
For enquiries before the sign-up, you embed a 5sDesk form on your website with two lines of code. Every enquiry becomes a customer, company and deal in the stage of your choice. The form reports views, starts, errors and submissions to your website's Google Tag Manager, waits for consent from your cookie banner and sets no cookies of its own.
Connect your support mailbox and every email becomes a ticket with a number, an owner and a deadline. The customer record, deals and earlier requests sit next to the ticket. Support sees who is trialling and who is already paying, and sales sees which questions a trial customer has asked.
Whatever your product knows about the customer, the API writes to custom fields on customer and card.
REST API and webhooks from Basic
A card from sign-up or form
Conversions in the tag manager
One customer record
Cancellation reasons in the reporting
Create an API key, embed the form, connect your support mailbox. Try it for 30 days in Basic or Pro.
