Use cases

Pick the wrap-up code for every contact from your own list

Picks the wrap-up code from your list when a contact closes and says if it was avoidable, for the agent to confirm. The codes are an example to replace.

Try it on this example

Example · A bill question caused by a notice that never went out, with a second request

Channel (call transcript, chat, email): call transcript

The whole conversation

Agent: Thanks for calling Veloway, this is Nicole. Can I start with the phone number or email on the account? Customer: Hi, yes, it's terry.oduya@example.com. Agent: Thanks. And for security, can you tell me the last four digits of the card you pay with? Customer: 2291. Agent: Perfect, thank you, Terry. What can I help with today? Customer: So my internet bill this month is sixty-one dollars. It's been thirty-eight dollars every month since I signed up last year. Nothing's changed on my side, I haven't added anything. I just want to know why it's gone up by twenty-three dollars. Agent: Of course, let me take a look at the bill. Bear with me one second. Customer: Sure. Agent: Okay. So your plan is Home 300, and when you joined you had a twelve-month welcome discount of twenty-three dollars a month. That discount ended on your August bill, which is why it's gone back to the standard price of sixty-one. Customer: Okay, but nobody told me that. I'd have remembered. Agent: Let me check what we sent. We normally email a reminder thirty days before a discount ends. Looking at your account, I can see that reminder was never sent. It looks like it didn't go out for a batch of accounts in July. I'm sorry about that, you should have had it. Customer: Right. And I did look in the app before I called, and it doesn't say anywhere when the discount ends or what the price goes to. It just shows the monthly amount. Agent: That's fair feedback, I'll pass that on. What I can do today is move you onto our current twelve-month price for Home 300, which is forty-two dollars a month, and credit the twenty-three dollars from this bill as the reminder didn't reach you. Customer: Forty-two. Brightwave down the road are offering the same speed for thirty-five, I got a flyer from them last week. Agent: I understand. Forty-two is the best price I can offer on this plan today, and it includes the router and no setup charge. If you'd like, I can set it up now and it will show from your next bill. Customer: Okay, fine. Go ahead with the forty-two and the credit. Agent: Done. You'll see a credit of twenty-three dollars on this bill, and the new price of forty-two dollars a month from your October bill, for twelve months. I've sent a confirmation to your email. Customer: Thanks. While I've got you, can I add a mobile line for my daughter? She needs a SIM with some data, nothing big. Agent: Sure. Our smallest plan is Mobile 5, five gigabytes for fifteen dollars a month, with the broadband discount. Would you like the SIM sent to the address on the account? Customer: Yes, same address. Agent: Great. I've added the line and the SIM will arrive in two to three business days, with the activation steps in the pack. Is there anything else I can help with? Customer: No, that's it. Thanks, Nicole. Agent: Thanks for calling, Terry. Have a good day.
  1. Which wrap-up code fits the main reason the customer made this contact?Bill question100%
  2. Does the customer raise a second, different reason for contact in the same conversation?Yes97%
  3. Could the firm have avoided this contact?Our error or delay100%
  4. What underlying cause of this contact does the conversation establish?Communication failure99%
  5. Which service is this contact mainly about?Home broadband100%
  6. How does the contact end for the main reason the customer got in touch?Resolved in the contact100%
  7. Does the customer say they have contacted the firm before about this same matter?No91%
  8. Does the customer say the website, app, bill or letters were missing, unclear or wrong about this matter?Yes97%
  9. Does the customer name or clearly describe a competing provider or its offer?Yes98%
  10. Is there enough in the conversation to tell why the customer made contact?Yes99%

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

The prism behind it

Pick the wrap-up code for every contact from your own list10 questions

Fields

  • Channel (call transcript, chat, email)
  • The whole conversation

Context

We are Veloway, a US home broadband and TV provider that also sells mobile plans to its broadband customers. The text is one whole customer contact that has just ended: a call transcript or chat with speaker labels, or an email thread. The answers fill in the wrap-up code the agent would otherwise pick, and feed the weekly contact-reason and avoidable-contact reports. They describe the contact, never the agent. How we code a contact: - One code per contact: the reason the customer got in touch, as they describe it, not whatever came up later in the conversation. A second, different reason is recorded as a second code by the agent. - A contact is coded by its topic, not by the mood of the customer. Complaints are recorded separately. - A contact is avoidable when it only happened because of something we did wrong or late, because the customer is chasing something we already promised, or because the answer is already on our website or in our app. A new, genuine need is not avoidable. - The root cause is what the conversation itself establishes. We do not guess at causes the conversation does not show. Worked examples: - "My internet drops every evening" is Fault or outage, even if the agent then books a visit. - "Why is my bill $20 more this month?" is Bill question, even if the agent offers a new plan. - "Where is the engineer? He was due at nine" is Visit or delivery, and it is avoidable as chasing. - "How do I change my Wi-Fi password?" is How-to question, and it is avoidable when the app or help center already explains it.

Questions

  1. Which wrap-up code fits the main reason the customer made this contact? Choice

    Pick the code for the reason the customer got in touch, using the definitions below and the coding rules in the context. When the customer raises several things, pick the one they contacted us about first, unless they say another matters more.

    • Bill question A question about, or challenge to, the amount or items on a bill: a higher bill, an unknown charge, a discount that ended. No payment failed.
    • Payment problem A payment that failed, was taken twice, was taken on the wrong date, or a change to how the customer pays.
    • Refund or credit request The customer mainly asks for money back or a credit, and does not question how the bill was worked out.
    • Fault or outage Broadband, TV or mobile service is down, slow, dropping or not working as it should.
    • Router, box or device A router, TV box, remote or phone that is lost, damaged or needs replacing or returning, when the service itself is working.
    • Visit or delivery The timing of an engineer visit, an installation, or a delivery of equipment: booking, moving or chasing it.
    • How-to question How to do something the service already supports, such as changing a Wi-Fi password or setting up a channel, with nothing broken.
    • Account access Logging in to the account or app: passwords, locked accounts, security codes, or who is allowed on the account.
    • Change plan or add-on Upgrading, downgrading or adding to a plan, TV package or mobile line the customer already has.
    • Moving home Moving the service to a new address, or ending it because of a move.
    • Cancel service Ending the whole service or account for any reason other than moving home.
    • New service enquiry Someone who is not yet a customer asks about buying a plan, prices or coverage at an address.
  2. Does the customer raise a second, different reason for contact in the same conversation? Yes / No

    Count a second matter only when it would take a different wrap-up code from the list and the customer asks for something about it. A follow-up question about the same matter is not a second reason. Yes: The customer raises a second matter that needs a different code. No: Everything the customer raises belongs to the same code.

  3. Could the firm have avoided this contact? Choice

    Use the definition of avoidable in the context, and judge only from what the conversation says. When more than one option fits, pick the first that applies in this order: Our error or delay, Chasing, Self-service would do.

    • Our error or delay The contact happened because the firm did something wrong or late: a wrong charge, a missed visit, a fault it caused, a notice it failed to send.
    • Chasing The customer is following up something already promised or in progress, such as a callback, a refund or a visit, with no error named.
    • Self-service would do A standard question or task that the conversation shows the website, app or help center already covers, with nothing wrong on the firm's side.
    • Not avoidable A new, genuine need the customer had to contact the firm about, such as a new fault, a move or a plan change.
  4. What underlying cause of this contact does the conversation establish? Choice

    Pick the cause the conversation itself shows, from what the agent finds or the customer explains. If the conversation does not establish a cause, choose the insufficient information option rather than guessing.

    • Network or product fault The network, a router, a TV box or the app did not work as it is supposed to.
    • Customer misunderstanding The customer misread a bill, a plan or how something works, and nothing on our side was wrong or unclear.
    • Process or policy gap A step in our process was missed or does not cover the customer's situation, such as a job closed before it was finished.
    • Communication failure We did not tell the customer something they needed to know, or a letter, message or earlier agent told them something unclear or wrong.
    • Billing or plan set-up The customer's charges, plan or discount were set up wrongly in our systems.
    • Third party A courier, a bank, a contractor or another outside party caused the problem.
    • No underlying problem The contact was a question or a request with no problem behind it.
  5. Which service is this contact mainly about? Choice

    Pick the service the main reason for contact concerns.

    • Home broadband The home internet connection, the router or Wi-Fi.
    • TV The TV service, the TV box, channels, packages or streaming apps.
    • Mobile A mobile line, SIM, phone or mobile data.
    • Not about one service The account as a whole, a bundle bill, or a question that names no service.
  6. How does the contact end for the main reason the customer got in touch? Choice

    Judge the main reason for contact only, from the last exchanges about it. A second matter raised later does not change this answer.

    • Resolved in the contact The question was answered or the problem fixed before the contact ended, with nothing left for anyone to do.
    • Transferred The customer was passed to another team or line to carry on.
    • Follow-up needed by us The firm still has something to do: a visit, a callback, a refund, a check by another team.
    • Waiting on the customer The customer has to do something next, such as send a document, try a fix or call back.
    • Customer left The call dropped or the customer stopped replying before an outcome.
  7. 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.

  8. Does the customer say the website, app, bill or letters were missing, unclear or wrong about this matter? Yes / No

    Count only what the customer says about our own information: they looked and could not find it, it was unclear, or it was wrong. Do not count the agent's view. Yes: The customer says our information on this was missing, unclear or wrong. No: The customer says nothing of the kind.

  9. Does the customer name or clearly describe a competing provider or its offer? Yes / No

    Count a named provider or a clear description of one ("the other company on my street offers..."). Do not count a general wish to pay less. Yes: A competing provider or its offer is named or clearly described. No: No competitor is named or described.

  10. Is there enough in the conversation to tell why the customer made contact? Yes / No

    Answer No when the text is cut off, too short, mostly silence or hold music, or so damaged by transcription errors that a careful reader could not tell why the customer got in touch. Yes: A careful reader could tell why the customer made contact. No: The text is too incomplete or garbled to tell.

Lens columns

reason, reason_probability, second_reason, second_reason_probability, avoidable, avoidable_probability, root_cause, root_cause_probability, product_area, product_area_probability, outcome, outcome_probability, repeat_contact, repeat_contact_probability, self_service_gap, self_service_gap_probability, competitor_named, competitor_named_probability, 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