Loading
Because support signs up for its own tool, which arrives with an empty customer table. It is filled from email addresses, and within a year it disagrees with sales about who the customer even is.
A customer in Desk is the organisation record the whole workspace shares, carrying support entitlement, contacts and every ticket ever raised.
There is one organisation record. Desk adds entitlement, support contacts and ticket history to it; Flow owns the relationship and Books the billing.
A group raises tickets from three trading names. They sit as one customer with several contacts, so entitlement is applied once and history is visible across all of them.
It will not decide whether to help a non-paying customer. It shows the arrears and the entitlement; the decision is a person's, made knowingly.
Flow's contract and renewal date, Books' invoice position, Loop's delivery, and every ticket, are all on the same record.
Yes, where the contract names them, with others flagged as unentitled.
The position, not the detail, unless permitted.
Yes, with the ticket attributed to the right one.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.