Today we are introducing tcxcDOCS, documentation that stays in sync with the platform it describes. It is the engine behind the TelecomsXchange Help Center, and from today tcxcONE operators can run it for their own buyers, sellers and developers, under their own brand.
The problem with documentation
Every platform team knows the pattern. The knowledge base was written at launch. The API reference lives in a separate tool. The screenshots were taken by whoever had time that week. Then the platform changes, as it does every week, and all three drift. Customers open tickets about things the docs describe wrongly, and the support team answers questions the docs should have answered.
The usual fix is a person whose job is to chase the product. It never keeps up, because documentation is updated after the fact, by hand, in four places.
What tcxcDOCS does instead
tcxcDOCS reads the platform's source code and builds the documentation from it. When a commit lands, each changed file is traced to the guides, API pages and screens that document it. Those are the only pages that change:
- Guides are rewritten against the new code. Each guide opens with a short answer, then numbered steps a reader can tick off, a diagram of the flow, troubleshooting tables and common questions.
- The API reference regenerates from the API's routes and handlers: parameters, errors, an example response and a ready request in cURL, Python and PHP for every endpoint, plus an OpenAPI file.
- Screenshots are rendered from the portal's own templates with fictional sample data, so they match the build exactly and never contain customer data.
- Everything is checked on phone and desktop, in light and dark mode, for broken links and layout faults. Only a clean build publishes, and every page shows the date it was last checked against the platform.
The TelecomsXchange Help Center is the first deployment: 57 guides for buyers and sellers, 28 integration guides for SIP and SMPP platforms, and an API reference of 67 endpoints, all built this way.
Tests and certificates
Each audience gets a test built from its guides. A reader who passes receives a certificate with a credential ID that can be added to their LinkedIn profile in one click, shared, printed or downloaded as an image. Your partners' staff become certified on your platform, and you can see who has done the reading.
Found by Google, read by AI
More customers now ask an AI assistant before they open a ticket. Every page tcxcDOCS publishes is ready for both search engines and answer engines, with nothing to configure:
- structured data on every page: article, breadcrumb, FAQ and organisation markup, generated from the content
- a sitemap where every URL carries its real last modified date
- search length titles and descriptions, canonical links and a share image per page
- llms.txt, per section full text files and a Markdown copy of every page for AI crawlers
- an Ask AI button on every guide that opens it in ChatGPT, Claude or Perplexity with the guide already loaded
Your brand is a settings file
Logo, colours, typeface, favicon, share card, domain and support address are settings, not a redesign. Change a few lines and every page, share card and certificate follows. The TelecomsXchange Help Center and a second operator's help center run on the same engine today with different brands, in light and dark mode.
Who it is for
tcxcDOCS is available to operators running their wholesale exchange on tcxcONE. We set it up on your platform, in your brand, on your domain, and it keeps itself current from there.
Book a tcxcDOCS demo →
Or see it live at help.telecomsxchange.com.
