From customer message to reply, in seconds.
OmniSaaSy sits between the platforms your customers use and your Intercom workspace. Messages come in, replies go out from your team or Fin, and nobody has to leave Intercom.
Source platforms
- Google Play
- Google Business Reviews
- Apple App Store
- Trustpilot
- X (Twitter)
OmniSaaSy
Bi-directional, real-time. Normalises every platform's events into a single conversation shape Intercom can consume.
Intercom
Every relayed event lands as a conversation, tagged with the source platform and ready for your team to reply.
Inbound and outbound flow.
Two mirror-image journeys, both running constantly in the background.
Inbound flow
- Customer posts a comment, review, DM or rating on a connected platform.
- OmniSaaSy receives the event in real time (webhooks) or on schedule (polling).
- The event is normalised into our common conversation shape.
- We open or update the matching Intercom conversation and attach the message.
- Your team sees it in the same inbox as the rest of their work.
Outbound flow
- Your team replies from inside Intercom as normal, or Fin replies automatically.
- Intercom's outbound webhook fires to OmniSaaSy.
- We look up the original platform, conversation and recipient.
- We send the reply back through that platform's API with the right shape.
- The customer sees the reply on the same platform they messaged you on, whether it came from a person or Fin.
The eight features behind the relay.
Every part of OmniSaaSy, and what each one does.
Hover to read more.
Workspace
Your tenant in OmniSaaSy. Holds users, billing, channels, and audit history. One workspace per Intercom org.
Intercom connection
The OAuth link to your Intercom workspace. Holds the access tokens, conversation routing rules and outbound webhook secret.
Connected accounts
One per third-party platform credential. A workspace can hold many of these and route to different Intercom inboxes per account.
Channels
A channel describes what we listen for and where to put it. Connected accounts can power multiple channels.
Inbound messages
Every event we accept from a connected platform — comment, DM, review, mention. Stored, tagged, then forwarded to Intercom.
Outbound replies
Every reply we relay out from Intercom to a platform. Recorded with the upstream API response for audit and retries.
Usage counters
Per-channel monthly counters used for billing and quota alerts. Reset on the workspace's billing anchor.
Insight Analytics
See where your conversation volume is going — inbound versus outbound, broken down by channel and platform. Spot the channels carrying the most weight at a glance.
Six things worth knowing.
The edge cases that come up most often.
Delete in one place
Redact a message in Intercom and OmniSaaSy will delete the original on the platform too, so the customer's view stays consistent.
Fin replies
Let Fin answer customers directly on any channel. Enable it per channel and Fin's replies relay straight back to the source, just like a human reply.
One view
Every channel's events land in the same Intercom inbox tagged by source, so reporting works across platforms with no extra setup.
Never hit a wall
If you're brushing up against the message ceiling, the volume add-on raises the per-channel quota. Get in touch if you need to go higher than that and we'll work out the right cap together.
Nothing gets lost
Webhook delivery is retried with exponential backoff. Outbound failures are surfaced as Intercom conversations on your admin inbox.
Plan ahead
Workspaces get usage alerts well before quota is hit, with one-click plan upgrades or per-channel ceiling tweaks.
Give your team their day back.
Connect Intercom. Pick your channels. Watch every customer message land in one place. It really is that simple.