Forum Discussion

fmaksad's avatar
fmaksad
Contributor 2
9 months ago
Solved

Multiple Branches

Hey Team,

I couldn't find something similar about this topic so I thought I'd post my own. 

We recently started a second branch of the same company and want to manage our jobs and data within Jobber but would love to have an easy way to separate the data when looking at the reporting screens. What are some suggestions how the best way to do that within the system without having to have 2 separate subscriptions?

Thanks in advance!

  • Hello! Thanks for bringing this to the community! 

    I recommend having two separate Jobber accounts for each branch as a best practice to keep things organized. 

    Alternatively, you could use Custom Fields on the job level to differentiate one branch from the other and use the fields to filter your reports! To set up the custom fields, please check out this article from our Help Center. 

    If you have any questions on this or anything else, please contact our Success Team 888-721-1115 ext 1 or email support@getjobber.com


4 Replies

  • jade's avatar
    jade
    Jobber Support Team

    Hello! Thanks for bringing this to the community! 

    I recommend having two separate Jobber accounts for each branch as a best practice to keep things organized. 

    Alternatively, you could use Custom Fields on the job level to differentiate one branch from the other and use the fields to filter your reports! To set up the custom fields, please check out this article from our Help Center. 

    If you have any questions on this or anything else, please contact our Success Team 888-721-1115 ext 1 or email support@getjobber.com


  • ryaantuttle's avatar
    ryaantuttle
    Jobber Ambassador

    I'd say separate accounts is best practice is you're trying to separate all of the data. You could always use a tagging system and some zaps, but that leaves a lot of room for human error. 

    • BrandenSewell's avatar
      BrandenSewell
      Jobber Ambassador

      I would agree. If both branches are self sustaining it would be ideal to have separate subscriptions. But I would also add that it depends how close the service areas are. For example, we have a branch in Orlando and one over on the coast. They are so close to one another it doesn't make sense to have a separate subscriptions from my experience. However, if it was something like North Florida vs South Florida I would have to separate them. 

  • BrandenSewell's avatar
    BrandenSewell
    Jobber Ambassador

    My suggestion is that if having a separate subscription isn't possible you could do a couple things. You could make one branch a certain color on your schedule. For example...Red Team is one branch and Blue Team is the other. Lastly, you could have a tagging system for each branch. Put a tag on each client based on which branch they are. Hope that makes sense. Interested in hearing how you end up approaching this.