Job Customer / Client / Contacts

[Roger A]

We are a subcontractor that works for restoration firms who have clients. Our customers are the restoration firms and pm - they pay the bills. Not the home owner.

So in CC, the project is the job, the customer is the restoration firm but we lose track of the job contact (typically the home owner). We also can't easily keep track of the job number and purchase orders for the job and other administrivia. I'm currently putting that info into the description, but there's gotta be a better cleaner way

It would be great if the job info had that contact info like: Client name, email, phone, and generic notes
The job could have: Job number, purchase order.
The Customer field works for us as is.

 

[Megan M.]

Hey Roger, thanks for sharing your feedback!

What exists today, and why it probably isn't your answer: A Customer record can hold more than one contact — name, email, phone, and a role each. So technically you could keep the restoration firm as your Customer and add the homeowner as a second contact. The catch is that those contacts belong to the Customer, not the job, and would stay linked. We can totally see why that would not work. What you actually need is contact info that lives on the job, and that's the gap. I've logged your workflow against the request we're already tracking for.

On the job number and PO side: we've got work underway that'll let you put your own labeled fields on a Project so things like Job Number and Purchase Order have a real home instead of living in the description. No date I can promise you, but keep an eye in the app and the News Center for updates on Custom Fields.

In the meantime, two things that'll buy you some sanity:

• Put the job number right in the Project name, something like "24-1138 — 123 Maple St." Project names are searchable, so you can pull a job up fast from the feed.
• Keep a fixed block at the top of the description, similar to what you're already doing: Job #, PO #, Homeowner, Phone, same order every time. Not pretty, but it's scannable, and it'll be easy to lift into real fields later.

Thanks for laying out the actual workflow. We'll be sure to get this feedback in front of the right team!