It never invents an answer
Replies come from your knowledge base and your own systems. When neither has the answer, it says so and hands over, instead of making up a refund policy.
Features
The agent answers what it can from what your business told it, and hands the rest to a person. Every step is visible, and every reply can be traced.
Most chatbots guess. SoRex is built so the agent only says what your business told it, and so the people and data behind it stay safe.
Replies come from your knowledge base and your own systems. When neither has the answer, it says so and hands over, instead of making up a refund policy.
Questions it could not answer are turned into draft articles, written from what your teammate replied. Nothing goes live until an admin approves it.
You declare read-only views of your database. Every query is built by the server and filtered to the customer asking, so nobody sees anyone else's rows.
Reply windows, approved templates and opt-outs are checked before anything is sent, so a campaign never trips over a platform's policy.
It asks for a rating only on resolved chats, once, and always shows how many people answered next to the score.
Channel tokens are encrypted before they are stored and only decrypted in memory to send. Staff see what their role allows, and transcript reads are audited.
Voice agent
Customers who would rather talk get the same agent, with the same knowledge, on a live call. It speaks for your business and writes everything back to the inbox.
Customer
Incoming WhatsApp call
00:00
Example call
Every feature, on every plan.
WhatsApp, Instagram, Messenger, Telegram, email, a website widget, in-app chat and voice calls land in the same place.
Any staff member can step into a conversation. The agent pauses until it is handed back.
Escalations rotate fairly across the people on each queue, with three rules on top.
Articles are found with hybrid search that tolerates typos and spelling variants, and each reply records what it used.
Connect your database read-only as named views, and add custom tools that call your API.
Verified channels link silently. Others ask for a registered number, with an OTP when it matters.
Send to a filtered audience or a pasted list, and schedule posts to Facebook, Instagram, X and LinkedIn.
The agent picks up calls and talks to customers on your behalf, and your team can answer calls from the browser too.
Every tool the agent can use is also an API, with the same scope, trust and validation checks.
Faster answers for customers, less repetition for your team, and one place to see all of it.
Customers get a reply on chat and on calls even when your team is offline.
Every channel in one place, so nothing slips between WhatsApp, Instagram and email.
Replies come from your own knowledge and data, and every one records where it came from.
Small talk like “ok” and “hello” gets an instant reply, and routine questions are handled before they reach a person.
Take over any chat in one click, route escalations fairly, and follow up with full history.
Start with a few articles and one channel. Add data, tools, staff and channels without changing anything else.
The same inbox, wherever your staff are.
The full dashboard in the browser: inbox, team and queues, knowledge, data, tools, campaigns and posts.
Follow conversations and take over from your phone.
The same inbox on iPhone, so nobody has to be at a desk to step in.
Choose the plan that fits your team today. Every plan runs on the same platform.
Every social channel, handled two ways.
SoRex answers the messages people send you on social media, and it writes and publishes the posts you send out. Both live in the same console.
Conversations
Answer every DM, chat and email
Messages arrive through each platform's official API, go through the same agent, and land in one inbox your team shares.
Publishing
Write once, post everywhere
Describe a post. SoRex drafts a version for each platform plus an image, you edit it, and it publishes on schedule.
Limits are checked while you write, so a post that is too long or missing an image is caught before it is scheduled. Each platform gets its own status and link, so if one fails the others still go out.