Resources/Core concepts/Contacts
Contacts
Contact: a person or an organization on your roster. A contact is not a user: a user has a login. A seat on a bond or certificate points at an organization and the person who represents it.
Contacts is your roster: the organizations you work with and the people at them. A bond or a certificate does not hold a name typed into a field. It holds a seat that points at an organization and at the person who represents it. When that person leaves, you reseat the person. The record does not break.
A contact is a roster record; a user has a login
| Thing | What it is | Example |
|---|---|---|
| Organization | A company or agency on your roster. Has a type. | Pacific Surety Partners, bond broker. |
| Person | Someone at an organization: name, title, email, phone. A person is a contact whether or not they can sign in. | The broker’s account manager. |
| User | A person with a login to Kuhlman. Only users can hold the ball, act on requests, or be on a team. | Your bond administrator. |
Kuhlman never treats a contact as a user. A sub’s estimator can be on your roster and seated on a bond without ever signing in. For some steps, such as submitting a retainage bond, we email them a secure link, and the record shows who acted. Anything else needs a login.
Every organization has a type
General contractor, subcontractor, owner, municipality, surety, broker, architect, lender, internal, other. The type is what the Contacts summary band counts and filters on. We count organizations you have not classified yet, but we don’t show a tile for them until you set a type.
A seat points at an organization and a person
Every bond seats a principal, an obligee, and a surety. Every certificate seats an insured, an insurer, and its holders. Each seat names an organization from your roster and, when you know it, a person at that organization as its representative. On a project, the Party representatives tab shows every organization seated on the project’s bonds and certificates, and lets you seat a person on the right one.
Seats are why a change of contact is a small edit. The organization stays. You point the seat at the new person. Every bond that seat touches is current.
We add contacts from email, and ask before we link
When an email arrives at your intake address, we resolve the people in it against your roster. When we recognize a person and their profile is complete, we link them silently and log it. When we recognize a person but their profile has gaps, we propose an item for you: complete their profile. We list only the fields the email showed. When we don’t recognize a person, we propose an item for you: create the contact. When an email address could match more than one person, we never link on a guess. You confirm the match.
You work with contacts on these screens
| Screen | What it shows |
|---|---|
| Contacts | A summary band by organization type, then the list of organizations and people. Click a type tile to filter. |
| Organization | One organization: its people, the projects and records it is seated on. For a GC, a Licenses tab that external parties see filtered to the jurisdictions they share with that GC. |
| Add contact | One wizard for a person or an organization, starting at which one you are adding. |
| Project → Party representatives | Every organization seated on that project’s bonds and certificates; seat a person on the right one. |
We use these terms
- Contact
- A person or an organization on your roster.
- User
- A person with a login. Kuhlman never mixes up a user and a contact.
- Party representative
- The person you seat to act for an organization on a bond, a certificate, or a project.
- Organization type
- General contractor, subcontractor, owner, municipality, surety, broker, architect, lender, internal, or other.
- Match
- We attach an email address to a person already on your roster. You confirm any match we are not sure of.
Read next
Product pages that build on this concept: Keep contacts current · Share a bond's status