Early-access support

A human path through setup, exceptions, and disconnects.

TerritoryLogic now accepts self-service HubSpot installs while keeping live owner writes separately gated per portal. Support covers OAuth setup, company sync, workspace roles, billing availability questions, map behavior, simulation/publication evidence, guarded rollback, privacy requests, and uninstall.

Email supportRead the setup guide

support@territorylogic.com

01 / A useful support request

Give us context without sending customer data.

A small amount of operational detail is enough to begin diagnosis safely.

Include these details

  • Your HubSpot portal ID and the affected TerritoryLogic screen
  • The approximate time of the problem, including your time zone
  • The correlation or request ID shown by TerritoryLogic, when available
  • What you expected and the last safe action you completed

Never send these

  • OAuth authorization codes, access tokens, refresh tokens, or client secrets
  • Raw contact data, exported CRM records, or complete customer addresses
  • Passwords, payment details, or screenshots containing unrelated customer data
02 / Escalate immediately

Tell us quickly when safety or access is in question.

Put “Urgent” and the portal ID in the subject line for these conditions.

Privacy or uninstall

You need customer-derived beta data deleted or cannot complete a controlled disconnect.

Unexpected CRM change

A HubSpot owner changed without an explicitly confirmed publication, or a published result does not match its activity evidence. Preserve timestamps, pause the program, and stop testing.

Repeated authentication failure

OAuth, signed HubSpot launch, or console access continues to fail after one clean retry.

03 / Controlled uninstall

Disconnect in a sequence we can verify.

Uninstall stops TerritoryLogic but does not automatically undo prior assignments. Preview and complete any desired guarded rollback before disconnecting.

  1. 1
    Preview any desired rollback

    Restore only TerritoryLogic writes that still pass the guarded rollback check before disconnecting.

  2. 2
    Stop active testing

    Do not start another sync, simulation, publication, or rollback while removing the app.

  3. 3
    Remove TerritoryLogic in HubSpot

    Use HubSpot's connected-app settings. Do not send screenshots containing tokens or customer records.

  4. 4
    Request help if needed

    Email the portal ID and removal time if you want human confirmation that jobs stopped and the purge path started.

Uninstall never rewrites ownership.

HubSpot keeps whatever owner values are present at removal time. If TerritoryLogic made assignments that should be restored, use the guarded rollback preview before uninstall.

04 / Self-service resources

Use the guide that matches the problem.

These pages describe the controls and limits in the deployed early-access product.

Install and first syncConnect the right portal and run a small read-only test.TroubleshootingResolve sign-in, sync, ZIP, stale-draft, and authorization states.Uninstall and deletionPrepare rollback, remove the app, and understand the purge.Early-access statusSee what is available, restricted, disabled, or incomplete.
Need a hand?

Start with one safe email.

Send the portal ID and a concise description to the operational support mailbox below. The best-effort response target is one business day during early access. Application-generated notification emails are not yet enabled.

support@territorylogic.comCompose email