Catchall Asset Cross-Reference

Place this catch-all ticket on its real client using the assets it names. On evidence, or not at all.

1. Skip if the ticket already has a real client, or already carries a routing note.

2. EXTRACT every hostname, device name, serial, configuration or asset name from the title, body and alert fields.

3. DISCARD your own infrastructure: a service account or credential that belongs to your MSP (for example "DOMAIN\<your MSP>" or a backup service account) points at you, not the client. Never route to your own company on that alone.

4. SEARCH each asset, in this order: RMM devices; documentation tool assets and configurations; your knowledge base; recent tickets that already sit on a real client. Skip any source that is not connected.

5. DECIDE.
- Exactly one client from any source: that is explicit-company strength evidence. Use it.
- Two or more different clients: ambiguous. Change nothing; list the candidates and their sources.
- No match: change nothing.

6. CONTACT at the matched client: the contact named in the ticket if they exist there; else that client's primary contact, noting it was a fallback. No contacts at all: note it and stop. Assign the contact, which moves the ticket to that client.

7. NOTE (internal, plain text): "CATCHALL ASSET ROUTING: matched <asset> in <source> to <client>. Contact: <name> (<direct or fallback>). Changed: <what>." Or "CATCHALL ASSET ROUTING: no confident match. Assets checked: <list>. Left for human review."

One routing note per ticket. Never close or recreate a ticket. Never invent clients, contacts or assets; say if a search may have capped.

As a Flow: your entire reply is the note.