Enter the access password to continue to this synthetic Customer Success measurement and account-workspace demonstration.
Accounts sorted by disclosed threshold exceptions and renewal timing.
Direct averages of the six health inputs.
Scheduled synthetic meeting dates from account records.
Exact rules used to flag values.
At risk <70 · Watch 70-81 · Healthy ≥82.
Coverage, adoption, value, stakeholder, support, or commercial readiness is flagged below 70%.
Renewal is flagged when 90 days or fewer remain.
Published inside the demo so the score is reproducible.
25% adoption + 25% outcome evidence + 20% stakeholder strength + 15% technical coverage + 10% support confidence + 5% commercial readiness.
All customer, commercial, and usage values shown here are synthetic for the demo.
Click an account to view metrics, dates, stakeholders, meetings, notes, technical state, support, and success-plan records.
| Account | Industry | Segment | ARR | Health | Lifecycle | Coverage | Adoption | Value | Renewal | Threshold flags |
|---|
Stored objectives, owners, proof definitions, and percent-complete values.
Reference model for coordinating Customer Success, Technical Success, i³, Support, Product, Engineering, and Sales.
Account strategy, value realization, executive alignment, adoption, EBRs, renewal risk, customer advocacy.
Technical lifecycle, architecture, stability, integrations, tuning, upgrades, optimization.
Investigation/intelligence services and insider-risk expertise where contracted.
Issue resolution, root cause, defects, complex escalation, product feedback.
Commercial strategy, pricing, and closure after customer need is established.
Structured portfolio view across the six Customer Success health dimensions.
Stored baseline and measured current duration.
Coverage percentage across agreed population.
Completion percentage across documented milestones.
Measured reduction in analyst effort, noise, or duplicate workflows.
Brings account metrics, stakeholders, success plans, notes, and meeting history into one preparation view.
Stored meeting dates and factual notes.
Days remaining, ARR, health, value evidence, stakeholder score, and commercial readiness.
Stored severity and support-confidence values.
Current request status and service context.
Static reference; DTEX Support determines actual severity.
| Severity | Public description | Target response | Target resolution |
|---|---|---|---|
| Sev 1 | Software substantially inoperable | Within 2 business hours | Within 5 business days |
| Sev 2 | Substantial feature/performance issue | Within 4 business hours | Within 10 business days |
| Sev 3 | Malfunction without substantial impact | Within 1 business day | Within 20 business days |
| Sev 4 | Cosmetic/documentation issue | Within 5 business days | Within 30 business days |