me
ta vi sion: The telecom platform for operators run by people and their agents /ˌmɛtəˈvɪʒən/nounwritten METAVSHN
- 1The system a telecom operator runs on: billing, provisioning and self-care on one customer record, open to the people who run it and to the agents working for them.“Ticinocom SA bills its customers on METAVSHN.”
- 2The best move available at each moment, and a clear direction for the next ones.“Fix the data model before buying the chatbot. That is the METAVSHN move.”
Origin From Most Efficient Tactics Available (META) and vision, written VSHN. Coined by telecom operators after more than 30 years of running networks.
Everyone on your team will work with an agent
ChatGPT, Copilot, Claude, or whichever one your IT approves. Your people will ask it to find a customer, explain a missing discount or prepare a plan change. It can only answer from the systems it can reach.
The METAVSHN CLI, in early access now, gives that agent a set of commands for METAVSHN. Your people stay responsible. Their agents do the legwork.
- AskIn plain words, in the tool your team already uses.
- Look upThe agent runs METAVSHN commands. Access is checked on every request.
- ConfirmAnything that changes data or sends something out waits for a person to say yes.
Customer A has a referral relationship from the billing cycle to the referred product. That alone doesn't confirm the discount applies. The next check is product eligibility. These records don't show it, so I won't guess.
The September invoice for Customer A is ready to email. Sending needs your confirmation.
Sent. METAVSHN checked your access before sending.
The interface is not the moat
Soon everyone at a telco works with an agent such as ChatGPT, Copilot or Claude. It builds the view you need when you need it. What it cannot build is the data underneath.
What stops mattering
- Polished demo dashboards
- Screens nobody adapts
- Reports assembled by hand every month
What decides
- Clean customer, contract and product data
- How that data is connected
- How reliably each process runs
One record per customer
Customers, contracts, products, services and invoices live in one model, with every relationship defined. Your team works on that model today, and an agent reads from it when it answers a question.
Customer signs Contract includes Product runs as Service billed on Invoice
- CustomerA person or company. One party can be payer, user and reseller at once.
- ContractTerms, billing cycle and the products it covers.
- ProductA catalogue entry with its price, tax and provisioning step.
- ServiceWhat runs on the network, with its state and policies.
- InvoiceBuilt from contract and usage, and dunned if it stays unpaid.
Built on the TM Forum SID data model, with N:N party roles.
Where your team works on it
Invoices go out without anyone building them
Invoices, payments, taxes and reminders run from your catalogue prices on a fixed cycle. Your team reviews exceptions instead of building each invoice.
- Customer portalCustomers change plans, view invoices and open tickets themselves.
- Hosted checkoutCustomers order online under your brand, on desktop or phone.
- Integration hubTyped connectors to third-party systems, with webhooks for domain events.
- Enterprise suiteRoles and permissions, an audit log of every action, and hosting in Switzerland.
The copy-paste cost
The hours your team spends retyping orders, invoices and plan changes between tools. It usually shows up in three places.
- Too much manual work to run
- Billing, reminders, provisioning and customer self-care work from one customer record, so nobody copies data between them.
- How billing runs
- Too slow to change an offer
- A new plan, bundle or add-on is a new entry in the product catalogue with its price and provisioning step, not a project.
- See the catalogue
- Too risky to leave the old system
- We map your systems with you, plan the move together and transfer customers in batches.
- How a move works
Under 2 weeks
from kickoff to the first NordVPN activation for a Ticinocom customer
Source: Ticinocom and NordVPN case study
We run our own ISP on METAVSHN
Ticinocom SA, the internet, TV and mobile provider behind ticino.com, is run by the METAVSHN team. It bills, provisions and serves its customers on the same platform you get.
We waited on purpose
We could have added a chatbot years ago. We spent that time on what an agent actually needs: one record per customer, products with their rules, processes that run the same way every time.
- 30+ years in telecom
- We have billed, provisioned and supported telecom customers for three decades, and we run our own ISP today.
- Mapped data and processes
- Customers, contracts, products, services and invoices sit in one model with their relationships defined, so an agent gets context instead of raw tables.
- Interfaces for people and agents
- A web platform for your team, and the METAVSHN CLI for the agent your company already approved. More interfaces follow.
Which one are you?
Pick your type of operator to see what your day looks like on METAVSHN.
Talk to the people who run an ISP on it
In 30 minutes we go through how you bill, provision and support customers today, and show you where METAVSHN fits.