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.
I 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.
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.
The 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
Just 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!
Looks 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.)?
I 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
This 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
nice 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.
Could you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!
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
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.
I 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.
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.
The 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
We wrote one in go, htmx and we've been using it for several months now without any issue.
Helpdesk is easy to build!
Freescout is open source and all its plugins is how we solved customer support at https://username.md
Just 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.
Looks 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.)?
Can you please provide some screenshots and examples issues? It's hard to guess the usability without it.
I 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
It may be very nice, but with no screenshots and no demo site you're going to have trouble getting people to try it out.
Can it kill Jira? That’s all I ask :(
For what specific use case would you like to kill Jira?
I built my own very similarly targeted cloudflare hosted open source wiki and task management application https://github.com/TAJD/projektor
This 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
nice 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.
Yeah Im sure threading detection must break at least 30% of the time
Still a lot of work left to do ofc