TSG GLOBAL/Developers
Campaign Manager Sandbox

Managed onboarding

Connect authorized customer accounts and understand the prerequisites for managed reseller registration.

Sandbox environment

Brand and campaign submissions are simulated. Nothing reaches The Campaign Registry and no carrier charges are incurred. Use credentials issued for this environment.

TNID authorization

TNID account sign-in is separate from the representative’s TCR SMS YES verification; neither replaces the other. The customer signs in interactively at Connect TNID with a one-time code and explicitly authorizes this customer account. Campaign Manager verifies the TNID user and company administrator relationship. Access and refresh tokens are encrypted on the server; they are never returned in browser pages, REST or MCP responses, or placed in links or browser storage. GET /tnid/connection and MCP get_tnid_connection return connection status only. Disconnect removes the stored connection. This does not revoke tokens held elsewhere or prove that profile sharing/publication is complete.

Brand pages show saved details directly, including incomplete registrations. Campaign detail and list responses return brand_ref, tcr_brand_id and tcr_campaign_id together; unresolved IDs remain null. Both REST and MCP use the same service and schema.

Managed sole proprietor / Mary Kay workflow

Wide Voice sends the representative information to Campaign Manager using its company-scoped key. TSG handles the sole proprietor registry actions under TSG’s CSP, with the verified Wide Voice reseller attribution. A Campaign Manager key is distinct from a TCR key and from TNID user authorization.

  1. POST /intakes with channel: "10dlc_sp", an Idempotency-Key, and representative answers. For Mary Kay include business_family: "mary_kay", mary_kay_role: "consultant" or "director", entity_type: "SOLE_PROPRIETOR", actual contact/address/mobile details and the real Mary Kay page. answers.customer_reference preserves your WV/WDV identifier.
  2. Save missing answers with PATCH /intakes/{ref}. Review and confirm them with POST /intakes/{ref}/confirm. Each action uses the latest expected_revision and source_hash returned by the intake or workflow response.
  3. Create the TNID profile with POST /intakes/{ref}/tnid-profile only after TSG establishes the authorized customer user connection. Staff can instead connect an existing, verified representative scope through POST /intakes/{ref}/sole-proprietor/profile. Public profile, privacy, terms and subscription URLs must be real and sender-specific. An API key or an enabled endpoint does not establish the customer’s TNID user grant.
  4. POST /intakes/{ref}/sole-proprietor/brand prepares the local brand without sending SMS. Upload the current rendered consent screenshot to the interview’s documents. Staff verify identity, role, legal pages, the unchecked consent box, actual Hello/YES process and Wide Voice/TSG access with POST /intakes/{ref}/sole-proprietor/evidence.
  5. POST /intakes/{ref}/sole-proprietor/mobile registers the brand and requests the representative’s SMS YES reply. Email verification is unsupported. Check with POST /intakes/{ref}/sole-proprietor/mobile/check; 409 means verification or another prerequisite is still pending. Use backoff.
  6. POST /intakes/{ref}/sole-proprietor/campaign prepares the documented campaign for staff review. Mary Kay retains SOLE_PROPRIETOR and all three sub-use cases: ACCOUNT_NOTIFICATION, CUSTOMER_CARE, MARKETING. Generic Low Volume Mixed defaults must not replace them.
  7. After current staff approval, an authorized TSG staff key may call POST /intakes/{ref}/sole-proprietor/submit with confirm_charges: true. When enabled, it registers the campaign, uploads and reads back the reviewed screenshot, then elects DCA1. Company keys cannot perform this staff action. A registry write can incur charges; an uncertain result stops for reconciliation.
  8. Poll GET /intakes/{ref}/sole-proprietor with backoff for IDs, progress and next action. These reads use the saved workflow; they do not send another OTP or submit a campaign.

The same actions appear in MCP tools/list, including create_intake, get_sole_proprietor_plan, prepare_sole_proprietor_brand, request_sole_proprietor_mobile, check_sole_proprietor_mobile and prepare_sole_proprietor_campaign. Use the discovered schemas rather than inventing arguments. Staff evidence and submission tools enforce staff authority independently of the transport.

JSON
{
  "data": {"workflow": {
    "intake_ref": "<CM interview ref>",
    "customer_reference": "WV-your-reference",
    "submission_reference": "WDV-<stable CM reference>",
    "brand_ref": "<CM brand ref>",
    "campaign_ref": "<CM campaign ref>",
    "tcr_brand_id": null,
    "tcr_campaign_id": null,
    "steps": [{"key": "otp", "state": "not_started"}],
    "next_action": "<current next action>",
    "revision": 1,
    "source_hash": "<current hash>"
  }}
}

This is an illustrative response, not a completed submission. TCR IDs remain null until actually registered. The stable WDV submission reference is used for the managed TCR brand and campaign reference IDs; your customer reference is preserved separately. A later SMS or attachment failure does not erase an already-created TCR ID. Read the existing workflow to recover it; do not create a replacement interview or brand to retry. reconcile_required needs staff resolution.

Live operation is gated by verified TNID user/profile access, published evidence, registry ownership, reseller configuration and staff approval. The provider email is a staff-only draft after confirmed election; no email is dispatched by this endpoint. DCA1 sharing, DCA2 progress, final deployment and number assignment are distinct. Progress reads are available; a partner callback delivery service is not implied.

Existing customer-owned TCR accounts

ClickBuzz’s current 10DLC workflow uses its own TCR accounts; toll-free intake uses TSG APIs. This is distinct from TSG-owned Wide Voice sole proprietor registration. Do not route ClickBuzz’s ordinary 10DLC records through the Wide Voice flow or infer that a Campaign Manager key selects one of ClickBuzz’s TCR accounts.

The first pilot is one or two brand/campaign packets: reuse existing business facts, message analysis and evidence; return a complete proposed submission for factual approval, plus exact website replacements only where an observed gap requires them. Clearly labelled working Terms and Privacy hyperlinks do not need their full URL printed beside them. Native toll-free form exports keep complete answers within the current 500-character output standard; this is not a universal claim about every carrier’s limit.

A future multi-TCR-account selector and optional derived toll-free application require explicit account authorization, number allocation, channel eligibility, current consent evidence and a separate review. A 10DLC approval or a TFN ready flag does not automatically authorize toll-free use or imply approval. These extensions are not implemented by the managed sole proprietor endpoints.