I 100% agree that no one uses your product to watch a walk-through, they’re there to do a job. The author primarily talks about new user onboarding.
While they do make the point about introducing new features, they don’t address how to make an interrupt-driven announcement successful with existing users.
Has anyone seen a good way to make ongoing update announcements
You can just have a bell icon that displays a little red (1) so the users know that they have a message/notification that they can, but don't have to, read.
Linear has an in-app changelog in the bottom right that doesn’t get in the way of work. It’s synced with their changelog on the website and can be revisited anytime clicking the help menu icon. Pretty elegant.
This is because the tools that CX teams have been provided by companies like Zendesk or Intercom are no more then IFTTT widgets. These tools are rigid and scream RTFM because they’re incapable of taking action or providing anything specialized to your situation.
What you want is to be understood and treated like you’re a human with unique needs. You need someone or something to look up your account data, listen, and to act based on your situation. The current tools were never built for this.
The next generation of these CX tools will deliver this. Here are ways that they will be dramatically better for customers and companies:
- They will learn from successful interactions in the past and mirror those outcomes
- Handle customer interactions based on company policies such as escalating bugs
- They will surface new insights for the company
- Won’t hallucinate
When you watch any CX agent do their job you’ll witness them utilizing 4-5 SaaS applications to get a simple answer for a customer. The hurdle to adopt Generative AI in a company will require that companies care to build read/write APIs for these tools to utilize.
It would be awesome to hear/see more about the system you built to auto-generate and submit evidence. This is a huge pain for many companies which an open source tool could solve.
Sure! I basically use PDF Lib to generate a letter with all my evidence bundled into one pdf file. It sucks up data from my database about the user's activity. Format is the following:
Formal 1 page letter with company logo - "Dear Sir/Madam.. writing about $9.99 dispute for card XXXX on X date for user [NAME]" (all this is pulled from the Stripe API).
I then have 5 appendixes on separate pages:
Appendix 1: Users' receipt (just a pic of the Stripe receipt)
Appendix 2: User's order history (just printed, name of items, price, and timestamp)
Appendix 3: Screenshot of the user's purchases page clearly showing the item
Appendix 4: Email confirmations - I store copies of each HTML email sent, so just take a picture of this.
Appendix 5: Site activity with IP addresses and timestamps. This is all user actions on my site (viewing items, purchasing, etc.)
I created it because I had 20 disputes piling up, and I was dreading processing them all. Given that you're likely to lose the majority of disputes, it's super discouraging to put in the work, but this makes it a bit easier (I don't want to let fraudsters just get away with it!).
While they do make the point about introducing new features, they don’t address how to make an interrupt-driven announcement successful with existing users.
Has anyone seen a good way to make ongoing update announcements