Use case

Customer support

The ticket is written on the screen where the answer should have been

Somebody gets stuck on step four, cannot find the answer, and opens a ticket describing step four. A person then reads it, opens the same screen, and types back the sentence the product could have shown at the moment they stopped. You pay for the round trip every time.

The numbers

What ARCY sees

ARCY watches the product, not the inbox, so a question that never became a ticket still counts. That is the half of demand a help desk cannot report on.

What ARCY does

ARCY answers inside the product, at the moment and on the screen the question was asked, through the chat surface and the flows your own team authored. It is not another inbox to staff.

What it measures

Some of your users never open ARCY at all. Same product, same customers, same window, no ARCY. The difference between them and the users ARCY helped is the contact volume ARCY absorbed, and it is measured rather than estimated from deflection rates.

+36.3% activation lift on this flow

With ARCY

42.8%

1,204 users who ran this flow

Without ARCY

31.4%

2,910 users who never used ARCY

ARCY compares the users it helped against the users who reached the same step and never used it. Both are counted as finished the same way.

Dashboard > ARCY Lift. Figures are illustrative.

Related

See which screen is writing your tickets

Book a walkthrough and we will look at where your contacts are actually coming from, using your own numbers.