Platform

Infrastructure,
not another app.

Relia is a conversation layer your product builds on: typed objects, one channel contract, isolated tenants and interfaces where you'd want to swap providers.

TENANT / PROD · CHANNEL_CONNECTED · AI_CONFIDENCE 0.982

Platform architecture

One layer, end to end.

YOUR PRODUCTRELIA SDKIDENTITYSIGNED · VERIFIEDMESSAGING LAYERTHREADS · TICKETSAI ENGINEAI_CONFIDENCE 0.982HUMAN INBOXHUMAN_HANDOFFCHANNEL ROUTERROUTE / ORIGINWEBEMAILTELEGRAMWHATSAPPSEARCH + INTELLIGENCE

Opinionated where it matters. Replaceable where it doesn't.

Relia's core infrastructure is standalone. AI and channel providers sit behind interfaces — connect your own without changing the conversation architecture.

LLMs↕ interface
SMTP↕ interface
Telegram Bot API↕ interface
WhatsApp Business↕ interface
Your provider↕ interface

Data model

Conversations are objects, not rows in someone else's app.

Everything in Relia is an addressable object with an ID, an API and webhooks. Build on the same primitives the product itself runs on.

Tenanttnt_acme

namestring

keysApiKey[]

channelsChannel[]

membersAgent[]

Customerusr_01HQZ8

external_idstring

emailstring?

verifiedboolean

traitsjson

Conversationcnv_018493

customerCustomer

channelweb | email | tg | wa

statusopen | resolved | …

assigneeAgent?

Messagemsg_9f2e1a

conversationConversation

authorcustomer | agent | ai

bodyrichtext

sourcesKnowledgeDoc[]?

KnowledgeDocdoc_77b3

titlestring

bodymarkdown

embeddingvector

visibilitypublic | internal

Tickettkt_00412

conversationConversation

prioritylow | med | high

sla_duetimestamp

stateopen | waiting | done

Channel adapters

Four channels, one contract.

Every channel implements the same conversation contract. Your team and your integrations never care where a message physically came from.

CapabilityWebwidget.jsEmailSMTP / IMAPTelegramBot APIWhatsAppBusiness API
Threading
Reply routing
Attachments
Read receipts
Typing

Adapters sit behind interfaces — swap providers without touching the conversation layer.

One conversation layer

Every channel. One inbox.

Customers choose where they talk. Your team doesn't have to. Email, web chat, Telegram and WhatsApp land in the same inbox, threaded by sender and automatically routed back through the right channel.

WEBIs there a fee for instant payout…EMAILRE: Invoice #2201 — still unpaid?TELEGRAMbonus code not working??WHATSAPPHi! I need to change my numberRELIA INBOXTHREADED BY SENDEROne customer. One history.Any channel.REPLY → SAME CHANNELAgent reply ✓
Marcus replies

One customer. One history. Any channel.

Multi-tenant architecture

Your infrastructure stays yours.

Every Relia customer operates inside an isolated tenant with their own users, conversations, permissions and keys.

Relia platform

Tenant Aisolated
  • Customers
  • Agents
  • Knowledge
  • Conversations
  • API keys
  • Channels
Tenant Bisolated
  • Customers
  • Agents
  • Knowledge
  • Conversations
  • API keys
  • Channels
Tenant Cisolated
  • Customers
  • Agents
  • Knowledge
  • Conversations
  • API keys
  • Channels

Build on the conversation layer.

Every object on this page has an API. Start with the docs.

Start buildingRead the docs