Customer case case · Rocketizer Intelligence

BProof grade

7Metrics retained

2Evidence records

DecagonVendor

Reported outcomes

32 percentChat deflection relative increase — headlineNo observation period is disclosed. · DecagonBaseline: 38% before; over 50% after · Formula: Using 50% as the lower-bound after rate, (50 - 38) / 38 × 100 = 31.6%, rounded to 32%; actual result is higher because after is over 50%.

50 percent, more thanChat deflection after deploymentNo observation period is disclosed. · DecagonBaseline: 38% before · Formula: More than 50% - 38% = more than 12 percentage points.

7 percent improvement as statedConversation-routing improvementImmediate after 75+ tag workflow implementation · DecagonBaseline: Prior and current routing accuracy are not disclosed. · Formula: The source does not state whether 7% means relative percent or percentage points.

75 tags, more thanRouting tags configuredConfiguration duration is not disclosed. · DecagonBaseline: Implementation scope is not a before/after metric. · Formula: Tag-count methodology is not disclosed.

12 product lines, more thanProduct lines supportedNo as-of date is stated. · DecagonBaseline: This is deployment scope, not a change metric. · Formula: Product-line definition is not disclosed.

400000 users, more thanUsers in support scopeNo as-of date is stated. · DecagonBaseline: This is customer scale, not a Decagon outcome. · Formula: Active-user definition is not disclosed.

1 day, withinAgent Assist replacement timeUrgent product deprecation event · DecagonBaseline: Elapsed change time is not a before/after metric. · Formula: Exact start and production timestamps are not disclosed.

Context and boundaries

Workflowcustomer_support_and_service–finance_reconciliation_and_payouts–marketing_engagement_and_campaigns–workflow_automation_and_ai_agentsBroad HR/IT/finance support with internal APIs, action workflows, routing and email deflection.

Implementation??

CaveatsThe Dutchie URL currently renders this same Rippling page and is not a separate case.–The 7% routing metric lacks point-versus-relative definition.vendor_owned

Source trail

Dutchie case URL routing anomaly
Despite its Dutchie URL, the live page title, body, speaker and metrics are the Rippling case. It is retained as a URL anomaly and is not counted as a distinct Dutchie case.
company · accessed 2026-07-13
Rippling customer story
Rippling reports chat deflection rising from 38% to more than 50%, a stated 32% increase, 7% better routing, 75+ tags and support across 12+ product lines for 400,000+ users. The duplicate Dutchie URL renders this same story.
company · accessed 2026-07-13

← Back to customer atlas