As a solopreneur means you have to do everything, right?
So my gmail now looks like Time Square at the midnight of new year.
But I have to reply most of them(except trash and ads), it almost take all my time, I am scared to open the gmail now.
How did you guys handle it at first?
New to CS and already overwhelmed by the inbox
I just started working in customer success, and I didn’t realize how much of the job would be email.
One client is very formal, another is super casual, and I also work with customers in different countries. Some of their emails seem AI-written or translated, so the wording can be confusing and I’m not always sure what they actually mean.
Then I spend even more time worrying about whether my reply sounds right for that particular customer.
It’s gotten to the point where opening Gmail makes me anxious because every conversation seems to need a different tone and context.
Did anyone else struggle with this when they first started in CS? Did you use templates, keep notes on how each customer communicates, or does it just get easier with experience?
We originally built Okeight just to help write replies.
But when I used it for scheduling emails, I noticed I still had to leave Gmail and manually create the meeting after we agreed on a time.
So we added this.
It reads the confirmed time from the email, drafts the reply, and asks if you want to add the meeting to your calendar.
Nothing happens until you confirm it.
A small update, but this is probably one of the features I use most now.
I don't always want AI to decide what I should say.
Sometimes I already know exactly what I mean，I just don't want to type and polish the whole message.
So we added an intent mode to Okeight.
Hold Option, say something rough like “going to SF for a jazz show and seeing a friend,” then release. It uses the conversation around the text box to turn that into a message.
No prompt window and no copying the conversation over first.
It still gets the tone wrong sometimes, but speaking the intent feels surprisingly natural.
Not the work. The replies. The forty little acknowledgements a day that exist only so people know you saw the message.
I used to treat each one like it mattered, then wonder why I was fried by 3pm.
Now I draft the low-stakes ones in my own voice and send in two seconds, and I keep my actual brain for the messages that need thought.
The weird part is people say I've gotten more responsive and more thoughtful. I've just stopped spending real attention on "sounds good, will look after lunch."
Where do you draw the line between a reply that deserves you and one that just needs to exist?
founder here, been building this for the past few months and finally shipped it.
the problem i kept hitting: replying to stuff in slack,email,wechat means either writing it myself when i'm already drained, or pasting the thread into chatgpt and getting back something that sounds like a linkedin post. "Thanks for reaching out! I'd be happy to..." nobody talks like that
so okeight works like this: double tap the option key in any app, it reads the conversation on screen and gives you a few drafts right next to the input box. arrow keys to switch, enter to fill. it never sends anything for you.
the part that took the longest: it only learns from messages you've sent, not what you've read. so drafts actually sound like you instead of generic ai voice. took a few weeks of my own usage before it clicked, now it's genuinely hard to tell my drafts from its drafts
there's also a voice mode, hold option and say "say yes but move it to 4pm" and it writes the full reply
video is a real slack thread, one take, nothing staged. mac only for now.
still debating the double-tap-option trigger, most testers like it but one guy keeps hitting it by accident when he alt-tabs. open to opinions on that
Hey everyone,
We’re building OpenTag an open-source way to @ mention AI agents directly inside GitHub issues, PRs, Slack threads, and other workspaces.
The idea is simple: instead of copying context into a separate chat window, you can tag an agent where the work already happens and get the result back in the same thread.
Right now, OpenTag supports GitHub + Slack ingress, a local-first runner, an auditable dispatcher, a TypeScript SDK, and a working Codex executor.
It’s still early v0, but we’re sharing it in public because we’d love feedback from people building with agents.
Curious to hear:
GitHub: github.com/amplifthq/opentag
Hey everyone,
This started from a personal annoyance.
Every time I wanted an AI agent to do something with a GitHub issue or a Slack discussion, I had to copy it out, paste it into a chat window, re-explain the context, and then paste the result back.
The work was in one place; the agent was always somewhere else.
So I built OpenTag.
The idea is simple: you tag an agent directly in the thread, it runs with the right context, and the result comes back to the same place progress, changed files, or even a full pull request.
What it does today:
It’s a young v0, and I’m sharing it early on purpose because I’d love feedback on a few things:
GitHub:
https://github.com/amplifthq/opentag
Any thoughts are welcome even “this is pointless because X” is useful right now.
Hey Product Hunt,
This time I'd like to introduce our latest product: Invoko.
When dealing with everyday tasks, we'd always feel overwhelmed with a lot of distractions: multiple agent sessions running at the same time, messages from slack popping up all day, colleges asking for quick calls out of nowhere, isn't it nice to have someone or something to handle these and sort them out for you?
That's the reason we build Invoko.
Invoko is a desktop agent lives on your mac that you can talk to while working. By simply pressing a shortcut (Fn), you can dispatch all the tasks that you don't want to handle to it. No matter it's sorting your emails and extract todo lists, or scheduling calendar to avoid those annoying quick calls, or simply replying to messages that you don't want to engage, Invoko got your back.
It's fully local deployed on your mac, which means it can easily understand what you are doing right now and what's your intention. It can operate across all your apps with full functionalities and zero privacy concern.
We've put around 3 months to build Invoko and have iterated 71 times till this morning (based on the version # lol)
It's something that we use daily within our team and we genuinely think that it can benefit ppl with the same pain points and passion.
For trying it out, please head to: https://www.producthunt.com/products/invoko
If you find any issue or bug, please reach out to hey@invoko.ai. We read & reply to every user email manually (100% hand written)
Hope you like it and we can't wait to hear your thoughts!
The idea is simple: instead of opening a new AI tab, copying context over, explaining what you’re doing, and then pasting the result back, Invoko stays on your Mac and helps from the context you’re already in.
What it can do：
It’s still in beta, so it’s not perfect yet. But the goal is to make an AI assistant that feels less like a separate destination and more like part of the OS.
Free while we’re in beta.
Feedback welcome.
https://reddit.com/link/1u3ej5c/video/ow6ox8pqjq6h1/player
Just ask what you want to do on you screen, invoko will help you see and finish the work!
The thing that keeps most people from using tools like OpenClaw isn't interest, it's Docker setup on a Tuesday night.
Invoko is the no-setup version of this category. Download it on Mac, press Fn, say what you want, it sees your screen and open apps and acts. No infrastructure, no model config, no API key. Immediately usable.
What it actually does: reads whatever's on your screen as context and executes across apps. I had a job listing open last week and said 'save the key requirements to my research Notion page and draft a cold message to the hiring manager based on my background.' It read the listing and did both.
Tradeoffs worth knowing: not self-hosted, not always-on, invocation-based. You call it, it acts, done. For long-running autonomous stuff this isn't it. For on-demand screen-aware execution it's the fastest path I've found.
How are people in this space thinking about the deploy-complexity vs accessibility tradeoff right now?
Looking for people who do real work on Mac and will tell us what breaks.
Invoko: press Fn, say what you want to happen, it reads your screen and open apps and does it across however many apps are involved. One command, multiple apps, no switching.
From early access:
'From this invoice email, mark it paid in my tracker and send a confirmation reply.' Done.
'Take the notes in this doc and create a calendar invite with the people mentioned.' Done.
'Summarize this PR and post a brief to the team channel.' Done.
Free during beta. Mac only. No API key.
We want: real usage, honest failure reports.
Where did it misunderstand?
What did you try that didn't work?
'This is cool' doesn't help us. 'I tried X and it did Y' does.
Drop a comment or DM if you want in.