4 ms·
Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
- gepeake 21d agoJust used a very similar stack to make my own mail client. Workers for routing, Resend for sending, uses a CF and Resend key to set up any inbox on any domain I want ~instantly so I can have inboxes for everything. Very cool, I think workers are underrated!
- aetherspawn 21d agoYou don’t need resend anymore, email is CF native.
- xeornet 21d agoFinally! Hopefully we can stop hearing about Resend. Hyping up an SES wrapper like it's the cure for cancer.
- mirza_rizvi 21d ago[dead]
- mirza_rizvi 21d ago[dead]
- orliesaurus 21d agoCould you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!
- aetherspawn 21d agoYeah GitHub repos need screenshots.
- ttul 21d agoJust have Codex or whatever take the screenshots and post them to the repo. Easy peasy.
- brazukadev 21d agoit is more efficient to prompt the meat proxy
- mirza_rizvi 21d agoYep, you're right. I spent way too much time on the setup/deployment side and somehow skipped the obvious part. I'll get some screenshots into the README.
- tathagatadg 21d agoThanks for making this - like others commenting here, working on something similar, but more for personal email workflow rather than a product. I'd definitely like to give it a spin - the screenshots (ahem video) would be great.
- roflchoppa 21d agoCan it kill Jira? That’s all I ask :(
- robgough 21d agoI get the temptation to self-host your support platform, as the existing tooling out there can be quite expensive when you want to upgrade from just using an email inbox. If any founders find themselves reading this, and don't think it's the best idea to self-host your own support infra, I've just spent the last 6+ months building stayupfront.com which has, I think, quite reasonable pricing, and a few more features than this... largely around the customer's portal experience (changelog, roadmap, etc.) and includes monitoring & incident management which I think should all be ran from the same surface. I've only just soft-launched, so still have founding pricing on there. Would certainly love to speak to others in this space too, as I was surprised how neglected an area it seemed to be when I was trying to find a replacement for jira service desk for a company I was working with at the beginning of this year.
- ttoinou 21d agoI dont think the helpdesk / webmail space is saturated, I was looking into this and most of them don’t have the features I need such as automatic LLM assistance, automated translation, sharing tickets among multiple accounts etc.
- mirza_rizvi 21d ago[dead]
- robgough 20d agoThe only listed feature here I've not got is the automated translation. It will currently draft responses in the incoming language right now – though that's not terribly useful if you don't speak that language. I'd been considering mostly an English speaking audience at launch. To be more accurate, I was generally thinking about users physically local to me initially, so I could meet with them for customer onboarding and feedback etc. Your post has got me thinking on an approach to making translation work in an open and honest way, so that is something I will experiment with and hopefully get in quite quickly. If you'd be interested in helping me test that, please feel free to reach out to hello@stayupfront.com
- faangguyindia 21d ago
- sfraxo 21d agonice stack. one question from someone who just built one of these: how do you handle inbound email threading? in my case the provider (SES) rewrites the Message-ID in transit, so In-Reply-To/References matching silently breaks. I ended up putting the ticket id in a plus address on the Reply-To, the envelope survives even when the headers don't. also curious how you handle webhook redeliveries, for me duplicates turned out to be the normal case, not the rare one.
- ttoinou 21d agoYeah Im sure threading detection must break at least 30% of the time
- mirza_rizvi 21d ago[flagged]
- mirza_rizvi 21d agoStill a lot of work left to do ofc
- deleted 21d ago[deleted]
- deleted 21d ago[deleted]
- 14u2c 21d agoIt may be very nice, but with no screenshots and no demo site you're going to have trouble getting people to try it out.
- kushalpandya 21d agoI built something similar, but for in-app Issue Reporting, as my macOS app needed a way for users to file bugs without having to create an issue in GitHub https://github.com/kushalpandya/Sluice https://github.com/kushalpandya/Sluice
- adobrawy 21d agoLooks great, and something I might try for my project. I am currently at stage of single mailbox, and bunch automation around it. For example, Google Apps Script trigger Claude Code routine to investigate issue, and draft email ahead of me looking at it. If I do not like draft, I get back to Claude session to fix draft, and make PR to fix prompt for next time. Curious, why did you choose OpenAI over CloudFlare AI (harness etc.)?
- cpursley 21d agoThis is neat, might give it a spin. I've had little luck getting good results from AI bots no matter how grounded they are with good quality context and examples. I actually decided to just build a dead-simple support chat that pipes into Telegram which has worked great for my simple saas support use case. If anyone wants access, just let me know: https://goodsupport.dev https://goodsupport.dev
- byako 21d ago[dead]
- vogje01 21d agoCan you please provide some screenshots and examples issues? It's hard to guess the usability without it.
- elatelee 20d ago[dead]
- alexsqncr 20d ago[flagged]
- deleted 19d ago[deleted]
- mirza_rizvi 19d ago[dead]