> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sender identity onboarding map

> Route your sender by identity class — person, org brand, or campaign draft — to the exact registration sequence (KYC, 10DLC, Sender-ID pre-registration, toll-free verification) and know when your set is complete enough to send.

# Sender identity onboarding map

Every outbound identity on Orbit passes through a registration sequence
before carriers and registries treat its traffic as known. The sequence
depends on what the sender **is**, not on anything Orbit screens for: a
sole-proprietor person files differently from an organization brand, and a
campaign that is still a draft files differently from both. This page routes
you to the right sequence and tells you when the set is complete enough to
walk the outbound pre-flight gates.

Use the table to place your sender in one row, then read only that row's
section below — the owning guides carry the step detail on purpose, so this
map stays a router, not a copy of them.

| Identity class           | You are…                                | Required registrations (in order)                                                       | Owning guides                                                                                                                                                                      |
| ------------------------ | --------------------------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Person (sole proprietor) | one individual, usually with one number | Sole-proprietor TCR brand → 10DLC campaign → number assignment                          | [10DLC wizard](/guides/10dlc-wizard), [10DLC registration](/guides/10dlc-registration)                                                                                             |
| Org brand                | a business entity (KYC/KYB-able)        | Organization KYC → compliance profile → Sender-ID country check                         | [Organization KYC](/guides/organization-kyc-onboarding), [Compliance profiles](/guides/compliance-profiles-assemble), [Sender-ID country matrix](/guides/sender-id-country-matrix) |
| Campaign draft           | a use case or template not yet filed    | Market filing (10DLC campaign, DLT template) and/or TFV when the number is US toll-free | [10DLC registration](/guides/10dlc-registration), [Toll-free verification](/guides/toll-free-verification)                                                                         |

## 1. Decision card — which class is your sender?

Answer three questions in order; the first one that resolves picks your row.

1. **Are you one person?** A sole proprietor, or a founder sending under
   their own name, follows the **person** path — TCR brands a sole-
   proprietor brand on a personal identifier instead of a company
   registration. If you can produce a business registration (tax number,
   corporate filing), you are an **org brand** even with a single number.
2. **Is the registry asking about a brand or about a campaign?**
   Registrations land on a brand entity once; campaign drafts then attach to
   that approved brand. If you already have an approved brand and you are
   preparing a new use case or template, you are working a **campaign
   draft**, not on-ramping from zero.
3. **Does the destination market file content, not identity?** Regulated
   markets (US 10DLC use-case categories, India DLT templates) register the
   message itself. If a market check — not a new identity — is what stands
   between you and launch, treat the sender as a **campaign draft** and file
   the content.

When the answers conflict (a person inside an org, a campaign that doubles
as brand onboarding), pick the row whose **first** registration you have not
completed yet — the class is decided by the earliest outstanding filing.

## 2. Person path — sole proprietors and single-number senders

TCR supports a sole-proprietor brand registered on a personal identifier,
and the [10DLC wizard](/guides/10dlc-wizard) walks that brand end to end
with save-and-resume drafts, OTP verification of the proprietor's phone,
and an atomic submit. (If you send as a business, skip to the org path —
sole-proprietor brands are capped at low throughput deliberately.) Once the
brand approves, file the [10DLC campaign](/guides/10dlc-registration) —
the use-case declaration that carries throughput — and assign numbers into
it; unassigned numbers send at unregistered-10DLC rates. The
[10DLC rejections and re-vetting](/guides/10dlc-rejections-and-revet)
guide covers verdict handling if the vet comes back rejected.

## 3. Org brand path — businesses and multi-market senders

Start with [organization KYC/KYB](/guides/organization-kyc-onboarding) —
submit the business registration, optionally add hosted ID verification for
signing members, and poll the status endpoint until the org is approved.
Regulated channels then reuse that verified packet as a **compliance
profile** instead of re-uploading documents per registration; the
[compliance profiles](/guides/compliance-profiles-assemble) guide shows
which profile shape each surface (RCS, WhatsApp, alphabetic Sender ID)
opens with. For alphabetic Sender IDs specifically, run the
[Sender-ID country matrix](/guides/sender-id-country-matrix) before you
choose launch markets: it separates markets that force pre-registration
(file before your first send) from markets where a dynamic sender works
outright — the lead time differs by weeks.

## 4. Campaign-draft path — filing content, not identity

A paused campaign stays incomplete until the campaign object itself is
filed with the market's registry. In the US that is a 10DLC campaign
declaration; in India it is a DLT template; both follow the same draft →
preflight → submit loop as the [10DLC registration
guide](/guides/10dlc-registration) describes for TCR. When the campaign
targets US toll-free numbers, add [toll-free verification
(TFV)](/guides/toll-free-verification) on top of the brand and campaign
filings — the TFV guide lints sample content before you submit the carrier
form, which removes the most common rejections. Either filing alone leaves
the draft incomplete in a regulated market; check the destination's rules
on the [country requirements](/compliance/country-requirements) before you
assume one registration covers all traffic classes.

## 5. Ready-to-send pivot — the final gate

Registration completeness is a carrier/registry question; the **send
gates** — wallet posture, opt-out sync, quiet hours, frequency caps — are
yours to walk afterward, and most of them are tenant-owned controls you
configure, not platform defaults. Run the [pre-flight
checklist](/guides/send-gates-preflight-checklist) once your registration
row above reads complete: it is the final admission check for every
outbound blast, voice broadcast, or API send, for senders of every class.