One Contact, Multiple Companies

This guide covers how RebelPSA handles a person who is associated with more than one company — a common real-world situation for consultants, contractors, board members, and people who work across a parent company and its subsidiaries. It’s written to double as both a technician reference and a Q&A resource your customer service team can use when a customer asks a question about how their contact relationships work.

In RebelPSA, a Contact (a person) and a Company (an organization) are linked through a relationship record — not a single fixed field. That means the same person can be linked to more than one company at the same time, each link carrying its own role and its own primary/VIP flags, independent of any other company that same person is linked to.

This shows up in two mirrored places, since the relationship can be managed from either side:

• From the Contact’s own record, under a Relationships tab, showing every company that contact is linked to
• From the Company’s own record, showing every contact linked to that company

There’s exactly one link record per contact–company pair — you can’t link the same two records together twice. Trying to re-add an already-linked pair is silently ignored rather than creating a duplicate or throwing an error.

RebelPSA has separate concepts that all use similar-sounding labels. Confusing them is an easy mistake, and it’s exactly the kind of thing a customer might ask about in a way that sounds like it’s the same topic when it isn’t.

Contact–Company Role vs. Company Relationship Role

You can create the link from either side, and both paths lead to the same underlying record.

From the Contact’s Record

• Open the contact and go to the Relationships tab.
• Choose Add Company.
• Search for and select the company.
• Optionally choose a Role from the list (Decision Maker, Technical Contact, Billing, Executive, Former Employee, or a custom role your organization has added).
• Optionally mark this as the contact’s primary company.

From the Company’s Record

• Open the company and go to its linked contacts section.
• Choose Link Existing (to connect an already-existing contact) or Add Contact (to create a brand-new contact already linked to this company).
• Search for and select the contact (if linking existing).
• Optionally choose a Role and mark as primary.

The company-side screen additionally shows a VIP column, and its edit-relationship option includes a specific “VIP for this company” toggle.

Other Ways a Link Gets Created

• The new-contact wizard can link one company when a contact is first created.
• A bulk “assign company” action can link a company across many selected contacts at once.
• The mobile app has its own company picker screen for linking on the go.

The Primary flag is used in two different directions, and each direction only cleans up its own side:

• Setting a primary from the Contact side — “this is this contact’s home company” — clears primary status on that same contact’s other company links, so exactly one comes out primary for that contact.
• Setting a primary from the Company side — “this is this company’s primary contact” — clears primary status on that same company’s other linked contacts, so exactly one comes out primary for that company.

However, simply creating a new link and marking it primary at the moment of creation does not go through either cleanup step — so it is possible for a contact to end up with more than one company marked primary if that happens twice in a row. This is an edge case, not the normal day-to-day experience, but it’s worth knowing if something looks inconsistent.

What marking a company as primary impacts:

• The company name shown on the contact’s summary and in most contact list/search views
• Contact-level reports
• Which company’s activity feeds a contact’s help-desk metrics
• Portal invitations — which company a new portal user gets connected to
• Ticket creation — as a fallback when nothing else determines the company (see Which Company Does a New Ticket Belong To?)
• Inbound email resolution — as one step in a longer fallback chain (see Which Company Does a New Ticket Belong To?)

A contact can be flagged VIP specifically in the context of one company — this is set from the company side, alongside the role and primary settings for that link.

If a customer or colleague asks whether VIP status “does anything” beyond showing a badge, the honest answer today is: not yet.

This is the question most likely to come up in practice, and the answer depends entirely on how the ticket was created.

A Technician Creates the Ticket

• If the contact only has one company, it’s selected automatically.
• If the contact has two or more companies, the technician sees a company picker and must choose — it does not silently default to the primary company.
• If a company is explicitly specified at creation (by whatever means), that explicit choice always wins over any automatic resolution.

An Email Creates the Ticket

Inbound email resolves the company through a fallback chain, through the order below:

• A company whose email domain matches the sender’s domain.
• Among the contact’s linked companies, whichever one’s domain matches.
• The contact’s primary company.
• If none of the above resolve, the ticket is treated as ambiguous — depending on your mailbox settings, it either goes to a system “Unassigned” company or is created without a company at all.

The Customer Creates the Ticket via the Portal

A portal ticket doesn’t carry an explicit company on creation — it resolves the same way a technician-side fallback would: primary company first, otherwise the first linked company found.

RebelPSA separately supports Related, Parent, and Child relationships directly between two companies — for example, a holding company and its subsidiaries. This lives on the Company record’s own “Related companies” section and has nothing to do with a person belonging to multiple companies.

When two duplicate Contact records are merged into one, their company associations are combined as follows:

• Any company linked to the duplicate (source) contact but not already linked to the surviving (target) contact is copied over, carrying the same role — always added as non-primary, regardless of whether it was primary on the source.
• VIP status is not carried over on a merge — a copied link always starts as not-VIP, even if it was VIP on the source contact.
• If both contacts were already linked to the same company, the surviving contact’s existing role, primary, and VIP values win outright — there’s no side-by-side comparison or manual review step for that conflict.

Removing a contact–company link is a hard delete of that relationship record — there’s no start/end date field and no soft-close that preserves the link in an “inactive” state automatically. Once removed, that specific connection is gone (though the contact and company records themselves are unaffected).

The one built-in way to preserve some memory of an ended relationship is the seeded Former Employee role — if you want a record that someone used to work at a company, set their role to Former Employee instead of removing the link outright. That’s a manual choice, not something that happens automatically when someone’s employment ends.

There is no hard limit on how many companies a single contact can be linked to, or how many contacts a single company can have. In practice, both the contact’s company list and the company’s contact list load as a complete list rather than a paginated one, so an unusually large number of relationships could make that specific grid slower to work with — but there’s no built-in cap that would block you from adding another link.

The questions below are phrased the way a customer or a colleague might ask them, with a direct answer for each.

“Can the same person be linked to more than one of our companies?”

Yes. A contact can be linked to as many companies as needed, and each link is independent with its own role and primary/VIP status.

“Why did my ticket end up under the wrong company?”

This depends on how the ticket was created. If a technician created it and the contact has multiple companies, they should have been prompted to pick one and you may need to double-check which one was chosen. If it came in by email, it will resolve by domain match first, then by the contact’s primary company. If it came from the portal, it resolves to the contact’s primary company by default. If the “wrong” company keeps happening, check which company is marked primary for that contact.

“Can I see all my companies in one view in the Customer Portal?”

Not currently. A portal login is tied to exactly one company at a time — there’s no switcher between multiple companies in the portal. Someone who genuinely needs visibility into two companies’ portal data today would need a separate portal invitation for each one.

“What does the VIP flag actually change?”

Today, it’s a visible badge on the company’s contact list and nothing more — it doesn’t currently affect ticket priority, alerting, or reporting.

“Someone left a company we work with — how do we update that?”

A technician can either remove the link entirely, or, if it’s useful to keep a record that the person used to be associated with that company, change their role to Former Employee instead of deleting the relationship.

“Is there a limit to how many companies someone can be linked to?”

No hard limit exists today.

“We merged two duplicate contacts — will we lose any company relationships?”

No relationships are lost, but it’s worth a manual check afterward: any VIP status is reset to off upon a merge, and if both contacts shared a company, the surviving contact’s existing settings for that company are what’s kept, without a prompt to compare the two.

Adding a consultant who works across two of your clients

• Open the contact (or create them if new) and go to Relationships.
• Add the first company with an appropriate role, and mark it primary if it’s their main affiliation.
• Add the second company the same way, leaving it non-primary unless it should replace the first as primary.

Double-checking why a contact’s ticket keeps landing on an unexpected company

• Open the contact’s Relationships tab and check which company is currently marked primary.
• If the ticket came in by email, check whether the sending domain matches a different company than the one you expected.
• Correct the primary flag if that’s the actual source of the mismatch, rather than assuming it’s a bug.

Marking someone VIP for a specific company

• Open that company’s record and find the contact in its linked contacts list.
• Edit the relationship and toggle VIP for this company.
• Remember this is a display flag only — it won’t change ticket handling on its own.