This is fantastic. I started Stripe's support team, built out our version of an internal tools team, and have since advised a bunch of mid-range startups on how to scale operations. Every company I've talked to is trying to figure out how to improve response times, but really lacks visibility into when load is coming in -- and especially any visibility into when it <i>will</i> come in.<p>The technical solution to modeling this out and providing more advanced forecasting is super interesting, and the product itself looks delightful to use (more than the spreadsheets our early support team used to be buried in navigating, at least :)
Hi HN,<p>I'm John, one of the co-founders of Assembled. Our mission is to transform and elevate customer support.<p>Today we’re launching a product that solves workforce management and helps support teams get staffing right. For the past two years, we’ve been building it alongside some of the most innovative support teams in the world like Slack, Stripe, and Harry’s.<p>Sam Altman’s startup playbook says: “great startups always have great customer service in the early days” [0], but he doesn’t talk about the later days. It turns out to be really hard to scale great support with spreadsheets and internal tools. We’ve built Assembled after talking to hundreds of different organizations that have been trying to solve this problem.<p>Our product tackles three core operational challenges:<p>- Forecasting: We automatically forecast support volume and translate it into the right staffing plan.<p>- Scheduling: We provide an intuitive team calendar that works across time zones and/or multiple specializations.<p>- Unified metrics: We make support schedules and metrics, like response times, visible across all levels.<p>Assembled is available today and you can request a demo here. We’ll be around all day answering questions, so feel free to comment here or email me directly at john@assembled.com.<p>[0] <a href="https://playbook.samaltman.com/" rel="nofollow">https://playbook.samaltman.com/</a>
Congrats on the launch! What's the minimum number of support agents do companies need to have before you're a good fit for them? Or how do you think about what a qualified customer looks like?
This is really cool! I'm working with a customer support team and getting the right amount of staffing was always a challenge. To really reliably have good support with low wait times for 95% of the time, you'd end up being overstaffed by quite a bit for >50% of the time.<p>In addition, just communicating with everyone about shifts and managing the people-side was also a challenge, and there never felt to be super-specialized tools for this.<p>Accurate staffing seems like precisely the kind of problem that good data and modeling could solve. Good communication is something that good UI design could solve too. I'm excited to see how this works!