UPS Replacement Likelihood

Bundle this UPS's alerts and score how likely it needs replacing.

1. KEY. Extract the UPS device ID from the title. No ID: use the client plus the UPS model or description as the key.

2. HISTORY. Search open and closed tickets for the same client in the last 30 days that carry the key. Include this ticket.

3. BUNDLE. Two or more: pick the oldest (or most descriptive) as parent and merge the others into it. Do not close anything else. Add an internal note listing every ticket: "#<number> | <title> -> <status> | <created>".

4. SCORE 1 to 10 from all signals across the history:
9 to 10, replace now: a replace-battery alert; repeated low-battery alerts over days or weeks; repeated offline plus low battery; a request to replace already on file.
6 to 8, likely soon: two or more low-battery alerts; low battery plus a power event; offline with no outage context; a hardware error code.
3 to 5, monitor: one low-battery event; a power event only; offline once and recovered.
1 to 2, power event, unit fine: only outage alerts, no battery signals, no recurrence.
When signals conflict, take the higher band and say why.

5. NOTE on the parent: "UPS replacement likelihood: <score>/10. <One sentence naming the signals that drove it>."

6. TITLE. Prefix the parent title with "RL<score> - ". If it already starts with an "RL<n> - " prefix, replace it; never stack prefixes.

Only one ticket: skip bundling, still score and prefix. Never close tickets, order hardware or contact the client. Never invent alerts or dates. Notes are plain text, no markdown or emojis.

As a Flow: your entire reply is the score note.