Use cases

Find the tickets marked solved that are not

Reads the thread when a ticket is set to Solved and says whether it was fixed, what the customer last said and what is open. An agent can always override.

Try it on this example

Example · Marked solved after fixing the wrong thing

Channel (email, chat, messaging, web form): chat

The whole ticket thread with speaker labels

[Tue 10:02] Customer (Josie Porter): Hi, I moved house two weeks ago and changed my address in my account settings last week. My new order (#48213-A, the desk lamp and two shelves) is due on Friday and I just noticed the confirmation email still has my old address on it. [Tue 10:02] Bot: Thanks for your message! An agent will be with you shortly. Average wait time: 4 minutes. [Tue 10:07] Agent (Carla): Hi Josie, thanks for getting in touch! Sorry for the confusion. Can I confirm the new address, please? [Tue 10:08] Customer (Josie Porter): 27 Hazel Street, flat 3. The old one was 9 Wharf Lane. [Tue 10:11] Agent (Carla): Thank you. I've checked your profile and updated the default delivery address to 27 Hazel Street, flat 3. You're all set for future orders! [Tue 10:12] Customer (Josie Porter): Thanks, but it's this order I'm worried about. The order page still shows 9 Wharf Lane as the delivery address. I don't live there any more, so if it goes there I won't get it. Will Friday's delivery go to the new address? [Tue 10:14] Agent (Carla): I completely understand. Your profile now shows the correct address, so everything should be fine going forward. [Tue 10:15] Customer (Josie Porter): That hasn't fixed it. I've just refreshed the order page and it still says 9 Wharf Lane. Can you change the address on order 48213-A itself, or stop it so I can reorder? [Tue 10:17] Agent (Carla): Thanks for your patience, Josie! Is there anything else I can help you with today? [Tue 10:17] Customer (Josie Porter): Yes, the order. Please. [Tue 10:18] Agent (Carla): Glad I could help, have a lovely day! [Tue 10:18] System: Agent Carla set the ticket to Solved.
  1. By the end of the thread, is the customer's problem resolved?Customer says it is not fixed93%
  2. What does the customer's last message in the thread do?Still reports the problem89%
  3. Did the customer ask something in the thread that no agent or bot reply answered?Yes98%
  4. Did an agent or the bot promise an action that the thread does not show as done?No80%
  5. Does the customer say they have contacted the firm before about this same matter?No93%
  6. Does the customer say they will or may cancel their account or service, leave, or switch to another provider?No93%
  7. How satisfied does the customer sound in their last messages?Dissatisfied98%
  8. Is the thread complete enough to judge whether the problem was resolved?Yes95%

These are real answers stored from one run on this example.

The prism behind it

Find the tickets marked solved that are not8 questions

Fields

  • Channel (email, chat, messaging, web form)
  • The whole ticket thread with speaker labels

Context

The text is a whole support ticket thread at the moment an agent or a bot sets it to Solved. It holds the customer's messages and the replies from agents or the bot, in order. The answers decide whether the ticket closes as it is, stays open, or the customer gets a short "did this fix it?" message. They do not score the customer's satisfaction and they are not a survey result. What resolved means here: - A ticket is resolved when the customer says the problem is fixed or the question answered, or thanks the agent for a fix. A reluctant "ok fine" counts. - An agent saying it is done is not the same as the customer confirming it. When the customer has not replied after the fix, the ticket is claimed resolved but not confirmed. - A thank-you for trying, or for a quick reply, is not a confirmation that the problem is fixed. - A promise to do something later ("I will ask the warehouse", "you will get a refund in 5 days") is an open commitment until the thread shows it done. - Judge only from the thread. Order status, refunds and other system data are checked by code, not here.

Questions

  1. By the end of the thread, is the customer's problem resolved? Choice

    Apply the meaning of resolved in the context. Judge from the whole thread, and give most weight to the last messages.

    • Customer confirms it is fixed The customer says the problem is fixed or the question answered, or thanks the agent for a fix.
    • Agent says done, customer has not confirmed An agent or the bot says it is fixed or answered, and the customer has not replied or has not said whether it worked.
    • Customer says it is not fixed The customer says, after the last fix or answer, that the problem is still there or the question still unanswered.
    • Still in progress The thread shows a step still to come from either side, such as a check by another team or a document the customer will send.
    • No problem or request The thread holds no customer problem or request: spam, an auto-reply, or a message that only says thanks.
  2. What does the customer's last message in the thread do? Choice

    Judge the customer's last message by what it says. Choose No reply to the last answer only when an agent or the bot gave an answer or a fix after that message; a sign-off or a question back with no answer does not count.

    • Thanks or confirms The last customer message thanks the agent, confirms a fix, or closes the conversation politely.
    • Still reports the problem The last customer message says the problem is still there, or repeats the original question.
    • Asks a new question The last customer message asks about something new that was not part of the original problem.
    • No reply to the last answer An agent or the bot answered or offered a fix after the customer last wrote, and the customer has not replied to it.
  3. Did the customer ask something in the thread that no agent or bot reply answered? Yes / No

    Count any direct question from the customer that no later reply answers, including a question that got a reply about something else. Yes: At least one customer question is left unanswered. No: Every question the customer asked got an answer, or the customer asked none.

  4. Did an agent or the bot promise an action that the thread does not show as done? Yes / No

    Count a specific promise to do something later: call back, send something, check with another team, refund, replace. A statement that something has already been done is not a promise. Yes: At least one such promise is made and the thread does not show it done. No: No such promise is made, or every promise made is shown done in the thread.

  5. Does the customer say they have contacted the firm before about this same matter? Yes / No

    Count an earlier call, chat, email, ticket, visit or reference number about the same matter, however the customer puts it ("this is the third time I have called"). Do not count earlier messages in this same conversation, or earlier contacts about other matters. Yes: The customer says they contacted the firm about this matter before. No: The customer mentions no earlier contact about this matter.

  6. Does the customer say they will or may cancel their account or service, leave, or switch to another provider? Yes / No

    Count a stated intention and a conditional one ("if this is not fixed I am cancelling"). Do not count a plain question about how cancelling works, or an intention the customer takes back later in the thread. Cancelling or stopping a single order is not leaving. Yes: The customer says they will or may cancel their account or service, leave or switch. No: The customer says nothing of the kind, or takes it back.

  7. How satisfied does the customer sound in their last messages? Scale

    Judge the customer's own words in their last one or two messages, not the agent's performance and not how serious the problem is. Do not judge from spelling, grammar or language.

    • Dissatisfied The customer complains, sounds frustrated or angry, or says the help did not work.
    • Neutral The customer shows no clear feeling either way, or has not written since the fix.
    • Satisfied The customer thanks the agent warmly or sounds clearly relieved.
  8. Is the thread complete enough to judge whether the problem was resolved? Yes / No

    Answer No when messages are missing, cut off, only attachments with no text, or so short that a careful reader could not tell what the customer needed. Yes: A careful reader could tell what the customer needed and where it stands. No: The thread is too incomplete to judge.

Lens columns

resolution, resolution_probability, customer_last_word, customer_last_word_probability, open_question, open_question_probability, pending_commitment, pending_commitment_probability, repeat_contact, repeat_contact_probability, churn_intent, churn_intent_probability, customer_mood_at_end, customer_mood_at_end_average, enough_information, enough_information_probability

Run it on your own text

Add this prism in the app, change any question, and test it on a file of your own.

Ask for an invite