Connected records
The invoice already knows the client.
Convert a won deal and the invoice opens with the client and the amount on it. The client's tickets sit on the same record as their invoices.
Connected records in practice.
Follow one client from the deal to the invoice to the ticket, without typing their name twice.
The deal names a real client
A deal points at an account record, not at a company name somebody typed into a box.
Bruno FeltrinConvert to invoice, once
Convert to invoice on a won deal saves a draft with the client chosen and one line at the deal's amount.
Your services fill in the rest
Add a service from your price list and its price and default tax arrive on the line.
The ticket points at the same client
A ticket carries a requester and an account, the two records the deal and the invoice already use.
One record, one place to look
The client's page shows what is still owed and how much of it is overdue, what they paid over the last 12 months.
Nothing to integrate
The modules are already joined, so there is no connector to build, pay for or babysit and no overnight sync to be behind.
The thing five separate tools can't do.
Your CRM, invoicing, help desk, HR and inbox share one set of records, so the client on the deal, the invoice and the ticket is one client.
Change a client's billing email once
Every module has it.
Add a board of your own
It links to the same clients.
Calendly partner portalInvoice paid
The deal it came from moves to Won.
More in Spodus.
Each one is its own page, on the same records.
Connected records, on your own data.
Bring a spreadsheet or an export to a demo and see it there.
Questions, answered
No. Every module already reads and writes one set of records, so a deal, an invoice and a ticket are joined the moment they exist. There is nothing to connect and nothing to maintain.
You choose Convert to invoice on the deal. Spodus opens a new invoice with the client already filled in and a line priced at the deal's amount, and you check the lines and issue it. Nothing is invoiced behind your back.
It updates everywhere at once. The deal in the CRM, the invoice in billing and the tickets in support all read the same record, so no copy of the customer is left holding the old value.
On the client's own record. It lists their invoices with their status and due date, what is still owed and how much of it is overdue, next to the tickets raised against that account and how many are still open.
Yes. Import by CSV, with presets that map the export from common CRMs onto our fields for you, and everything you bring lands on shared records the rest of Spodus can use.
Yes. Add custom fields to what is already there, or build an object of your own, and relate it to the built-in records the same way they relate to each other.