Coming soon
Plumbing
Convert urgent calls into identified work, coordinate technicians, and keep customers informed throughout.
Urgent call → Triage → Dispatch → Repair → Follow-up
Industry Solutions
One governed operating system, adapted to how service businesses actually work.
Runory connects omnichannel intake, CRM, Sales, and FSM into one operating loop, then adapts through industry configuration instead of rebuilding the product for every vertical.
Conversations become business workExternal Super Agents can operate safelyOne shared customer and work context
Industry starting points
Begin with a mature scenario. Expand into a complete operating system.
Explore solution
Home Services
Unify customer intake, quoting, scheduling, dispatch, field work, payment, and after-service follow-up.
Call → Customer → Opportunity → Visit → Completion
Explore solutionExplore solution
HVAC
Support reactive calls, equipment records, maintenance plans, recurring visits, and technician scheduling.
Request → Asset → Work order → Technician → Service history
Explore solutionExplore solution
Waterproofing & Repair
Manage inspection, proposal, quote, project execution, evidence, change, completion, and after-sales.
Lead → Inspection → Quote → Project → Acceptance
Explore solutionComing soon
Installation Services
Coordinate longer-running jobs, milestones, field teams, documents, staged payments, and handover.
Opportunity → Contract → Milestones → Field work → Handover
Why Runory
Not another FSM interface. An operating runtime for the Agent era.
Omnichannel intake
Phone, AI voice, SMS, web, and manual entry become structured customers, leads, and work.
One operating loop
CRM, Sales, scheduling, field execution, payment, and follow-up share the same business context.
External Super Agents
Codex, ChatGPT, Claude, Cursor, Trae, or enterprise Agents can operate through MCP, Skills, or SDK.
Governed execution
Permissions, validation, confirmation, idempotency, audit, and human handoff bring Agents into real operations.
Real operating scenarios
Different services. The same connected, controlled operating discipline.
Emergency repair
1Customer calls
2Identity and urgency captured
3Work created and technician matched
4Service completed and customer updated
Inspection & quote
1Site visit scheduled
2Evidence recorded
3Proposal generated and approved
4Signed work enters project execution
Recurring service
1Maintenance plan becomes due
2Service visit created
3Customer confirms timing
4Asset and service history updated
Shared business model
Industries differ. The core operating objects stay consistent.
Customers, service locations, assets, opportunities, quotes, work orders, visits, projects, payments, and service history run in one governed business model.
Customers & locations
Opportunities & quotes
Work orders & projects
Scheduling & field tasks
Payments & after-sales
Audit & operational analytics
Start with one high-value workflow.
Mature scenarios can often become a working pilot loop in 1–2 weeks.