Shared inbox, tickets, queues, tags, and ownership
Every channel feeds one shared inbox, so no request sits unowned in someone's personal folder.
Runlium Support
Give service teams context from sales, projects, billing, and product activity without exposing information they should not see.
Core capabilities
Omnichannel tickets, service levels, knowledge, customer health, and success plans.
Every channel feeds one shared inbox, so no request sits unowned in someone's personal folder.
Service-level targets and escalation rules apply automatically based on the account and issue type.
Company knowledge is kept in one place for agents and Ask Runlium. Drafting replies from it is planned.
Planned: support and usage signals combined into one customer health score.
Backlog, SLA and resolution figures are visible on the Support dashboard. Satisfaction (CSAT) surveys are planned.
Customers submit and track requests through a portal instead of a shared email alias.
Connected workflows
Each workflow is modeled as visible steps, typed events, clear ownership, approval rules, retries, and recoverable execution.
Classify and route a request using customer tier and issue type.
Escalate a breached service level with the full customer context.
Create a success task when product usage drops below a threshold.
AI in context
The AI experience is designed to retrieve only permitted context, expose evidence for important answers, and separate recommendations from approved execution.
Summarize this customer issue and prior attempts to resolve it.
Draft a response grounded in the approved knowledge base.
Which accounts show both support and renewal risk?
Works with
Records, permissions, and events are common across the platform, so each module adds context to the others instead of copying it.
Documents, decisions, policies, procedures, wikis, templates, and governed knowledge.
Event-driven workflows, approvals, agents, schedules, integrations, and execution history.
A permission-aware assistant that understands every connected business record.
New to the category? Read what an AI business operating system is, or see how the modules share one platform architecture and workspace-based pricing.
Founding design partner
Use cases from founding teams will define the first workflows, integrations, fields, and migration tools.