On a phone
- Open the client from Contacts.
- Tap Edit. It is at the bottom of the screen, on the right, next to the round back arrow.
- At the bottom of the sheet that opens, tap the bin.
- Tap Yes to confirm.
On a computer
- Open the client from Contacts.
- Click Edit, at the top right of the client's page.
- Click the bin at the bottom of the sheet, then Yes.
It is gone straight away. There is no bin to fish it back out of.
Or ask Mucka
Tell Mucka which one — "delete the second Harbourside Lettings, it's a duplicate". In the chat it puts a Delete it button under its reply. On a call there is nothing to tap, so it reads back which client it means, says it cannot be undone, and deletes it when you say yes.
On a call, Mucka only deletes a client with nothing left on it: no jobs, quotes, invoices, certificates, service plans, reminders or saved cards. If something is still there it tells you what, so you can move it onto the client you are keeping (ask Mucka to move a job and it will) or delete it first. You cannot see the client's page on a call, so it does not let anything go with it by accident.
What stops a delete
A client with a job still to do, booked in or under way, cannot be deleted. Finish or cancel the job first.
If you delete a client from the bin who has finished jobs, quotes or invoices, those stay on file but no longer have a customer on them. The confirm line says how many jobs and quotes will be unlinked before you tap Yes. If the client is a duplicate of one you are keeping, merge the two instead: everything moves across and you can undo it for 30 days.
If the client is linked to Xero, QuickBooks or FreeAgent, the contact there is archived rather than deleted, because those packages will not delete a contact with transactions on it.
Who can do it
Owners and managers. Other roles need delete rights for clients, set under Settings, then Roles. If you cannot see Edit on a client's page, your role cannot change clients at all.
What you cannot delete
A client mirrored from JobLogic has no bin, because the next sync would bring it straight back. Delete it in JobLogic instead.