Summary: When the Thread Magic Agent reassigns a ticket from a catchall company to the correct client company, the ticket's agreement field should automatically be populated with that company's default agreement — mirroring the behaviour ConnectWise applies when a technician manually changes the company in the PSA UI.

Current Behaviour: When the Magic Agent identifies the correct company and reassigns a catchall ticket via the ConnectWise API, only the company field is updated. ConnectWise's default agreement logic is a client-side UI event and does not fire on API-based company changes. As a result, the ticket lands on the correct company with no agreement applied (or retains the catchall's agreement), requiring a technician to manually open the ticket in ConnectWise and re-save it to trigger agreement defaulting.

Expected Behaviour: After the Magic Agent updates the company on a ticket, Thread should query ConnectWise for that company's default agreement and apply it to the ticket in the same operation — so the ticket arrives fully configured, just as it would if a technician had made the change manually.

Business Impact:

Tickets without agreements can fall through billing and SLA tracking gaps

Technicians must manually correct agreements after every Magic Agent reassignment

Undermines confidence in automated triage if downstream data (agreement, SLA) is still wrong after the agent acts

Suggested Implementation After a company reassignment via the API, Thread should make a follow-up API call to retrieve the default agreement for the newly assigned company and patch the ticket's agreement field accordingly.

Workaround (current): Technician must open the ticket in ConnectWise and manually re-select or re-save the company to trigger agreement defaulting.