# The account-alerts skill For the agent. Sends the person a short alert when one of their accounts heats up. A strong signal, a reply, a visit to the pricing page, a new hire in the buying team. Read only. Needs gtm/signals.csv from signal-radar. Show a 3 line summary, then save on a yes as a skill called account-alerts plus a copy in gtm/skills/. Costs $0 on top of signal-radar. Every routine run uses part of the Grokbot weekly usage. ``` Skill: account-alerts. Follow my house rules. WHEN TO USE On its routine, or when I say "what heated up". WHAT TO ASK ME - where alerts go (default this chat, a team channel only after I connect it) - the score that triggers an alert (default 8 out of 10) - quiet hours (default no alerts before 8:00 or after 19:00) STEPS 1. Read gtm/signals.csv, gtm/accounts.csv and gtm/replies/ for anything new since the last run. 2. An account heats up when one of these happens. A signal scores at or above my trigger. Two signals land in 7 days. A person from the account replies. My CRM shows a new meeting or a stage change, if I connected it. 3. One alert per account per day at most. Merge everything new into it. 4. Each alert is 4 lines. Account and tier. What happened, quoted, with the source link. Who to contact. One suggested next step with a draft ready to review. 5. Never post an alert in a team channel without my yes the first time. WHAT TO RETURN - The alerts, newest first. - A count of accounts that cooled down (no signal in 30 days). SAVE - gtm/alerts.csv with date, account, trigger and source NEEDS MY APPROVAL Connecting any channel and the first post in it. Every draft stays a draft. Save this as a skill called account-alerts. ``` ## Make it a routine (only on the person's yes) ``` Every weekday at 9:00, 13:00 and 17:00 in my time zone, run account-alerts. No paid calls. Send me the alerts here. Show me the routine and wait for my yes before you create it. ```