Nobody checks five apps
A Friday-evening Instagram comment about urgent pain relief surfaces in the same stream as a Facebook DM, so it doesn't sit unseen until Monday just because nobody opened that specific app over the weekend.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business responds to customer messages and comments faster because every conversation from every platform lands in one place instead of five separate apps.
Works with
What it does
Socie pulls comments, mentions, and direct messages from all connected accounts into a single filterable inbox stream. Owners can reply, tag a message for follow-up, or mark it resolved without switching apps.
A dental clinic's Instagram gets a steady trickle of enquiries in the comments and DMs — 'do you take walk-ins', 'what's a root canal cost' — but the practice manager only checks Instagram once a day, buried under Facebook Messenger and a LinkedIn tab nobody remembers to open. A patient asking about urgent pain relief on a Friday evening doesn't get an answer until Monday.
A single inbox pulls comments, mentions and direct messages from every connected account into one filterable stream, so a reply, a follow-up tag or a resolved mark happens without switching between five apps. Speed matters here specifically because Instagram and Facebook enforce their own reply-window rules — a message sent back too late after a customer's last contact can simply fail to deliver, which makes a unified inbox less a convenience and more the difference between an enquiry answered and one silently lost.
Socie runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Comments, mentions and direct messages from every connected account arrive together in a single inbox, filterable by platform or status, so nobody has to remember to separately check Instagram, then Facebook, then LinkedIn every single morning.
Each connected platform pushes new messages through a webhook the moment they arrive, so a Friday-evening enquiry about urgent pain relief shows up promptly rather than sitting unseen until someone happens to open the right app the next morning.
An agent replies directly from the unified stream, tags a message for follow-up, or marks it resolved, all without leaving this one screen to open the platform's own separate app just to send a response.
Because webhook delivery isn't guaranteed by any platform, a periodic poll checks for anything a webhook might have missed, so a dropped delivery doesn't mean a message is simply never seen by anyone at the clinic at all.
Why it matters
A Friday-evening Instagram comment about urgent pain relief surfaces in the same stream as a Facebook DM, so it doesn't sit unseen until Monday just because nobody opened that specific app over the weekend.
An agent replying to messages doesn't need separate muscle memory for Instagram's interface versus Facebook's — one inbox, one way of replying, tagging and resolving, regardless of where the message actually originated.
Marking a conversation open, tagged or resolved means a practice manager scanning the queue can see at a glance what's still genuinely waiting on a reply.
The detail
Reply timing is a real, platform-enforced constraint, not just good customer service practice. Meta applies a standard messaging window — commonly 24 hours from a customer's last message — for many message types across Facebook and Instagram, and a reply attempted after that window closes can simply fail to send, regardless of how relevant the response is. This makes response speed a functional requirement, not a nicety: a message sitting unanswered for a day and a half can be one the platform is now blocking from reaching the customer at all.
Webhook delivery is not guaranteed by any platform, worth understanding rather than assuming away. A webhook can fail to fire due to a temporary outage, a timeout, or a momentary connectivity issue, and if the inbox relied purely on webhooks with no fallback, a dropped delivery would mean a message that never appears anywhere. A polling job that periodically checks for anything a webhook missed exists specifically to close that gap — the difference between an occasional missed webhook being a non-event versus a genuinely lost enquiry.
Customer messages captured through the inbox are personal data, carrying a real handling obligation beyond displaying them conveniently. A patient's message about a medical concern, or any customer's phone number and enquiry history, needs the same privacy and retention discipline as any other customer record — not disposable engagement metadata just because it arrived through a comment section rather than a form. A business storing this history should have a clear view of retention and who on the team can see it.
Industry use cases
12 industries where Socie applies this directly.
A car service center plans a week of posts showing before/after detailing work and a monsoon check-up reminder, schedules them all on Monday morning, and lets Socie publish each one at its recommended time through the week.
See the automotive playbookA B2B software reseller drafts three LinkedIn posts about a recent client rollout, routes them through an approval step to the sales director, and once approved they publish automatically on the days set in the calendar.
See the b2b sales playbookA regional NBFC's marketing associate drafts a post about a new loan product, and it sits in the approval queue until the compliance officer reviews the wording and either approves it or sends it back with a comment.
See the banking and finance playbookA cosmetics brand uploads a batch of new product photos to the media library, drags them onto the grid preview to arrange the order, then schedules the whole week's worth of posts in one sitting.
See the beauty and cosmetics playbookA freelance graphic designer uses the AI content-idea generator to get five post concepts, turns two into drafts, and schedules them for the week so their profile stays active while they focus on client work.
See the freelancers and consultants playbookA physiotherapy clinic drafts a post about a new treatment offering, and the clinic owner reviews and approves the exact wording before it's allowed to schedule.
See the health and wellness playbookA furniture showroom uploads new collection photos, previews how they'll look next to already-published posts in the grid, reorders a few tiles, and schedules the finalized sequence.
See the home decor and furnishing playbookAn agency account manager creates draft posts for two different retail clients, sends each batch through that client's own approval workflow, and later exports a branded campaign report for each client separately.
See the marketing agencies playbookA real estate broker uploads photos of a new listing, generates a caption highlighting the property's key features, and schedules posts across Instagram and Facebook to go live over the coming days.
See the real estate playbookA restaurant manager schedules a week of daily-special posts on Sunday night, with AI-suggested captions and hashtags for each dish, and Socie publishes them automatically at lunch and dinner hours.
See the restaurants and food playbookA salon owner previews how a new set of styling photos will look in sequence on the grid, adjusts the order, and schedules the batch to post through the week alongside a recycled "book now" reminder post.
See the spas and salons playbookA travel agency schedules a series of destination-highlight posts ahead of a holiday season, using the content calendar to make sure posts are spaced out rather than bunched on one day.
See the travel and tourism playbookMore from Socie
The business can see everything planned across all social channels for the month at a glance, so gaps and clashes get caught before they become missed posting days.
Learn moreThe business writes a post once, customizes it per network, and it goes out automatically at the chosen time without anyone touching a phone.
Learn moreThe business gets a ready-to-post caption in seconds instead of staring at a blank composer box.
Learn moreThe business reaches more relevant people without manually researching which tags are trending in its niche.
Learn moreThe business never runs out of things to post, even during slow weeks with nothing obviously newsworthy to share.
Learn moreThe business gets a usable, on-brand social graphic without hiring a designer or opening editing software.
Learn moreQuestions
No — Meta enforces a standard messaging window, commonly 24 hours from a customer's last message, for many message types, and a reply attempted after that window closes for the relevant message type can fail to send outright regardless of content. This makes responding promptly a functional necessity rather than just good practice, since a delayed reply can genuinely be blocked by the platform itself, not merely arrive late.
A polling fallback job periodically checks for anything a webhook might have missed, specifically because webhook delivery isn't guaranteed by any platform and can occasionally fail due to a timeout or a temporary outage. Without that fallback, a dropped webhook would mean a message that never surfaces anywhere at all, which is exactly the gap the polling check exists to close.
It needs to be treated with the same privacy and retention discipline as any other customer record, not as disposable engagement data just because it arrived through a social comment or DM rather than a form. A dental clinic in particular should be clear on how long message history is retained and who on staff can actually see it, given the sensitivity of what a patient might mention in an enquiry.
Yes — every message keeps its originating platform visible and filterable, so an agent can tell at a glance whether a given enquiry came through Instagram, Facebook or another connected account, and filter the stream down to just one platform's messages when that's specifically what's needed at that particular moment during a busy shift at a dental clinic's front desk.
The rest of your stack
No rip-and-replace — reply to every dm and comment in one inbox works alongside the systems already running your business.
Coming soon