I developed 12Bot, a SaaS platform that brings WhatsApp, Instagram, and Facebook conversations into one place.
One shared inbox, AI-powered replies, automation, CRM, and lead management.
Built to make customer communication simpler.
#SaaS#BuildInPublic#SoftwareDevelopment
Small business owners: customers now message on WhatsApp, Instagram and Facebook. How do you keep track of who replied to whom, especially after hours? I'm a developer working on a shared inbox for this and want to hear what actually works for you.
Agents, when a buyer messages on Instagram or Facebook about a listing and your team is busy, how long does the first reply usually take? And who owns that lead after the first message? Trying to understand how teams handle it before I build more.
Question for Dubai brokers: do most of your WhatsApp leads expect replies in English, Arabic, or both? And when a team shares one number, how do you stop two agents answering the same lead?
Agents, quick question: when a new lead messages at 11pm, do you reply that night or first thing in the morning? Have you noticed it changes whether they book a viewing? Trying to understand this properly before I build follow-up features.
@AIMoshHq Fair catch, thanks. The free plan is for trying the Instagram and Facebook inbox, and WhatsApp plus AI replies start on Starter, which has the 7-day trial. I'll point clinic posts to the trial from now on.
Clinics and property agents share a problem: WhatsApp, Instagram and Facebook enquiries after hours, no one sure who replied, leads gone cold.
I built 12Bot for it. One inbox, AI answers common questions, every enquiry saved as a lead.
DM me or try https://t.co/R80M0BJG14 free
@TangEstate@actrfg@HellenTUSA Posting it in both English and Chinese makes a lot of sense for that area. Hope the Saturday open house brings you a good tenant quickly.
12Bot is managing real customer chats.
51,187+ conversations automated
152,616+ messages processed
10,041+ leads captured
89+ live automations
Real platform usage across WhatsApp, Instagram, and Facebook.
And we are still building.
#SaaS#StartupGrowth#Automation
@cyberallante Can have this live before Monday. I build with Next.js and AI tools daily, and I am fine with an NDA. Recent work: https://t.co/qmuo4Pjno8
@harikesh_devops Point 1 is the easiest to get wrong. Putting the tenant ID and role in the cache key is cheap, and far simpler than invalidating shared entries after permissions change. Short TTLs on anything permission-dependent cover most of point 4.
@mustaphaDevFS Logs help most when every line carries a request ID and the user or tenant ID. Then a bug a customer reports at 3pm is one search instead of guesswork. Structured JSON logs from day one cost almost nothing.
@_kekule15 A common one is fixing a bug that other code was quietly compensating for. Fix the timezone on order dates and a report that was adjusting for the old behaviour is now off by a day. Before shipping a fix, check everything that reads that field, not just what writes it.
@SamVale29 The classic one in multi-tenant apps is an endpoint that checks you're logged in but not that the record belongs to your tenant. Change an ID in the URL and you see someone else's data. Scoping every query by tenant at the data layer catches what route checks miss.