Update to Delpha

{
  "description": "Use when a lead or company needs a GTM/CRM routing call — resolving its commercial parent and determining whether it should be treated as a new logo or routed under an existing account.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 285
    }
  ],
  "name": "delpha-gtm-account-routing",
  "skill_md_contents": "---\nname: delpha-gtm-account-routing\ndescription: Use when a lead or company needs a GTM/CRM routing call — resolving its commercial parent and determining whether it should be treated as a new logo or routed under an existing account.\n---\n\nUse this skill when the user asks whether a company or lead is a new logo, an existing account, a subsidiary that should roll up to another account, or which parent/company should be used for GTM, CRM routing, territories, account ownership, or commercial hierarchy.\n\nThe user's explicit instructions take precedence over this skill.\n\n## Goal\n\nUse Delpha to resolve commercial identity, then turn the result into a concise GTM decision. Distinguish the commercial/GTM parent from a passive holding company, financial parent, legal operator, franchisee, or other entity that Delpha does not recommend for GTM routing.\n\n## Workflow\n\n1. Identify the company name and website from the user's request.\n   - A website is required by `findAndValidateUltimateParent`.\n   - If the website is missing and cannot be determined reliably from context, ask only for the website.\n   - Use country when provided or when needed to disambiguate the entity.\n\n2. Call `findAndValidateUltimateParent` with the company name, website, and country when relevant.\n\n3. Use the returned `job_id` with `getUltimateParentResult`.\n   - Do not create duplicate resolution jobs for the same request.\n   - If `getUltimateParentResult` returns `status_code: 202`, wait before retrying; do not issue repeated rapid calls.\n\n4. For sales, RevOps, GTM, territory, and CRM-routing questions:\n   - Use `result.ultimate_parent` as the recommended commercial/GTM parent.\n   - Use `result.relationship_type` as the relationship type.\n   - Use `result.confidence` as the routing confidence.\n   - If `result.ultimate_financial_parent` differs from `result.ultimate_parent`, treat that difference as meaningful. The financial parent is relevant for ownership/compliance; it does not replace the GTM parent for routing.\n   - Use the ownership chain and `comment` only as supporting evidence. Do not replace Delpha's selected GTM parent with a different entity from the chain.\n\n5. For a \"new logo\" decision:\n   - A company is **not a distinct new logo** only when the user states, or an authorized CRM source confirms, that the resolved commercial/GTM parent already exists as an account/logo in the user's CRM.\n   - If the resolved commercial/GTM parent is confirmed absent from the CRM, treat the lead as a new logo.\n   - If CRM existence is unknown, do not guess. Resolve the commercial parent and state that the new-logo decision requires knowing whether that parent already exists in the CRM.\n\n6. Confidence:\n   - Display the Delpha confidence as a percentage when available, e.g. `0.95` → `95%`.\n   - Treat `-1` as missing, not as low confidence.\n   - If confidence is below `0.85`, make the uncertainty visible instead of presenting the routing decision as definitive.\n\n## Output\n\nFor new-logo or GTM-routing questions, keep the complete answer concise, normally under 100 words.\n\nLead with the business decision. Then provide no more than these fields when available:\n\n- **GTM decision:** New logo / Not a new logo / Cannot determine from CRM context\n- **Commercial parent:** [Delpha `ultimate_parent`]\n- **Relationship type:** [Delpha `relationship_type`]\n- **Confidence:** [percentage]\n\nFinish with one short routing sentence:\n\n**Route:** [queried company] → **[commercial parent]**.\n\nIf a different financial/legal parent or operator is relevant, add one short sentence explaining the distinction. Do not narrate the full ownership chain unless the user asks for it.\n\n## Preferred phrasing\n\nWhen the commercial parent already exists in the CRM:\n\n- **GTM decision: Not a new logo** — route under the existing [commercial parent] account.\n\nWhen the commercial parent does not exist in the CRM:\n\n- **GTM decision: New logo** — create or route as a new [commercial parent] account.\n\nWhen CRM existence is unknown:\n\n- **GTM decision: Cannot determine yet** — Delpha resolves the commercial parent as [commercial parent], but the new-logo decision depends on whether that account already exists in the CRM.\n\n## Example\n\nUser:\n`Starbucks Coffee Chile (starbucks.cl) is a new lead. We have Starbucks Corp in CRM. Is this a new logo?`\n\nDesired response shape:\n\n- **GTM decision: Not a new logo** — route under the existing Starbucks Corporation account.\n- **Commercial parent:** Starbucks Corporation (US)\n- **Relationship type:** Member Firm / Franchise\n- **Confidence:** 95%\n\n**Route:** Starbucks Coffee Chile → **Starbucks Corporation**. Alsea is the financial/legal operator, but not the recommended GTM parent.\n\n## Guardrails\n\n- Do not infer CRM account existence from public web data, brand familiarity, or the ownership chain.\n- Do not use the absolute top legal/financial holding entity for GTM routing when Delpha returns a different `ultimate_parent`.\n- Do not invent confidence, relationship type, CRM state, or ownership facts.\n- For ownership/compliance/KYC questions rather than GTM routing, follow the financial/legal ownership information instead of applying the GTM-parent rule.\n"
}