Hey PH!
I'm Akash, and I built Foxchat because I got tired of paying Intercom prices just to chat with website visitors.
Foxchat is a live chat widget that lets you reply to website chats directly from Slack. No new dashboard to learn, no per-message fees, setup takes about 5 minutes.
What makes it different:
✔️ Reply from Slack (where you already are).
✔️ AI Assist suggests replies in your Slack threads using Claude.
✔️ Add your docs as a knowledge base so AI replies stay accurate.
✔️ Transparent pricing, no surprise per-resolution charges.
I built this for developers and small teams who want Intercom-level UX without the Intercom-level bill.
Would love your feedback. Happy to answer any questions here!
Report
@designerdada The Slack-native approach is the right call — switching to a separate dashboard just to reply to a chat is friction nobody needs. Knowledge base + Claude for accurate AI suggestions is a solid combo, that's usually where live chat AI falls apart. Congrats on the launch Akash! Curious — how does it handle offline hours, does AI take over automatically or does it queue for the team?
If a startup is already using an Intercom alternative like a basic widget or a helpdesk, what are the top 1–2 moments where Foxchat is meaningfully better and worth switching—especially considering migration risk and changing internal habits?
@curiouskitty It's for small teams and individual where team members handles support. Foxchat is incredibly useful if teams are already living in Slack. They don't need to switch screens just to reply to support tickets.
Report
I love the idea of this -- having troubles connecting though.
@corey_leon You can share this link and ask the ai agent to troubleshoot. This usually happens when your Slack is not setup properly. Make sure
you have selected the default Slack channel
you have enabled a team member to send messages via Slack
You can reach out to me via chat widget from the dashboard if you're still having some trouble
Report
@designerdada Okay, widget is working! Now, it doesn't seem to send the message back to the person when I send in the slack thread
Report
The "no per-message fees" line is doing a lot of heavy lifting — that's quietly where Intercom gets expensive for any startup seeing real traction. The knowledge base + Claude combo for AI suggestions is the right architecture too, grounding replies in your actual docs instead of hallucinating support answers. Does it support multiple Slack workspaces or is it strictly one workspace per site?
Report
@giammbo is this [not using docs] still common now? —
> The knowledge base + Claude combo for AI suggestions is the right architecture too, grounding replies in your actual docs instead of hallucinating support answers.
Report
@hboon Surprisingly still common, yeah — a lot of tools bolt AI on without proper retrieval, which is fine until a customer asks something product-specific and gets a confident hallucination. The doc-grounding is the right call.
Report
This is the right product at the right price point. I've run support across 15 countries for a hardware brand — started with Intercom, eventually realized we were paying $300/mo for what 2 people in Slack could handle better.
The real test for tools like this is what happens when your customers and your team aren't in the same timezone or language. A customer writes in at 2am your time, gets no response, and by morning they've already emailed your competitor. Does the AI assist handle that gap — auto-responding in the customer's language, buying time until a human can follow up?
That's the unsexy problem that kills small teams going international. Not features, not pricing — just the 14-hour timezone void where nobody's watching.
Report
I’ve been analyzing a lot of AI tools recently and the biggest thing I notice is people struggle to compare them properly. Curious how you position this vs the current options.
Replies
AutoSend
@designerdada The Slack-native approach is the right call — switching to a separate dashboard just to reply to a chat is friction nobody needs. Knowledge base + Claude for accurate AI suggestions is a solid combo, that's usually where live chat AI falls apart. Congrats on the launch Akash! Curious — how does it handle offline hours, does AI take over automatically or does it queue for the team?
AutoSend
@mangal_s07 It queues for the team
AutoSend
Loved the experience! We are actively using this in AutoSend 🚀
Product Hunt
AutoSend
@curiouskitty It's for small teams and individual where team members handles support. Foxchat is incredibly useful if teams are already living in Slack. They don't need to switch screens just to reply to support tickets.
I love the idea of this -- having troubles connecting though.
AutoSend
@corey_leon Checking right away
AutoSend
@corey_leon It should be working now!
@designerdada Working but the widget doesn't work. I'm using base44.com as my website hoster. And it doesn't seem to connect. Would you know why?
AutoSend
@corey_leon You can share this link and ask the ai agent to troubleshoot. This usually happens when your Slack is not setup properly. Make sure
you have selected the default Slack channel
you have enabled a team member to send messages via Slack
You can reach out to me via chat widget from the dashboard if you're still having some trouble
@designerdada Okay, widget is working! Now, it doesn't seem to send the message back to the person when I send in the slack thread
The "no per-message fees" line is doing a lot of heavy lifting — that's quietly where Intercom gets expensive for any startup seeing real traction. The knowledge base + Claude combo for AI suggestions is the right architecture too, grounding replies in your actual docs instead of hallucinating support answers. Does it support multiple Slack workspaces or is it strictly one workspace per site?
@giammbo is this [not using docs] still common now? —
> The knowledge base + Claude combo for AI suggestions is the right architecture too, grounding replies in your actual docs instead of hallucinating support answers.
@hboon Surprisingly still common, yeah — a lot of tools bolt AI on without proper retrieval, which is fine until a customer asks something product-specific and gets a confident hallucination. The doc-grounding is the right call.
This is the right product at the right price point. I've run support across 15 countries for a hardware brand — started with Intercom, eventually realized we were paying $300/mo for what 2 people in Slack could handle better.
The real test for tools like this is what happens when your customers and your team aren't in the same timezone or language. A customer writes in at 2am your time, gets no response, and by morning they've already emailed your competitor. Does the AI assist handle that gap — auto-responding in the customer's language, buying time until a human can follow up?
That's the unsexy problem that kills small teams going international. Not features, not pricing — just the 14-hour timezone void where nobody's watching.