Last verified: 2026-05-19
TSP partner communication (SaaS2 ↔ launch)
SaaS2 is the product (orders, storefronts, payouts to merchants). Territory Services Provider (TSP) partners handle in-country rails (PSP, 3PL, MoR) per contract. This page is for anyone writing partner-facing copy that mentions TSP near SaaS2 launches.
Full TSP onboarding lives in CRM (apps/crm2/docs/kb/). Use the same a, not the rule here.
Say a, not the
| Use | Avoid |
|---|---|
| A Territory Services Provider for [city] | The Territory Services Provider for [country] |
| Rails scoped to Exhibit X | “You own the territory” / “You run Bumi in [region]” |
Why: The sounds like one exclusive regional operator. A sounds like one contracted provider type.
SaaS2 context (stay narrow)
When email or docs mention SaaS2 + TSP together:
- TSP enables order-rail pay-in and delivery contracts per counsel — not merchant POS training, not field sales hiring.
- Do not describe MAS, MDM, FCO, COR, or field org names in TSP-facing SaaS2 notes.
- Product issues on storefronts → platform owner; settlement / PSP → a TSP per exhibit.
Copy-paste (Product Co → partner)
We’re onboarding a Territory Services Provider for [city] to stand up PSP and 3PL rails for direct ordering. Your deliverables are listed in Exhibit [X]. SaaS2 product access for merchants is separate from your scope.
CRM documentation
Partners with CRM login should read (on the CRM /docs site):
- TSP — your docs (
field/tsp-your-docs) - How to refer to a TSP (
shared/tsp-communication-guide) - TSP scope — contract boundaries (
shared/tsp-partner-boundaries)
Verified against
apps/crm2/docs/kb/shared/tsp-communication-guide.mdapps/saas2/docs/COMMISSION_BILLING_PERFORMANCE_REBATE_LOGIC.md(two-rail context)
