Chapter 2

Customer, contacts and property

Co-owners and signers, recording consent to text and email, and where property data comes from.

Who: Sales repOfficeAll plans

Behind every lead are three records:

  • The customer is the household or company: the Whitfields.
  • Contacts are the people on it: Dana and Chris, each with their own phone and email.
  • The property is the house: 418 Harbor Rd, with its roof details, measurements and history.

A customer can have several contacts and several properties, and a property keeps its history from job to job.

Add the co-owner

Both Whitfields own the house, so both need to sign the contract. Add Chris as a second contact.

Add the co-owner · 23 s, no soundWho: Sales repOffice
Lead page with the customer name link highlighted in the Customer card
1The lead's Customer card links to the household: open it with the homeowner's name.
Add contact dialog for Chris Whitfield with Signs contracts switched on
2Add contact for each person on the account. Leave Signs contracts on for everyone who has to sign, like both owners.
Contacts card listing Dana Whitfield (Primary, Signer) and Chris Whitfield (Signer)
3Both owners are now contacts and signers. The primary contact is shown first and used for the Call and Text buttons.

ShingleSync won't send a text or email to a contact until you've recorded their consent for that channel. Record it when they agree, with the details: who agreed, when, and what was said or signed. If they ask you to stop, Opt out applies straight away, everywhere in your company.

Record consent to text · 12 s, no soundWho: Sales repOffice
Consent form for texting with Verbally selected and the evidence typed
1Before you text or email from ShingleSync, record how the homeowner agreed: who, when, and what was said or signed.
Consent ledger showing texting granted, verbally, with the evidence
2Texting now shows Granted, with your evidence. If the homeowner asks you to stop, use Opt out: it applies straight away.
The Text button on a lead opens your phone's own messaging app. Texts and emails sent from ShingleSync are the ones that need consent recorded here.

The property

Property page header with the Contractor-entered data source badge
1Every property shows where its data came from: Verified, Contractor-entered, Third-party or Estimated.
Property details card with property type, roof type, stories and roof age
2Add the roof type, stories and roof age when you know them. The property keeps its measurements and its lead and job history.
Where property data comes from matters. A badge shows whether each property's details are Verified, Contractor-entered, from a Third-party source, or Estimated. Storm data and lookups never prove damage; only your inspection does.