ELSA is your TVU support copilot in Slack. Not everything it does carries the same certainty — this page sorts every capability into three trust zones, so you always know when to act directly and when to double-check. ELSA 是 Slack 里的 TVU support 助手。它的能力并不是同一种"确定程度"——这页把所有能力分成三个信任区，让你随时知道哪些可以直接用，哪些要留个心眼。
Every synthesized answer starts with a 🟡 line; answers read straight from a system of record never do. If you see 🟡, it means: "this is ELSA's synthesized judgment, not a confirmed record — open the linked source and sanity-check before acting on a customer." No 🟡 = a direct lookup you can rely on. ELSA labels itself, so you never have to guess. 所有"综合判断"出来的回答，开头都带一行 🟡；照库直读的回答从不带。看到 🟡 就是 ELSA 在说："这是我的综合判断，不是确凿记录——点开出处链接核对一下，再对客户动手。"没有 🟡 = 直查结果，可以放心用。ELSA 会自我标注，你不需要猜。
You'll also meet two smaller marks: an ℹ️ line means the text is quoted verbatim from the linked source, and 📋 heads a digest of records. Neither is a warning — they tell you exactly where the words came from. 另有两个小标记：ℹ️ 表示内容逐字取自所附来源；📋 是记录摘要的抬头。它们不是警告——只是告诉你这些字从哪来。
These are triggered by exact patterns (a PID, a ticket number, a model name) and answered by querying the system directly — no interpretation in between. Act on these directly. 这些能力由精确格式触发（PID、工单号、产品型号），直接调系统查询返回，中间没有"理解"环节。可以直接采信。
Full 16-char PID → model, online status, firmware, ports, full warranty (verdict line first), feature count. Hardware warranty and Support Plan (SLA) are reported as separate verdicts — and the plan line states whether the plan covers hardware repair (Silver/Gold: parts & labor included; Bronze and SUPPORT-T custom contracts: software support only, repairs billable). A RED rental-pool unit reads covered by default — it is TVU's own asset, so coverage follows from ownership, not from a date. It gets NO warranty expiry: its Odoo lines are booking charges that post to the same Hardware Revenue account as a sale, so a ship-date estimate there would be an expiry nobody ever sold. The card names the pool and the unit's rental state instead. Add "features" (or a feature name like IS+) to your question for the full entitlement list. Mis-pasted PIDs self-correct: O/I/l typos and an extra pasted character are both detected and the real device is queried. Ask "how many channels" with a PID for the Rx/Tx channel count (from the HubSpot asset record) — or ask it by name right after a device card ("is this a dual server?"): ELSA carries that device forward and answers yes/no, since the asset holds one PID per receive channel (2 = dual, 4 = quad). Ask "modem type" (or SIM / IMEI / ICCID / carrier) with a PID for that unit's per-slot cellular modem models (5G marked), carriers and SIM identifiers — the HubSpot asset's Radio Information fields, a registration snapshot the backend syncs once daily from the device's own reports (not live: an empty slot doesn't prove a missing modem, and gaps refill once the device reports again); a bare "modem type" right after a device card also carries the device forward. The pairing roster works both ways: a receiver's card leads with "Bound transmitters: N" and a transmitter's with "Bound receivers: N"; add "bound transmitters" / "bound receivers" (or just ask "which packs?" as a follow-up) for the roster with each transmitter's name, platform, firmware and online state, read from TPC's own record. Entitlement/pairing rules are configured in CC/TPC — ELSA reports the roster, it does not rule on authorization.完整 16 位 PID → 型号、在线状态、版本、端口、完整保修（结论行置顶）、功能授权数。硬件保修与支持计划（SLA）分行分别下结论——且计划行会标注是否覆盖硬件维修（Silver/Gold 含 parts+labor；Bronze 与 SUPPORT-T 定制合同为纯软件支持，维修收费）。RED 租赁池设备结论为默认在保——是 TVU 自有资产，在保与否看归属不看日期；同时不给保修到期日：它们在 Odoo 里的记账行是租赁计费、却和真实销售记在同一个 Hardware Revenue 科目下，按出货日估算等于编一个没人卖过的保修期。卡片改为标注所属租赁池与当前租赁状态。追问带 "features/功能"（或具体 feature 名如 IS+）看完整功能清单。PID + "几路/路数/通道数" 可查接收/发送通道数（来自 HubSpot 资产记录）；看完设备卡后直接追问「是不是双路 / 是不是双R」也认——会承接刚才那台设备并直接回答是/不是（资产上一个接收通道一个 PID，2 个=双路，4 个=四路）。PID + "模组型号"（或 SIM卡 / IMEI / ICCID / 运营商）可查这台设备各槽位的蜂窝模组型号（标注是否 5G）、运营商与 SIM 标识——来自 HubSpot 资产的 Radio Information 字段，是后台每日同步一次的登记快照（非实时：空槽位不代表没有该模组，设备重新上线上报后缺失会回补）；看完设备卡后直接追问「模组型号」也会承接刚才那台设备。配对清单双向可查：接收机的卡上先给一行「名下发射端：N 个」，发射端的卡上给「名下接收机：N 个」；追问「绑定了哪些背包 / 哪些接收机 / 关联的发射端」给出清单，含每个发射端的名称、平台、版本与在线状态，逐条取自 TPC 记录。授权/配对关系由 CC/TPC 界面配置——ELSA 只如实报清单，不替你判定授权。PID 贴错能自纠：字母 O/I/l 误打和多贴一位都会被识别并按真实设备查询。
Per-feature license validity from TPC: start date and expiry date for every feature on the device — permanent grants marked, expired or soon-to-expire features flagged. Works as a follow-up too ("features end?" right after a PID lookup).TPC 实查每个 feature 授权的生效与到期日期——永久授权注明，已过期/将到期的标出。跟进句也行（查完 PID 后直接问"什么时候到期"）。
Live device version compared against the latest release — a deterministic comparison, not an opinion.设备当前版本 vs 最新发布版本的确定性比对，不是估计。
Note: needs the device to respond; an offline device returns its last-known state.注意：需要设备在线响应；离线设备返回最后已知状态。
Status, assignee, latest comments (older comments folded to keep it readable).状态、经办人、最新评论（旧评论自动折叠，只看最新动态）。
The repair record as filed.维修记录原样返回。
Note: RMA data currently covers the China repair center.注意：RMA 数据目前覆盖中国维修中心。
Physical specs quoted verbatim from the hardware manual, with the manual named as the source. Whatever is not on file for that model is said plainly — and the other models' figures come with it as clearly-labelled reference, so if you know which families share a chassis you can still get what you need. ELSA never claims two models are equivalent.逐字引用硬件手册里的物理规格，并注明出自哪本手册。该型号手册里没有的会明说，同时附上其它型号的物理规格作为标注清楚的参考——你若知道哪些型号同壳体，就能自己拿到答案。ELSA 不会替你断言两个型号相同。
Note: manuals document the DEVICE. Bags/cases are separate SKUs and their dimensions are not in the manual set — that gap is tracked in the knowledge-gap sheet instead.注意：手册记录的是整机。背包/箱体属独立 SKU，手册库里没有它们的尺寸——这类缺口走填坑表补录。
"case / ticket" + an 8+ digit ID → the HubSpot support-Case record (type, status, depot, created date). If the ID turns out to be a HubSpot ticket, ELSA says so honestly — its access has no ticket-read scope — and hands you the direct HubSpot link instead."case / ticket / 工单" + 8 位以上数字编号 → HubSpot 支持案例记录（类型、状态、维修点、建档日期）。如果这串号其实是 HubSpot 工单（Ticket）编号，ELSA 会如实说明自己没有工单读取权限，并直接给出 HubSpot 直达链接。
Jira version records across 35 products. Ask "last 3 LinuxR versions" for a recent-releases list, or a specific version for its full change log. A bare build number works too — TM1000V3 82041 release note.35 款产品的 Jira 版本记录。发「LinuxR 最近 3 个版本」看近期版本列表，指定版本号可看完整发布说明。直接给 build 号也行——TM1000V3 82041 release note。
Searches every product's release-note change log for the peripheral and lists the product lines and builds that record it, quoting the change-log line verbatim.拿这个外设去检索全部产品线的发布说明 Change Log，列出记录了它的产品与 build，并逐字引用对应的 Change Log 行。
Read it as: what the release notes RECORD, over the version window Jira keeps. A product line that isn't listed has no such change-log entry — that is not proof it's unsupported. Confirm with that product's PM when the answer is load-bearing.怎么读：这是发布说明里"有记录"的意思，范围是 Jira 保留的版本窗口。没被列出的产品线＝它的 Change Log 里没有这条记录，不等于一定不支持；结论承重时找该产品 PM 确认。
Model → official link, from a maintained lookup table (links are never invented).型号 → 官方链接，走维护好的查表（链接绝不现编）。
Model (+ build) → the Clonezilla / disk-image download link, verbatim from the firmware sheet, with FTP credentials. Name a build to narrow it, or omit it to list every version on file.型号（+ build）→ Clonezilla / 刷机镜像下载链接，逐字取自固件表，含 FTP 凭证。带 build 号精确匹配，不带则列出该型号全部版本。
Platform → two versions, verbatim from the dial-patch release sheet: the latest RELEASED one (Support default) and the latest overall — flagged as engineer-self-tested / QA-unverified when unreleased. Name a version number to see its changelog.平台 → 两个版本，逐字取自拨号补丁发布表：最新发布版（Support 默认用）+ 最新版（未发布则标注"工程师自测通过、QA 未验证"）。带版本号可查对应 ChangeLog。
TVU repair center list (address / contact), filtered by the region you name.TVU 维修中心清单（地址 / 联系人），按你说的地区过滤。
Live Odoo Inventory query over the [RED] rental catalog: in stock / broken / out with customers or on rental / in transit, per location. Plain inventory wording works ("V3 in stock") — no need to say "loaner". Add "list serials" for per-unit serial numbers with device PIDs; name no product for a whole-catalog overview. After a card, bare follow-ups work: "list serials", "what about V4", "which are broken". Loaner policy/process questions still go to the support policies.实时查 Odoo Inventory 的 [RED] 租赁目录：在库 / 坏机 / 客户或租赁在外 / 在途，按位置分组。直接说「V3库存」即可，不必带"备机/loaner"。加「列出序列号」看每台明细（序列号+PID）；不带产品名给全目录总览。看到卡片后可直接追问：「列出序列号」「那 V4 呢」「哪些坏了」。备机政策/流程类问题仍走支持政策。
PDI factory software version for pre-shipment checks.PDI 出厂软件版本，售前验机用。
Read from the product-owner directory, source cited. Accuracy = that directory's accuracy.照产品负责人对照表直读并注明来源，准确性以该表为准。
Product/component → on-call engineers' name / mobile / WeChat, from the roster Engineering maintains. Per policy P0136: urgent backend incidents only — these engineers may be paged outside business hours.产品/组件 → 值班工程师姓名 / 手机 / 微信，照工程团队维护的名单直读。按政策 P0136：仅限紧急后端事故，可在非工作时间呼叫。
Name → the products/modules they own (and on-call contacts if listed), from the engineering directory. Accuracy = that sheet's accuracy.人名 → TA 负责的产品/模块（在 on-call 名单上的还带联系方式），照研发分工表直读，准确性以该表为准。
Both directions: country/region → salesperson, and name → coverage/contact (name / coverage / email / phone), read from the Global Sales Team sheet, source cited. A third direction covers a named CUSTOMER ("who owns Meme House LA?"): ELSA reads the sales owner off the HubSpot company record and names them with their email when it can; when it cannot read the owner directory it says only whether an owner is assigned and links the record — it never guesses a name. Either way it attaches the country's regional rep as reference, explicitly not claimed to be that customer's owner.双向可查：国家/地区 → 销售负责人，人名 → 负责区域与联系方式（姓名 / 负责区域 / 邮箱 / 电话），照 Global Sales Team 表直读并注明来源。第三个方向是按**客户名**查归属（「MEME HOUSE LA 是哪个销售的」）：ELSA 从 HubSpot 公司记录读归属销售，读得到就直接报姓名+邮箱；读不到则只说有没有分配、并给记录直链——绝不猜人名。两种情况都会附上该国家的区域销售供参考，并明确标注这不等于该客户的归属销售。
Tested phones (Android/Apple), external mics, gimbals, Blackmagic capture devices and dual-camera models, read from the Anywhere compatibility sheet, source cited. The sheet lists tested devices — not listed ≠ not supported.已测试的手机（安卓/Apple）、外接麦克风、云台、Blackmagic 采集设备、双摄机型，照 Anywhere 设备适配表直读并注明来源。表收录的是已测试设备——表中没有 ≠ 不支持。
Quoted verbatim from the weekly Support summary (~16 weeks), with dates. Entries are usually email subjects — search your mailbox by them for the full text.逐字引用支持团队每周信息汇总（约 16 周），带日期。条目多为邮件主题，可据此搜邮箱看原文。
Which GM group a user email belongs to in TVU systems.查该邮箱在 TVU 系统中的 GM 权限归属。
A fixed card, not a guess: ELSA was designed, built and is maintained by Bill on the TVU Support team, and the card hands you a direct Slack mention. Feature requests, a wrong answer, a new data source to connect — DM him; it's his call. The in-channel paths (🙁 on any answer, teach ELSA: <answer>) reach him too.固定卡片，不是猜的：ELSA 由 TVU Support 的 Bill 设计、开发并持续维护，卡片直接给出他的 Slack @。想加功能、发现答错了、想接新的数据源——直接私信他，由他拍板。频道内的两条路（任何回答下的 🙁、投喂ELSA：<答案>）同样直达他。
These also end in a real system query — but ELSA first has to understand what you want and extract the right parameters. If it "gets" you, the answer is as solid as the green zone. If it doesn't, it may route to the wrong capability or miss entirely. Trust the data; if the answer feels off-target, rephrase — don't assume the data is wrong. 这些能力最终也是调真实系统查询——但 ELSA 得先理解你要什么、抽对参数。听懂了，答案和直读区一样铁；没听懂，可能路由错方向或干脆没接住。数据本身可信；答案跑偏时换个说法重问，别当成数据错了。
HubSpot asset list for a customer.HubSpot 里该客户的资产清单。
Tip: use the words "devices" or "assets" with the customer name. HubSpot asset data is global.技巧：带上"设备"或"资产"字眼 + 客户名最稳。HubSpot 资产数据覆盖全球。
One line per device — end user first, channel partners tagged — instead of a full device card each. After any batch you can simply ask "whose are these" without re-pasting the PIDs.一行一台——终端用户在前、渠道商标注——而不是每台一张完整设备卡。看完一批设备后直接追问「这些是谁家的」即可，不用重贴 PID。
Note: the source is the HubSpot asset→company association. Odoo's invoiced customer can differ (reseller vs end user) — ask for a single PID to see the full card with both sources.注意：来源是 HubSpot 资产→公司关联。Odoo 开票客户可能与之不同（渠道商 vs 终端用户），需要双源对照请单台查完整设备卡。
Reads HubSpot the way a salesperson would: registered assets, support cases, deals and closed revenue → existing customer / opportunity never won / churned / no engagement, with the evidence printed under the verdict.按销售的读法查 HubSpot：在册设备、支持工单、商机与成交收入 → 给出「是现有客户 / 曾有机会未成交 / 已流失 / 无往来」的结论，依据逐项列在结论下面。
Note: registered assets are the hard evidence — an empty asset list can also mean the gear was bought through a reseller, so a PID or serial number is the final word.注意：在册设备是最硬的判据；资产为空也可能是走经销商下单，最终以 PID / 序列号反查为准。
Finds the HubSpot asset by serial number and returns the record with every channel PID.按序列号找到 HubSpot 资产记录，报出该设备各通道的 PID。
Tip: say "S/N", "SN", "serial" or 序列号 before the number; partial serials work too. Send a returned 16-char PID back for the full device card.技巧：号码前带上 "S/N"、"SN"、"serial" 或「序列号」字眼；部分序列号也能匹配。拿到 16 位 PID 后可回发直查设备完整档案。
The other direction: the serial printed on the label, from the Odoo asset registry (item.asset), cross-checked against the HubSpot asset record. If the two systems record different serials, both are shown and flagged — neither is silently preferred.反过来查：从 Odoo 资产库（item.asset）取机身序列号，并与 HubSpot 资产记录交叉核对。两套系统若登记不一致，两个都报出来并标注，不会替你悄悄选一个。
Tip: right after a device card you can just ask "what's its S/N". If neither registry has the device, you get an honest miss (a device can be live in TPC and still unregistered — TPC carries no serial field at all), not a silent card.技巧：刚看过设备卡时，直接问「它的序列号呢」即可。两个库都查不到会明说（设备在 TPC 在线也可能没登记——TPC 本身不带序列号字段），而不是给你一张答非所问的卡片。
Repair stats with fault-module and resolution breakdown.维修统计，含故障模块与维修方案分析。
Note: RMA statistics currently cover the China repair center only.注意：RMA 统计数据目前只覆盖中国区（中国维修中心）。
Searches the repair ledger's symptom column; optionally add a model, 接收机/receiver, or a time window (今年 / 2025年 / 近半年). Answer includes counts, in/out-of-warranty split and model distribution.按台账"现象"列检索维修记录；可加机型、"接收机"、时间窗（今年 / 2025年 / 近半年）。回答含条数、保内外拆分、机型分布。
Note: supported symptom families: power-on failure, SDI IN/OUT no signal, SIM card, charging, screen, freeze/auto-shutdown, overheating, HDMI, etc. China repair-center ledger only.注意：支持的现象类别：开不了机、SDI IN/OUT 无信号、SIM 卡、充电、屏幕、死机/自动关机、发热、HDMI 等；数据为中国维修中心台账。
Searches Jira for matching known issues and their fix status. Your symptom gets turned into search keywords — a loose description means loose matches.反查 Jira 列出可能相关的已知问题及修复状态。你的现象会被转成搜索关键词——描述含糊，匹配就含糊。
Tip: include the exact error text or behavior; treat results as candidates to open, not verdicts.技巧：带上具体报错原文；结果当"候选工单"点开看，不当结论。
Technical specs pulled from official manuals (28 products, 50 manuals) — the source is authoritative, the extraction step is where to keep an eye.从官方手册提取技术规格（28 款产品、50 本手册）——源是权威的，"提取"这步值得多看一眼。
Tip: for contract-critical specs, open the linked manual page and confirm.技巧：写进合同/承诺客户的规格，点开手册链接确认原文。
Send a monitoring screenshot or error screen with a line of text — ELSA reads the image and matches it against the knowledge base.发监控截图或报错界面 + 一句说明，ELSA 直接读图并匹配知识库。
Tip: always add a sentence of context; a bare image gives the router nothing to grab.技巧：务必配一句文字说明，光发图路由没抓手。
ELSA pulls the logs, identifies a root cause, and files a Jira ticket (~1–3 min). The retrieval is exact; the root-cause call is analysis — check it against the cited log lines.ELSA 自动拉日志、定位根因并建 Jira 工单（约 1–3 分钟）。取日志是精确的；根因结论是分析——对照引用的日志再确认。
Couldn't parse the last reply? Say "put your answer in plain language" / "translate your reply to English" / "summarize what you just said", or simply send ? — ELSA rewrites its own previous reply. The rewrite is grounded in that reply only (no new facts added), which is why it lives in this zone: the phrasing must clearly point at ELSA's own output ("your answer / 你上面的回答") — "explain SRT" with no such reference is treated as a normal knowledge question. Bonus behavior: sending the exact same message 3+ times gets a nudge to rephrase or hit 🔍 Deep analysis, because re-sending usually means the answer keeps missing the point.看不懂上一条回复？直接说「把你上面的回答说通俗点」「把你的回答翻译成英文」「总结一下你刚才说的」，或干脆发个 ？——ELSA 会改写它自己的上一条回复。改写只基于那条回复本身（不加新内容），所以放在这个区：措辞必须明确指向 ELSA 自己的输出（"你上面的回答/你这几个问题"）——不带指代的「解释一下SRT」会按正常知识问题处理。另一个配套行为：同一句话连发 3 次以上会收到主动提醒——换一句话说出你真正想要的结果，或点 🔍 深度分析（复读通常说明还没答到你要的点上）。
Here ELSA matches your question across knowledge bases (500+ checklists, 800+ KS docs, 100+ policies) and reasons over what it finds. These answers carry the 🟡 line and always cite sources. They save you real time — as a starting point, not a verdict. Open the source link before acting on a customer. 这个区 ELSA 要在多个知识库（500+ 排查清单、800+ KS 文档、100+ 政策）里匹配、再综合给出判断。这类回答带 🟡 标注、必附出处。它们确实省时间——但定位是"起点"，不是"结论"。对客户动手前，先点出处核对。
Matches your symptom against checklists + KS docs (Chinese docs come with English translations), plus R&D's own wiki — the engineers' hand-written pages on what QA actually tested: supported accessory models, what a battery field means, platform differences.拿你的现象去匹配排查清单 + KS 文档（中文文档配英文翻译），另外还有研发自己的内网 wiki——工程师手写的 QA 实测结论：支持哪些配件型号、电池字段怎么读、平台之间差在哪。
Tip: specificity is everything — include the model, whether there's input, and the exact error message.技巧：具体度决定命中率——带上型号、有无输入信号、具体报错。
Searches 100+ Support policies. The text it quotes is verbatim with a policy ID — but which policy matches your case is a judgment call.检索 100+ 条 Support 政策。引用的政策原文是逐字的、带编号——但"哪条政策适用你的情况"是判断。
Tip: before quoting a policy to a customer, open the cited policy and read it in full.技巧：把政策口径给客户之前，点开引用的那条政策通读一遍。
Structured records from the RD patch-release emails to QA: patch name, updateTVU -p apply command, QA status (✅ verified / ❌ rejected / ⏳ pending) and target models. Iterations across baselines are merged and the QA-passed version recommended.取自研发发给 QA 的补丁发布邮件，结构化：补丁名、updateTVU -p 应用命令、QA 状态（✅已验证/❌打回/⏳待测）、适用型号。跨基线的迭代版会归并，优先推荐 QA 通过的那版。
Tip: a ⏳ pending or ❌ rejected patch is not cleared for a customer — check the QA status before applying.技巧：⏳待测 / ❌打回 的补丁没有放行给客户——应用前先看 QA 状态。
Questions unrelated to TVU products: ELSA says so plainly instead of guessing, and points you back to what it's rock-solid at. An honest "I don't know" here is by design.与 TVU 产品无关的问题：ELSA 会坦白说超出范围、不瞎编，并把你指回它铁准的能力。这里的"我不知道"是有意设计，不是故障。
What to type → what you get → how much to trust it. 输入什么 → 得到什么 → 信到什么程度。
| You type你输入 | You get你得到 | Trust信任级 |
|---|---|---|
PID of a RED rental unitRED 租赁池设备的 PID | verdict: covered by default (TVU-owned) + pool & rental state, no invented date结论「默认在保」（TVU 自有资产）+ 所属池与租赁状态，不给编造的日期 | 🟢 |
2E2B1AA285E81D01 | device info, status, warranty, flags设备信息、状态、保修、权限 | 🟢 |
2E2B1AA285E81D01 how many channels?2E2B1AA285E81D01 是几路的? | Rx/Tx channel count (HubSpot asset)接收/发送通道数（HubSpot 资产） | 🟢 |
is this a dual server?是不是双R? | Yes/no on the device just shown — carried forward from the previous card对刚查过的那台直接回答是/不是——承接上一条设备卡 | 🟢 |
2E2B1AA285E81D01 modem type2E2B1AA285E81D01 的模组型号 | Per-slot cellular modem model (5G marked), carrier, IMEI/ICCID (HubSpot asset Radio Information)各槽位蜂窝模组型号（标注5G）、运营商、IMEI/ICCID（HubSpot 资产 Radio Information） | 🟢 |
put your answer in plain language把你上面的回答说通俗点 | ELSA rewrites its own previous reply (simplify/translate/summarize) — grounded in that reply onlyELSA 改写它自己的上一条回复（通俗/翻译/总结）——只基于那条回复，不加新内容 | 🔵 |
AD055947E129DBDE bound transmittersAD055947E129DBDE 绑定了哪些背包 | Transmitter roster on that receiver (name/platform/firmware/online), from TPC该接收机名下的发射端清单（名称/平台/版本/在线），取自 TPC | 🟢 |
<transmitter PID> bound receivers<发射端 PID> 绑定了哪些接收机 | Receiver roster this transmitter is bound to (name/platform/firmware/online), from TPC该发射端名下的接收机清单（名称/平台/版本/在线），取自 TPC | 🟢 |
<PID> features<PID> 功能清单 | full feature entitlement list完整功能授权清单 | 🟢 |
<PID> features expire?<PID> 什么时候到期 | per-feature license start/expiry dates每个 feature 授权的起止日期 | 🟢 |
Is <PID> on the latest version?<PID> 是不是最新版本 | version comparison verdict版本比对结论 | 🟢 |
FB-4451 | Jira ticket status & commentsJira 工单状态与评论 | 🟢 |
RMA12345 | RMA recordRMA 记录 | 🟢 |
check case 46668217632查一下 case 46668217632 的状态 | HubSpot support Case by ID (ticket IDs → direct link)HubSpot 支持案例直查（工单号给直达链接） | 🟢 |
how heavy is TM1100TVU One 尺寸是多少 | dimensions/weight from the manual + labelled reference rows手册物理规格 + 其它型号参考（标注清楚） | 🟢 |
Producer latest release notesProducer 最新版本 | latest release notes最新发布说明 | 🟢 |
last 3 LinuxR versionsLinuxR 最近 3 个版本 | recent releases list近期版本列表 | 🟢 |
TM1000V3 82041 release note | release notes for that build该 build 的发布说明 | 🟢 |
TM1000V3 | a menu of what's answerable for that model (no intent guessing)该型号能直接答的问题清单（不猜意图） | 🟢 |
which backpack versions support OSMO Pocket3哪些背包版本支持 OSMO Pocket3 | product lines + builds whose change log records itChange Log 里记录了它的产品与 build | 🔵 |
TM1100 manual / datasheetTM1100 手册 / 彩页 | official doc links官方文档链接 | 🟢 |
flash image for TM1000v2 6580V2背包 6580 的刷镜像文件 | image download link + FTP刷机镜像下载链接 + FTP | 🟢 |
latest dial patch for TM1000V3TM1000V3 最新拨号补丁 | released + latest dial-patch versions最新发布版 + 最新版拨号补丁 | 🟢 |
TVU repair center in the US美国的维修中心 | repair center address/contact维修中心地址/联系人 | 🟢 |
How many V3 in stockV3库存还有几台 | live rental stock: in stock/broken/out with customers/in transit (Odoo)租赁库存实时：在库/坏机/客户或租赁在外/在途（Odoo） | 🟢 |
who built you?你是谁创建的 | ELSA's owner (Bill) + a direct way to reach himELSA 的 owner（Bill）+ 直接找到他的方式 | 🟢 |
Who is the PM of X?X 的产品经理是谁 | owner directory entry负责人对照表条目 | 🟢 |
X backend incident, who's on call?X 后端事故 on-call 是谁 | on-call engineer contacts (P0136)值班工程师联系方式（P0136） | 🟢 |
Who is Eason / which module?Eason 负责哪个模块 | engineer's products/modules研发分工表反查 | 🟢 |
Sales rep for Serbia? / Who is Johnny Ha?塞尔维亚的销售是谁 / Johnny Ha 负责哪个区域 | regional sales owner, both directions (name/coverage/email/phone)区域销售负责人，双向可查（姓名/负责区域/邮箱/电话） | 🟢 |
who owns Meme House LA?MEME HOUSE LA 是哪个销售的 | whether HubSpot has a sales owner on that customer + record link + the region's rep for reference该客户在 HubSpot 有没有归属销售 + 记录直链 + 该区域销售供参考 | 🟢 |
Which phones work with Anywhere?适配 Anywhere 的手机型号 | tested-device compatibility cards (phones/mics/gimbals)已测试设备适配卡（手机/麦克风/云台等） | 🟢 |
recent patches for 8421?最近 8421 有什么补丁 | weekly-summary quotes, dated周报逐字引用，带日期 | 🟢 |
all devices of <customer>XX客户 的所有设备 | HubSpot asset listHubSpot 资产清单 | 🔵 |
whose are these? + a batch of PIDs这些分别是哪家的？+ 一批 PID | ownership table, one line per device资产归属对照表（一行一台） | 🔵 |
is <company> our customer?XX公司 是我们客户吗 | customer-identity verdict from HubSpot (assets / cases / deals / revenue)HubSpot 客户身份判定（设备/工单/商机/收入） | 🔵 |
S/N <serial> → PID?S/N XX 对应的PID是多少 | HubSpot asset record with per-channel PIDsHubSpot 资产记录 + 各通道 PID | 🔵 |
<PID> serial number?<PID> 的序列号是多少 | Serial from the Odoo asset registry, cross-checked with HubSpotOdoo 资产库序列号，并与 HubSpot 交叉核对 | 🔵 |
<customer> RMA statsXX客户 RMA 统计 | repair statistics维修统计 | 🔵 |
cannot power on RMAs this year今年开不了机的RMA有哪些 | RMA search by symptom按现象筛 RMA | 🔵 |
<symptom> — known bug?<现象> 是不是已知 bug | candidate Jira issues候选 Jira 工单 | 🔵 |
TM1100 video formatsTM1100 视频制式 | specs from manuals手册规格提取 | 🔵 |
| [screenshot] + context[截图] + 一句说明 | image-based diagnosis读图诊断 | 🔵 |
video freezing during live | matched checklists + KS docs匹配的排查清单 + KS 文档 | 🟠 |
is there a patch for Pocket4 lip-sync?Pocket4 音画不同步有没有补丁 | RD patch: name + updateTVU cmd + QA status研发补丁：补丁名 + updateTVU 命令 + QA 状态 | 🟠 |
warranty policy on demo units?保外设备可以免费维修吗 | policy excerpts + IDs政策原文摘录 + 编号 | 🟠 |
"TM1100 no video output on SDI 1, input LED is green" will outperform "device has a video problem" every single time. Model + exact error text + what you've observed = best match."TM1100 SDI 1 无视频输出，输入灯是绿的"永远比"设备视频有问题"命中率高。型号 + 报错原文 + 你观察到的现象 = 最佳匹配。
After a PID lookup you can just ask "when does its warranty expire?" — ELSA carries the device over. No need to re-paste the PID.查完 PID 后直接追问"那它保修到什么时候"即可——ELSA 会继承上一轮的设备号，不用重贴 PID。
Ask in English, get answers in English — including checklists originally written in Chinese (they have English translations).中文问得中文，英文问得英文——中文排查清单也有英文翻译版。
Found an answer ELSA didn't have? Send teach ELSA: <the answer> (or a Google Doc link). It's filed into the knowledge base and reviewed by the ELSA Knowledge Task Force — once approved, the whole team gets it, and that question never goes unanswered again.查到了 ELSA 不会的答案？发 投喂ELSA：你的答案（也可以发 Google Doc 链接）。会进知识补录表、经填坑特战队审核确认后全团队都能查到——你补的一条，从此这个问题不再无解。
When the quick lookup does NOT return a certain answer — a synthesized analysis, nothing found, or out of coverage — the answer carries a 🔍 Deep analysis button. Click it and ELSA spends ~1-3 minutes cross-searching all knowledge sources and returns a 🟡 cited synthesis in the thread. It shines on cases like a mistyped PID the lookup couldn't find. When a direct lookup already returned valid data, the button is not shown — that answer is already authoritative; to force an independent recheck, post @ELSA deep analysis in the thread. Mid-discussion in a channel the same summon works too: ELSA reads the whole thread first. Its sources include the body text of the official user manuals, not just their links — for "how do I / where is this setting" questions the manuals are the only source that documents the UI (which panel, which tab, which option), so it names the real menu location instead of guessing one. It also searches R&D's internal wiki, which is often the only written record of what QA tested — the supported USB Bluetooth adapters, for instance, are written down nowhere else. Deep analysis also carries your recent DM conversation — asking "is this a dual server?" right after a device card resolves to THAT device, and it can pull the live device/warranty record itself while researching.当快速查询没有给出确定答案时（综合分析、没查到、超出覆盖范围），回答下会出现 🔍 深度分析 按钮：点它，ELSA 花约 1-3 分钟交叉翻遍全部知识源，在原消息下回一份🟡带出处的综合分析。PID 抄错查不到这类情况它尤其擅长。直查已给出有效数据时不再显示按钮——那已经是权威答案；想强制独立复核，在 thread 里发 @ELSA 深度分析 即可。频道里讨论到一半也可以同样召唤，它会先读完整个 thread 再带着上下文去查。它的检索源包含官方用户手册的正文（不只是手册链接）——「XX 怎么操作 / 在哪里设置」这类问 UI 步骤的问题，手册是唯一写了菜单位置的源，所以它会给出真实的菜单路径，而不是猜一个。它也会翻研发的内网 wiki——很多「QA 到底测没测过」的结论只写在那里（比如支持哪些 USB 蓝牙适配器，别处一个字都没有）。深度分析现在也带着你最近的对话上下文——看完设备卡接着问「这台是不是双R」，它知道你指哪台，并且研究过程中能自己实时调取设备/保修记录。
👍 = this landed. 🙁 = didn't help (logged and queued to be fixed — you'll get a DM when it's resolved). On uncertain answers, ✒️ Help ELSA improve appears: write the correct answer if you have it, or just flag what's off. The ✒️ sticks around — come back and fill it whenever you learn the answer. None of them block your next question.👍 = 答对了。🙁 = 没帮上（会被记录、安排补齐——修好后 ELSA 私信告诉你）。不确定的回答下还会出现 ✒️「帮 ELSA 补个更准的」：有答案就写答案，没答案说说哪里不对也行。✒️ 会一直留着——以后什么时候问到了答案，回来点它补上就行。三个按钮都不挡你继续提问。
Type help for the full capability list, leaderboard for this week's feedback contributors, usage stats for per-feature confidence based on recent ratings.发 帮助 看完整能力清单，反馈榜单 看本周贡献榜，使用统计 看各功能近期评价与置信度。