In our workflows, we frequently need to associate the same contact with multiple jobs. Examples include insurance carriers, individual adjusters, and city or county permitting offices. While JobNimbus allows a contact to be linked to multiple jobs, all activity, documents, and correspondence tied to that contact currently appear across every associated job. This creates clutter in job activity feeds and makes it difficult to determine which communication belongs to which job.
The feature request is for a more relational or context aware contact to job relationship. Ideally, contacts could still exist as centralized records, but when linked to a job, activity and documents would be scoped to that specific job context. From the job view, users would only see correspondence relevant to that job. From the contact view, users could see all associated jobs and optionally filter activity by job when reviewing past communication or documents.
An additional enhancement would be the ability to define contact types such as Insurance Company, Adjuster, or Permitting Authority and dynamically display only the fields relevant to that contact type. This would allow documents, requirements, and reference material to live on the contact record while still being cleanly linked to individual jobs.
This functionality would significantly improve automation capabilities. For insurance related contacts, job scoped relationships would allow for automated follow ups, reminders, and email sequences without referencing unrelated jobs. For permitting jurisdictions, this would allow teams to link a city or county to a job and store permit applications, inspection requirements, IRC code references, and licensing details in one place, while still triggering job specific tasks such as permit submission, inspection scheduling, or license expiration reminders.
For insurance carriers and adjuster contacts, this would allow teams to analyze historical interactions or previous scopes written, patterns, and approval tendencies across multiple jobs while keeping individual job records clean and readable. It would also enable more advanced adjuster based automation without cross pollinating activity feeds.
Overall, this feature would reduce noise in job activity logs, improve clarity across multi job stakeholders, and unlock more advanced automation and reporting use cases for companies that rely heavily on insurance carriers, municipalities, and third party contacts.