Description:

When working catch-all tickets (or any ticket where the requester is unknown), we often know the company but not the specific contact. Currently, there's no easy way to set the company on a ticket first and then narrow down the contact from that company.

Requested Behavior:

Allow technicians to update/set the company on a ticket independently of the contact — with the company defaulting to its configured default contact upon selection.

After the company is set, provide the ability to search and assign a contact scoped to that company, so the list is filtered down to only relevant people rather than searching across all contacts MSP-wide.

Use Case / Problem Being Solved:

Catch-all tickets frequently come in without a known sender. In these situations, we typically know which company the ticket belongs to before we can identify who submitted it. A company-first → contact-second workflow would:

Speed up ticket assignment and routing

Reduce errors from picking the wrong contact

Make it easier to clean up catch-all tickets quickly and accurately

Current Workaround:

We have to search all contacts across all companies, which is slow and error-prone when multiple companies have contacts with similar names.

Expected Impact:

High — this directly affects ticket hygiene and triage speed, especially for MSPs handling high volumes of catch-all or unidentified inbound tickets.