u/Indranil_Maiti

- Used framer motion for animating the content inside card with opacity , blur and y animation

variants={{
initial: { opacity: 0, filter: "blur(4px)", y: 8 },
animate: {
opacity: 1,
filter: "blur(0px)",
y: 0,
transition: {
duration: 0.42,
ease: [0.165, 0.84, 0.44, 1],
},
},
exit: {
opacity: 0,
filter: "blur(4px)",
y: -4,
transition: {
duration: 0.15,
ease: [0.55, 0, 1, 0.45],
},
},
}}
initial="initial"
animate="animate"
exit="exit"

- used https://ui.bklit.com/docs for chart library. It has beautiful components of chart for ready to use.

https://reddit.com/link/1tifc3m/video/kdv8qwwh492h1/player

- Used framer motion for animating the content inside card with opacity , blur and y animation

variants={{
                initial: { opacity: 0, filter: "blur(4px)", y: 8 },
                animate: {
                  opacity: 1,
                  filter: "blur(0px)",
                  y: 0,
                  transition: {
                    duration: 0.42,
                    ease: [0.165, 0.84, 0.44, 1],
                  },
                },
                exit: {
                  opacity: 0,
                  filter: "blur(4px)",
                  y: -4,
                  transition: {
                    duration: 0.15,
                    ease: [0.55, 0, 1, 0.45],
                  },
                },
              }}
              initial="initial"
              animate="animate"
              exit="exit"

- used https://ui.bklit.com/docs for chart library. It has beautiful components of chart for ready to use.

https://reddit.com/link/1tifbbu/video/v6rk2soq592h1/player

Hi everyone,

I’ve been working on a Slack app that transforms your Slack workspace into a fully functional customer support chat. The idea came from the frustration of constantly switching between tools like Intercom/Zendesk for customer messages and Slack with per agent pricing.

With this app, you can:

• Handle customer support in one place. Support@domain.com goes to #support, billing@domain.com goes to #billing. Every conversation is saved stored and ready for ai analysis to fix bugs, content creation, blog post

• Integrate live chat in website and chat from slack

• Simplify your workflow by saving pre filled responses and use them,.AI auto tags every tags and divide each of them based on urgency

Team member assignment so that every ticket is handled by one person only, secondly if someone comes in the middle gets full context of it.

We send a full report every day based tickets solved, still waiting urgent tickets to.your inbox for a quick check.

It’s still in beta, but I’m curious to know if this is something you’d be interested in trying. I don't want to promote, so let me know if it sounds useful. I am in beta and ready to share to you.

I’d love to hear your thoughts and answer any questions.

Thanks! 😊

I built a support tool for teams that live in Slack and don't want to pay per agent based pricing which goes exponentially high with teams that grows.

I would be happy to know if this solves your problem and if not what would you like to have to switch to syncsupport.

Here's what it actually does:

Email to Slack routing

• support@, billing@, sales@ all route to dedicated Slack channels
• Email lands in 2–5 seconds
• No inbox to monitor, no Gmail tab to keep open

Live chat widget

• Two lines of code on your site
• Visitors chat → your team replies from Slack
• Users can send bug screenshots directly in chat — you see them in Slack instantly

Ticket management

• Claim tickets so teammates know it's handled
• Track status: open → in progress → resolved
• No duplicate replies, no dropped tickets

AI auto tag and urgency analysis

• AI tags each ticket e.g. pricing-issue, login-issue for quick analysis and fix and ship them
• AI does urgency analysis as well
• We send daily email with detailed report to your email to take action if tickets are missed.

Canned responses & templates

• Pre-written replies for your most common questions
• One click to insert, edit, send

Analytics

• Response times, ticket volume by alias, 7 and 30-day trends
• Spot which email alias is getting overwhelmed before it becomes a problem

AI monthly digest

• Instead of reading 500 tickets, you get 5 bullet points
• Top pain points surfaced automatically every month

CSV export

• All your data, anytime, no lock-in

The pricing model is the part most teams care about:

• Flat $19/month — no per-seat fees
• Add your 5th, 10th, 20th teammate — same price
• Zendesk charges $55/agent/month — a 10-person team pays $6,600/year
• SyncSupport: $228/year flat

Who this is for:

• Small SaaS teams (2–20 people) already using Slack
• Solo founders who can't check email every hour
• Anyone paying per-seat for a help desk and watching the bill grow

Setup is 5 steps: connect Slack, add your domain, create aliases, embed the widget, send a test email. Under 10 minutes total.

Share your reviews, thoughts, if you want to try this you can contact me for discount as well for your team.

SyncSupport is a comprehensive customer support solution designed to integrate seamlessly with your existing workflow, primarily within Slack. It streamlines customer communication by routing support emails directly to designated Slack channels, ensuring no inquiry goes unnoticed. The platform also offers a live chat widget that can be embedded on your website, allowing real-time interaction with visitors, with responses handled directly from Slack.

• Email-to-Slack Routing: Automatically route all incoming support emails to the appropriate Slack or Discord channels for immediate attention.
• Live Chat Widget: Embed a customizable live chat widget on your website to engage with visitors and capture leads.
• Canned Responses & Templates: Utilize pre-written responses and email templates for quick, consistent, and one-click replies, significantly reducing response times.
• Ticket Management: Claim, track, and manage support tickets directly within Slack, maintaining full visibility and control over customer issues.
• Multi-Domain Support: Manage support for multiple domains with custom email aliases for each.
• AI-Powered Insights: Benefit from AI digests and content suggestions to enhance support quality and efficiency (available on higher tiers).
• Flat-Rate Pricing: Enjoy predictable, per-month pricing with no per-user fees, making it an affordable solution for teams of all sizes.

SyncSupport eliminates the need to switch between multiple tools, allowing your team to manage all customer interactions from within the familiar environment of Slack or Discord. Setup is designed to be quick and straightforward, enabling you to start providing enhanced customer support in minutes.

Today morning I have received few notifications from GSC but I do not know what to do with them.

My project is just 1 week old and I am just starting

As per GSC current stat

1 Total click : 8
2. Total impression : 405
3. Total CTR : 3.4%
4. Average Position : 17.8

Few queries like

external support slack integration, "syncsupport" email management software blog, "syncsupport" vs zendesk

but i am unable to understand what should I do with these queries data. Please help me.

Thanks

I see in the market there are two types of pricing for customer ticket management softwares.

A. Per agent B. Flat based pricing.

I feel for SMBs, soloenterpreneurs per agent cost initially seems to be low but it can grow siginificantly with growth of the teams. Is it the same for you?

Also, they seems to be a bit complex with new dashboard, new software systems, notification system

What are you choosing. I am bit hesitant with zendesk and syncsupport.

Zendesk seems to have per agent pricing and bit complex. On the other hand syncsupport is flat price and simple , managable everything from slack.

Any help would be very helpful .

Last week I launched SyncSupport — a tool that routes support emails directly into Slack so small teams can manage customer tickets without ever leaving Slack and take actions fast, integrate live chat widget and answer from slack. This will be beneficial for solodevs to fix bugs quickly, smbs with small teams, smbs who wants flat price not price/agent.

One week in, no paying customers yet, actively hunting for beta users. But I've already learned more in 7 days than in the months of building.

Here's what I got wrong:

1. I skipped real competitor research and paid for it

I knew who my competitors were — Front, Help Scout, Zendesk. But I didn't go deep enough. I didn't study their Reddit threads, their 1-star reviews, the "why I cancelled" posts. I built what I thought the gap was, not what customers were actually screaming for.

If I'd spent 2 weeks lurking forums before writing a single line of code, I'd have a much sharper positioning today.

Competitor research isn't reading their pricing page. It's reading their angry customers.

2. I spent way too long polishing the UI for an MVP

I genuinely spent weeks getting the UI "right." Animations, spacing, component consistency. For an MVP. For a product with zero users.

Nobody cares how pretty your MVP is. They care if it solves their problem. I should have shipped something functional in half the time and used the saved weeks to talk to customers instead.

Ugly and in users' hands beats beautiful and on your localhost.

3. I chose Resend over AWS SES because I was scared — it cost me $20/month more than it needed to

AWS SES is notoriously cheap (~$0.10/1000 emails). I went with Resend because I wasn't confident setting up SES and Resend had a clean API. Totally understandable at 2am — but now it's a $20/month overhead that compounds.

Not a disaster, but a reminder: don't let lack of confidence push you toward the more expensive option. Resend is great, but I wasn't at scale — I had time to figure out SES.

Uncomfortable ≠ wrong. The scary option is often just the cheaper one.

Where I'm at now:

• 1 week post-launch
• Looking for beta users (if you manage support in Slack, I'd love your feedback)
• Focusing on SEO and content to build organic traction
• Building out features based on early conversations

Would love to hear — what was your biggest mistake in the first week of launching?

Last week I launched SyncSupport — a tool that routes support emails directly into Slack so small teams can manage customer tickets without ever leaving Slack and take actions fast, integrate live chat widget and answer from slack. This will be beneficial for solodevs to fix bugs quickly, smbs with small teams, smbs who wants flat price not price/agent.

One week in, no paying customers yet, actively hunting for beta users. But I've already learned more in 7 days than in the months of building.

Here's what I got wrong:

1. I skipped real competitor research and paid for it

I knew who my competitors were — Front, Help Scout, Zendesk. But I didn't go deep enough. I didn't study their Reddit threads, their 1-star reviews, the "why I cancelled" posts. I built what I thought the gap was, not what customers were actually screaming for.

If I'd spent 2 weeks lurking forums before writing a single line of code, I'd have a much sharper positioning today.

Competitor research isn't reading their pricing page. It's reading their angry customers.

2. I spent way too long polishing the UI for an MVP

I genuinely spent weeks getting the UI "right." Animations, spacing, component consistency. For an MVP. For a product with zero users.

Nobody cares how pretty your MVP is. They care if it solves their problem. I should have shipped something functional in half the time and used the saved weeks to talk to customers instead.

Ugly and in users' hands beats beautiful and on your localhost.

3. I chose Resend over AWS SES because I was scared — it cost me $20/month more than it needed to

AWS SES is notoriously cheap (~$0.10/1000 emails). I went with Resend because I wasn't confident setting up SES and Resend had a clean API. Totally understandable at 2am — but now it's a $20/month overhead that compounds.

Not a disaster, but a reminder: don't let lack of confidence push you toward the more expensive option. Resend is great, but I wasn't at scale — I had time to figure out SES.

Uncomfortable ≠ wrong. The scary option is often just the cheaper one.

Where I'm at now:

• 1 week post-launch
• Looking for beta users (if you manage support in Slack, I'd love your feedback)
• Focusing on SEO and content to build organic traction
• Building out features based on early conversations

Would love to hear — what was your biggest mistake in the first week of launching?