[dead]
Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
21–30 of 37 posts
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#22Could you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!
Yep, 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.
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#23nice 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
#24Can you please provide some screenshots and examples issues? It's hard to guess the usability without it.
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#25Just 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!
You don’t need resend anymore, email is CF native.
Finally! Hopefully we can stop hearing about Resend. Hyping up an SES wrapper like it's the cure for cancer.
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#26Could you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!
Yep, 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.
Thanks 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.
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#27Just 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!
[dead]
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#28Just 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!
You don’t need resend anymore, email is CF native.
[dead]
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#29I 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.
[dead]
Re: Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues
#30nice 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
[flagged]