We have a shared support inbox through Zendesk which has been manned by one part time employee, just scaled that to two part time as we hit $1.5M ARR. We have a FAQ, also via zendesk, to answer common questions. Otherwise we steer most requests to the common mailbox. We have built some apps in Retool to allow customer support to handle common issues like refunds, cancelling subscriptions, updating users, enrolling users to courses, etc. Then there is a slack channel where we can discuss special issues that come up.
We do not fix reported bugs unless they are deemed to be critical, and rather focus on shipping features as we think that brings the most value for us and customers in the long run.
Pretty much our take at Scrimba. Except the most self-motivated students the content needs to take small steps, be relevant, be engaging and have low barriers to getting your hands on the code. So many students say they get an AHA moment with this approach.
Thanks for your feedback! The tutorials section provides in-depth technical content to anyone for free. In addition, it helps drive organic and relevant traffic to AlterClass so that instructors with published courses can benefit from it. No more relevant traffic on AlterClass, the more potential students for the instructors ;)
In August 2021, a putative class action complaint captioned Williams v. Udemy, Inc., Case No. 3:21-CV-06489, was filed against us in the U.S. District Court for the Northern District of California alleging violations of California’s unfair competition and false advertising statutes as well as the California Consumer Legal Remedies Act in connection with the promotional “strike-through” pricing for courses offered on our platform, alleging that the reference prices used for comparison purposes are false or misleading. The complaint seeks injunctive relief, unspecified damages, restitution and disgorgement of profits. We are in the process of investigating the claims alleged in the complaint and have not yet answered. We intend to vigorously defend ourselves in this matter.
How much do you already have decided and available in terms of assets like logo,symbols,icons, colors, fonts, style guides? We spent around $25k I believe for our process that is documented here: https://medium.com/@dnlbtlr/my-agile-design-process-to-redes...
The traditional format will endure, but don´t you think there is ways to improve it? I would think the format is a compromise around the constraints of a teacher to student ratio and the availability of different media where whiteboard was an excellent way to share before digital media. People who learn well from watching others and are highly motivated to get their hands dirty perform well with this format. But isn´t it better to get help if you are stuck - either automated as our format have the context you are working in or by easily sharing your actual code with the context it is written?
We propose that bringing the process of writing code closer to the teaching materials will make more students likely to write more code. We also think making it easier to share your code within a context, without setting up a matching environment online or that the group teacher has to copy it locally, will make it easier to get quality feedback. And we will introduce this feedback loop as a part of the courses where students give feedback on each others code. We think that will give more people access to learning to code, and we can bring it even closer to the realities of being a developer.
We do not fix reported bugs unless they are deemed to be critical, and rather focus on shipping features as we think that brings the most value for us and customers in the long run.
Things are running well!