Storm Service

The support side of the relationship, on the same records

After the deal is signed, the project delivered and the invoice paid, the relationship keeps going. Storm Service handles what happens next, on the same record as everything that came before it, and gives your customers a real place to bring their questions.

Licensed separately from Storm OS. The first beta group starts in September.

Where it fits

Support that already knows your customer

Storm Service runs on the same records as your deals, projects and invoices, so a ticket arrives with its whole history attached and whoever answers is already caught up. Add it when support becomes a real part of your day; it is licensed on its own, so you only pay for it when you need it.

  • A ticket lands with the deal, the project and the invoice behind it
  • Whoever answers sees what was sold, built and billed, without asking around
  • The same people and companies you already keep, with no second system to maintain
  • Want it early? The first beta group starts in September

The portal

A public face for your support, on an address you choose

Every Storm Service account gets a persistent customer-facing portal, and you choose part of its URL. Your customers open tickets, follow their status, and read your service library there, with embeddable forms for the places they already are. Custom domains and subdomains follow later.

  • A hosted portal your customers can actually visit
  • You pick part of the address; custom domains and subdomains come later
  • Embeddable ticket forms for your site and product
  • A service library your answers build over time

Phase 1 · September

Ticketing that knows who it is talking to

The first release covers the working core: tickets through the portal and embedded forms, routed to the right person, answered faster with pre-written replies, and measured on dashboards, with the relationship context on every ticket.

  • Portal-based ticketing
  • Embeddable ticket creation forms
  • Ticket routing
  • Analytics and dashboards
  • Pre-written replies
  • On-time context from the record behind the ticket

Phase 2 · November

The knowledge base starts answering first

November brings the self-serve layer: a knowledge base that learns from your answers, live conversation when a customer wants a person, and assistance that steps in before a ticket exists.

  • Intelligent knowledge base
  • Messaging and live chat
  • AI-powered proactive assist

Phase 3 · December

Automation, and an agent of its own

December closes the year with the automation layer: tickets born from email, workflows that route and respond on rules you set, and custom AI service agents that can chat, suggest replies, and answer on their own where you allow it.

  • Email-based ticket creation
  • Automations and workflows
  • Custom AI service agents: chat, suggested replies, and auto-response where you choose

Have a say

Tell us what your support flow needs

This page will fill with real screens as the product comes together. If you want a say in what it does first, or a place in the beta group, the contact form goes to a person who reads it.

  • It will carry a beta label while it is one
  • Beta customers shape the roadmap ahead of each phase