​
What You’ll Find Here

Platform Architecture

Understand how OneLink is evolving from its upstream base into a shared platform with isolated domain zones

Domain Profiles

Explore how generic, healthcare, and construction profiles fit into the shared platform

API Reference

Explore the APIs that power accounts, agents, conversations, contacts, and integrations

Platform Overview

See the current shape of the platform, its layers, and the direction of the OneLink fork

​
Getting Started Paths

Choose your path based on what you want to accomplish: Start with the Platform Overview and Current Architecture documents. They capture:
  • the current shape of the shared platform
  • the inherited account-scoped communication model
  • the planned split between shared platform logic and domain zones like healthcare and construction
  • the CRM and domain direction around shared entities and domain-specific behavior

​
I want to build integrations or extend APIs

Use the API Reference for:
  • application APIs
  • platform APIs
  • client APIs
  • integration-facing implementation patterns
OneLink is a product fork built on top of an existing omnichannel support platform. The goal is not only to rebrand the upstream product, but to evolve it into a shared platform that can support:
  • shared support and CRM capabilities
  • white-label branding and product-specific workflows
  • isolated domain zones such as healthcare and construction
  • controlled divergence from upstream while preserving the ability to receive upstream updates

​
Documentation Principles

This docs folder should increasingly reflect OneLink itself:
  • keep inherited operational docs where they still apply
  • add OneLink-specific architecture and product direction first
  • document where the fork intentionally diverges from upstream
  • prefer OneLink terminology and workflow over generic upstream wording for active development docs
Use the platform, domain, and API sections as the primary entry points in this interface.