Earlier quoted context omitted.
Yeah GitHub repos need screenshots.
Just have Codex or whatever take the screenshots and post them to the repo. Easy peasy.
it is more efficient to prompt the meat proxy
Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
11–20 of 37 posts
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#12I 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
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#13Can it kill Jira? That’s all I ask :(
For what specific use case would you like to kill Jira?
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#14nice 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 turne…
Yeah Im sure threading detection must break at least 30% of the time
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#15I 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 t…
I 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.
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#16nice 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 turne…
[deleted]
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#17Can it kill Jira? That’s all I ask :(
I built my own very similarly targeted cloudflare hosted open source wiki and task management application https://github.com/TAJD/projektor
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#18I 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 t…
We wrote one in go, htmx and we've been using it for several months now without any issue.
Helpdesk is easy to build!
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#19Looks 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.)?
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#20This 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