Shared inbox, tickets, queues, tags, and ownership
Every channel feeds one shared inbox, so no request sits unowned in someone's personal folder.
Every request, one history
Runlium Support
Give service teams context from sales, projects, billing, and product activity without exposing information they should not see.
Su
RunliumSupport
LiveOperating focusResolve issues faster and make customer risk visible earlier.
01Shared inbox, tickets, queues, tags, and ownershipActive
02Service levels, escalation rules, and operating hoursConnected
03Knowledge base and internal response guidanceConnected
Core capabilities
Everything support teams need—connected to the rest of the business.
Omnichannel tickets, service levels, knowledge, customer health, and success plans.
Service levels, escalation rules, and operating hours
Service-level targets and escalation rules apply automatically based on the account and issue type.
Knowledge base and internal response guidance
Agents draft responses grounded in an approved knowledge base instead of writing every reply from scratch.
Customer health, success plans, and risk signals
Support and product-usage signals combine into one customer health score, visible before renewal.
CSAT, resolution, backlog, and quality reporting
Resolution time, backlog, and satisfaction scores are visible without a separate reporting tool.
Customer portal and request forms
Customers submit and track requests through a portal instead of a shared email alias.
Connected workflows
Move work across modules without losing context.
Each workflow is modeled as visible steps, typed events, clear ownership, approval rules, retries, and recoverable execution.
1
Classify and route a request using customer tier and issue type.
2
Escalate a breached service level with the full customer context.
3
Create a success task when product usage drops below a threshold.
AI in context
Useful answers begin with clear scope and trustworthy sources.
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?
Founding design partner
Would Runlium Support remove real operational friction for your team?
Use cases from founding teams will define the first workflows, integrations, fields, and migration tools.