Relvios
Summary
Running support across email, WhatsApp, Instagram, and Slack means your team is context-switching between five tabs before they've had coffee — and half the responses are still late. Relvios collapses that into one inbox where an AI either handles the ticket or drafts the reply for a human to approve.
The vendor describes a single workspace that ingests Gmail, Outlook, SMTP/IMAP, WhatsApp, Instagram, Messenger, Telegram, Slack, Discord, and webhooks, then runs each message through Gemini-based triage — topic tagging, sentiment, priority, suggested action — before routing to either autonomous AI or a human review queue. You configure that boundary per inbox, not globally, which means you can let AI auto-resolve billing FAQ threads while keeping refund requests in human approval mode. Knowledge grounding pulls from docs, PDFs, Google Docs, or markdown, so answers stay tied to verified content rather than model improvisation. The REST and MCP API lets external agents read threads, draft, and reply inside the same guardrails. Teams hitting edge cases in autonomous handling tend to fall back to draft-only mode, which adds a review step but preserves the unified queue.
Bottom line: Relvios is the right call when your support volume spans four channels and your team is losing tickets in separate inboxes — but teams that need on-premise data residency or a perpetual free tier will hit a hard wall immediately, because neither option exists.
Pricing Plans
SubscriptionLast verified 1 week ago- Price
- $19/mo
- Free Tier
- 7-day free trial
Starter
For growing teams
- up to 6 connections
- 5,000 messages/month
- 1 workspace
- All Channels available
- Unlimited Team Members
- Email support
- Audit logs
Pro
Complete multi-channel support
- 15 connections
- 20,000 messages/month
- 3 workspaces
- All Channels available
- Unlimited Team Members
- Priority support
- Audit logs
Business
High volume and scale
- 30 connections
- 50,000 messages/month
- 8 workspaces
- All Channels available
- Unlimited Team Members
- Priority support
- Audit logs
View full pricing on relvios.com →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Per-inbox autonomous vs. draft mode toggle, so you apply different risk thresholds to different customer segments without splitting them into separate tools or writing routing logic.
- Ten channel integrations — Gmail, Outlook, SMTP/IMAP, WhatsApp, Instagram, Messenger, Telegram, Slack, Discord, and webhooks — unified into one ticket queue, which means your team stops losing context switching between inboxes when a customer follows up on a different channel.
- Gemini-powered triage tags topic, sentiment, priority, and suggested next action on every inbound message, so agents inherit structured context instead of reading raw threads to decide what to do first.
- Knowledge base grounding from docs, PDFs, Google Docs, and markdown keeps AI replies tied to verified content, which means the autonomous agent does not improvise answers that contradict your actual policy.
- REST and MCP API exposes the inbox to external agents with guardrails, so teams building broader automation pipelines can route messages through Relvios without bypassing the audit trail or approval controls.
Cons
Sign in to edit- No self-hosted deployment option exists — all data routes through Relvios cloud infrastructure. Teams in regulated industries (healthcare, finance) with contractual on-premise or single-tenant data residency requirements cannot use this tool and will need to evaluate competitors that offer self-hosting.
- The 7-day trial has no perpetual free tier, so evaluation is time-boxed. Teams with slow procurement cycles who need more than a week to gather internal stakeholder sign-off face a forced purchase decision before they have validated fit in production — at which point many move to alternatives that offer a usage-capped free tier without a deadline.
- Autonomous mode configuration happens at the inbox level, not at the message-type or customer-tier level. Teams that need finer-grained rules — auto-resolve for tier-1 customers but always escalate for enterprise accounts within the same inbox — have to build that segmentation upstream by splitting traffic into separate inbox connections before it reaches Relvios.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Web
- API Available
- Yes
- Self-Hosted
- No
- Last Updated
- 2026-06-28T08:30:19.722Z
Best For
Who it's for
- Growing support teams handling multiple channels
- Teams wanting configurable autonomous AI
- Businesses needing ticket analytics and audit logs
What it does well
- Unified multi-channel customer support
- AI triage and automated ticket creation
- Knowledge-base grounded responses
- Human-in-the-loop approval workflows
- Integration with external AI agents via API
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare Relvios
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Relvios free?
- Relvios has a permanent free tier alongside paid upgrades (paid plans from $19/mo). You can keep using a baseline version indefinitely without paying.
- Is Relvios open source?
- No — Relvios is a closed-source tool. Source code is not publicly available.
- Does Relvios have an API?
- Yes. Relvios exposes a developer API. See the official documentation at https://relvios.com for details.
- What platforms does Relvios support?
- Relvios is available on: Web.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Customer messages arrive from a dozen directions — email threads, Instagram DMs, a Discord server, a website chat widget — and most support tools force you to triage them separately. Relvios is a cloud-only AI support inbox that normalizes all of those channels into one workspace. The core workflow: connect your channels via OAuth, SMTP/IMAP, bot integrations, or webhooks; attach your knowledge sources (docs, FAQs, PDFs, Google Docs, markdown); then choose, per inbox, whether AI resolves high-confidence tickets automatically or prepares drafts for a human to approve before anything sends. Every inbound message becomes a numbered ticket moving through Open, Pending, Resolved, and Closed states, with audit logs and analytics attached.
The differentiating feature is the per-inbox autonomous/HITL toggle. Most AI support tools make you choose one operating mode globally — you are either running an autonomous bot or a draft assistant. Relvios lets you run both in the same workspace: autonomous resolution on your public-facing FAQ inbox, human approval required on your enterprise account inbox. That boundary is configurable without engineering work, which matters when your risk tolerance is not uniform across customer segments.
The API and MCP protocol layer is worth noting for teams building agent pipelines. The vendor describes exposing the inbox to external AI agents with explicit guardrails — those agents can list threads, read context, draft replies, and respond, but within defined constraints. For teams integrating Relvios into a broader automation stack rather than using it as a standalone tool, this is the mechanism that makes that possible.
The fit is clearest for growing support teams managing multi-channel volume without a dedicated platform. Where it breaks: there is no self-hosted option, so teams with strict data residency requirements cannot route around the vendor’s cloud. The freemium model has no perpetual free tier — the vendor states a 7-day trial, after which continued use requires a paid subscription. Teams that exhaust the trial evaluating fit and then need procurement approval face a gap.