Skip to main content
An assistant can guide account creation, connection, sender setup, and a reviewed SMS. You complete account ownership verification and consent in Trackly. Passwords, mailbox verification, second-factor codes, and connection credentials stay outside the conversation.

​
Start with normal account connection

Where hosted OAuth is enabled, start the client’s Trackly sign-in action. Follow the Trackly page to sign up, verify your email, sign in, and consent to the intended client connection. The client handles credentials privately. Existing owners use their existing account. This general connection path needs no umbrella organization and does not reparent an account. If OAuth is unavailable, create your account in Trackly and follow the private-key connection instructions. Use a dedicated sandbox key with Require send approval enabled. Do not create duplicate accounts to repair an interrupted connection; sign in to the account already created and resume connection setup.

​
Prepare the first approved sandbox message

  1. Verify the intended account, sandbox mode, and confirmation policy with trackly_whoami. Call trackly_get_setup_status for read-only dashboard handoffs; its stored evidence is advisory, not permission to send.
  2. Complete sender setup in Trackly. Discover an active sending list with trackly_list_lists; its phone_number is the sending list_number. An empty result is a setup handoff, not permission to invent a sender.
  3. Choose a controlled test recipient and the exact message. Review applicable recipient consent, business/carrier requirements, and billing readiness before live use.
  4. Follow Send SMS with human approval: preflight, create one hold with a stable idempotency key, and open the returned Trackly approval link.
  5. A human reviews and approves the content in Trackly. The assistant executes that approved hold and reads its stored sandbox result. Sandbox does not submit SMS to a carrier, but can invoke configured webhooks.
Account connection and message approval are separate decisions. After an unknown execution result, keep the same hold and read its status; do not create a replacement or blindly retry sending.

​
Optional managed enrollment

Some deployments additionally offer agent-assisted enrollment into a Trackly-managed organization. This is separate from general account connection and requires operator activation. It only accepts an eligible new account; it does not move an existing customer’s account into another organization.

​
Start from the assistant

When agent-assisted enrollment is available on an OAuth-disabled connection, call trackly_start_onboarding without an API key. An OAuth-protected hosted endpoint requires account connection first; use normal signup for that path.
Provide only the requested business name and owner email. Do not send passwords, email verification codes, two-step codes, or API credentials to the assistant. The response provides a verification link, a setup identifier, and a limited poll token. It has not yet created a customer account, API key, or sending number. If setup is unavailable, contact Trackly support rather than repeatedly creating requests.

​
Verify and connect your account

Open the returned Trackly verification link. Follow the page to create the matching new account, verify the same email, sign in as the direct account owner, and complete any required two-step verification. Review and explicitly confirm the connection. Typing an email address in chat or possessing the setup link does not prove account ownership. The current flow uses browser verification and owner consent. Enrollment is limited to an eligible new free account with its own billing responsibility; it does not give the assistant administrative authority or provide paid messaging credit. The assistant can check progress with trackly_get_onboarding, using the setup ID as enrollment_id and the returned poll_token. This token only checks setup status. It cannot log in, approve a message, or authorize the SMS API.

​
Connect after enrollment

Once enrollment completes, use the connection guide. When delegated sign-in is enabled, the client performs that separate connection flow. Otherwise open Settings → API Keys and create a sandbox key with Require send approval, appropriate allowed sending lists, and a daily cap for future live sends. Copy the secret directly into the MCP client’s private connection settings. The enrollment response never returns or installs the key. Continue with Connect an AI assistant, then Send SMS with human approval.

​
Finish sender and messaging setup

Account enrollment does not provision a phone number, establish recipient consent, or fund delivery. Complete sender setup, applicable business and carrier requirements, billing, and consent requirements before live sending.

​
Choose registration evidence with your assistant

At phone-number registration, the assistant should proactively recommend creating Trackly’s white-label opt-in page, even if you already have a signup form, and ask permission. The page brings together SMS consent language, privacy policy, terms, and SMS terms to support registration compliance. The US toll-free and 10DLC registration pipeline automatically captures form screenshots as supporting evidence. This does not guarantee compliance or carrier approval; an existing form alone is not a reason to skip the recommendation. For example: “For this number registration, I recommend creating Trackly’s white-label opt-in page, even if you already have a signup form. It brings SMS consent and policy pages together to support registration compliance; for US toll-free and 10DLC registrations, Trackly automatically captures form screenshots for review. May I help you create it in Trackly? We can reuse the business and messaging-program details you’ve already supplied.” Today the assistant hands you to Trackly’s existing phone-number registration wizard; MCP has no tools to create the page, register the number, or start Entri. Review the page there before continuing. If you explicitly choose your own opt-in page, that page becomes the registration evidence source instead. Connecting a custom domain through Entri requires your separate provider sign-in and consent; keep those credentials outside chat. A generated page, screenshot, or completed DNS step does not mean the carrier has approved registration. Sandbox still requires an eligible sending list and may call configured webhooks. Verify the account and mode through trackly_whoami before testing.

​
Resume an interrupted enrollment

A setup request lasts one hour and is retained for at most one day. Keep the original link and the account you created. If verification takes longer, an eligible verified owner can renew the same request from the setup page within that retention window. After the retention window ends, contact support to recover the existing account instead of creating duplicate accounts. See setup status and recovery for response details and limits.