The detail rail beside the conversation. It carries the identity header (name, stage, value), the core facts a builder needs — phone, email, address, building type, source, start and due dates — the answers they gave when they became a lead, their voicemails, recordings and photos, and the chips that jump to their pipeline card and estimate.
Also called: customer details · client file · contact card · customer record
The facts about the customer sit next to the conversation, not behind a tab
Phone, email, job address, building type, source, what the deal is worth and where it stands, all on one rail beside the thread. Where an internal 3D design exists, the record carries a summary of the actual building rather than a button that says open the estimate. Three screens to see one customer is three screens a rep will not open while somebody is on the phone.
A phone or an email you can add while the customer is still on the line
Both rows are always shown and always editable, even when empty — click, type, Enter. They used to be hidden when blank, which meant a contact with no number had no Phone row and no way to add one, and you found out when a text failed.
What they said they wanted, on the screen where you ring them back
The questions and answers from the form that created the lead render on the contact, with the campaign and source beside them. Calling a lead back without knowing what they asked about wastes the first thirty seconds of the only conversation you get.
The job address is stored as street, city, state and zip, because the permit check reads it
One free-text line has to be guessed back apart, and a guess here quietly puts a building in the wrong jurisdiction. Four fields mean the permit lookup, the crew drive and the delivery all read something clean, and anyone can add or correct it in seconds instead of waiting for the lead form to have collected it.
Two clicks from a text message to that customer's estimate
Chips on the record move between the contact, their pipeline card and their estimate — one person, three views, resolved from a single store so the surfaces cannot disagree. Where no pipeline card exists yet, the chip becomes Send to Pipeline and creates the link from the place you went looking for it.
‘fb ad’ and ‘Facebook lead’ stop looking like two different sources
Source strings arrive in a dozen shapes from forms, imports and manual entry, and each is matched to one brand mark so a list of leads can be scanned for where the work is coming from. A source nobody recognises keeps its original text beside a neutral dot rather than being hidden.
- 1Reads the contact from the canonical pipeline_synthetic_contacts store
- 2Core fields are inline-editable in place; edits save through /api/contacts/details
- 3A build summary card renders when an internal 3D design exists for the contact
- 4Sections collapse independently and the panel is width-draggable
The contact details said nothing about the build itself — just a link to open the estimate — so a rep on the phone with a customer had to leave the conversation to remember what the person was actually buying. By the time they got back the customer had asked something else. One panel now holds reachability, the building, the source, the address, the lead-form answers, the media and links to the estimate and pipeline card, so the facts sit beside the conversation instead of behind a tab.
- Customer facts split across CRM, estimate and pipeline
- Needing to open the estimate just to remember what the building is
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →