{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:concierges-complaint-resolution-escalation:t-bu:v1","lens":"AIService","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":1,"C7_magicLensFit":1,"C4_competitorHonesty":1,"C6_crossSlotCoherence":1,"C1_customerSpecificity":1,"C2_problemFrictionRealism":1,"C9_killCriteriaAttestability":1,"C3_approachEngineCoverability":1,"C5_differentiationLoservilleEscape":1},"upperRightLoserville":true},"cellRef":{"id":"work-contexts.org.ai/concierges-complaint-resolution-escalation","stableHash":"wcc:concierges:complaint-resolution-escalation:voice:v1"},"problem":{"slotStatement":"When a PUC informal complaint lands, the Tier-2 concierge has to piece together the guest's call recordings, IVR transcripts, field-tech truck-roll notes, billing adjustments in CC&B, and the outage-management timestamps from four different systems — and when the 10-day PUC response goes out, roughly a third of the case files are missing the one IVR leg or field note that proves the utility actually did what it said, which the state consumer advocate flags as an adverse finding at the next rate case."},"approach":{"oneSentence":"A complaint-case-file service that, the moment a PUC-tagged or executive-escalation complaint is opened, pulls the CC&B billing trail, Genesys/NICE call legs, OMS outage windows, and field-tech Click/ServiceMax notes into a single chronological case record with each claim linked back to its source system log line, producing a review-ready packet the regulatory analyst can hand to the PUC without a 3-hour manual reconstruction."},"customer":{"icpShape":"Investor-owned or municipal public utilities (CompanyType/company-type-public-utility) with 200k–2M residential meters and an active state PUC docket, where the buyer is the VP of Customer Operations (or Director of Regulatory Compliance for co-signed purchases) and the daily user is the Tier-2 escalations concierge / complaint resolution analyst who handles PUC-tagged and executive-office complaints.","beachheadShape":"EarlyAdopterJTBD: regulated electric and gas utilities under a PUC consent decree or active rate case who must produce a per-complaint case file on 10-day PUC response windows and currently miss 15–30% of informal-complaint deadlines."},"archetype":"startup-archetypes.org.ai/AIService-Subscription","beachhead":"EarlyAdopterJTBD: regulated electric and gas utilities under a PUC consent decree or active rate case who must produce a per-complaint case file on 10-day PUC response windows and currently miss 15–30% of informal-complaint deadlines.","competitors":{"substitutes":[{"name":"Manual Outlook + SharePoint + CC&B tab-hopping reconstruction","category":"manual-bridge"},{"name":"Salesforce Service Cloud for Utilities (Energy & Utilities Cloud complaint console)","category":"incumbent","uncopyabilityReason":"Salesforce's E&U Cloud is an integration-depth problem for them: the complaint console is a case-object UI sitting on top of customer-supplied connectors, and the PUC-grade evidence assembly requires deep, utility-specific joins into Oracle CC&B meter-read history, OMS event logs, and Click/ServiceMax dispatch audit trails that Salesforce cannot own without rebuilding adapter IP they've explicitly left to SI partners — a 2-3 year reseller-contract re-negotiation, not a 6-month roadmap item."},{"name":"Oracle Utilities Customer Care & Billing (CC&B) with Customer Self Service add-on","category":"incumbent","uncopyabilityReason":"Oracle CC&B's deployment-mode mismatch is structural: it ships as a heavyweight on-prem/OCI billing system of record on a 12–18 month utility upgrade cadence gated by PUC change-control, so embedding a live complaint-evidence assembler that crosses into Genesys call recordings and non-Oracle OMS instances would require Oracle to exit its own billing-core scope and take liability for third-party call-center data — something its utility MSAs contractually disclaim."},{"name":"Verint / NICE CXone Quality Management for contact centers","category":"AI-native horizontal","uncopyabilityReason":"Verint/NICE are bounded by vertical-data-corpus: their speech analytics and QM are trained on contact-center interactions only and have no native model of a utility tariff, a PUC informal-complaint schema, or a CC&B billing adjustment — wiring those in means building a utility regulatory data model and a state-by-state PUC docket library they do not possess and cannot acquire from their telco/BPO customer base in under 18 months."},{"name":"J.D. Power / Escalation Management spreadsheets + homegrown Access DBs used by regulatory affairs teams","category":"informal"}]},"studioThesis":"T-BU","killThreshold":{"K":10,"M":70,"N":8,"rubricItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C7_magicLensFit","C8_lensFit","C9_killCriteriaAttestability"],"verdictPolicy":"all-load-bearing-pass-and-overall-ge-X","loadBearingItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C9_killCriteriaAttestability"],"verdictPolicyVerbatim":"KILL unless every load-bearing rubric item passes per workbook AND overall pass-rate ≥ 8/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Source-system reach for a single complaint (contact-center transcripts only ↔ full utility stack: CC&B billing + OMS outage + MWM field dispatch + IVR/ACD legs)","yAxis":"Time-to-packet for a PUC 10-day response (analyst hand-assembles over 3–5 hours ↔ draft case file ready within the first hour of ticket open)","winningQuadrant":"Full utility-stack reach with a sub-hour draft PUC case file the regulatory analyst only has to review-and-sign","loservilleEscape":true,"loservilleQuadrant":"Contact-center-transcript-only QM tools (Verint/NICE) that deliver a call summary hours later but leave the billing, outage, and field-dispatch reconstruction as manual analyst work — the documented failure mode where 25–30% of 10-day PUC responses go out missing the field-tech or OMS evidence leg"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/concierges-complaint-resolution-escalation","thesis":"https://api.sb/v1/theses/T-BU"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575a4e3d370555","edgeLocation":"a0575a4e3d370555","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1/references"},"items":[]}}