TargetOS support

Bring us the problem. We’ll help find the signal.

Get help with installation, ICP discovery, record cards, workflows, qualification results, enrichment, or your TargetOS account.

Email support Try troubleshooting first

Contact

Tell us what happened

Email is the support channel for TargetOS. A concise reproduction gives us the fastest path to the underlying job, request, or configuration.

targetos@smokesignals.ai

Include these details when they are relevant

  • Your HubSpot account ID.
  • The contact, company, deal, workflow, or onboarding job you were using.
  • The approximate time of the issue and your timezone.
  • The expected result and what happened instead.
  • Any visible TargetOS request ID or exact error message.
  • A screenshot with private customer data removed when possible.
Never email a secret.

Do not send passwords, API keys, OAuth tokens, private app secrets, session cookies, or full CRM exports. We will never ask you to send a provider credential by email.

Common requests

Choose the closest topic

The details below help us start with the right context.

Installation and access

Include the HubSpot account ID, the installer’s permission level, and the exact page or consent step where access stopped.

Onboarding and models

Include the onboarding phase or model name, whether the job is running or failed, and the result you expected to review.

Workflow qualification

Include the workflow and contact IDs, enrollment time, research depth, action status, and latest TargetOS qualification timestamp.

Cards and properties

Include the object type, record ID, affected HubSpot team or view, and whether the TargetOS properties are present on the record.

Data and enrichment

Name the affected source and fields, but redact customer-sensitive values and never include the provider credential itself.

Usage and account

Include the HubSpot account ID, the usage period in question, and which lead, action, model, or refresh limit needs review.

Production issue

Is live qualification failing?

Use a clear subject line so the report is immediately distinguishable from a configuration question. Include one affected contact, the workflow action status, the time of failure, and any TargetOS request ID. Do not repeatedly re-enroll a large list while the cause is unknown.

Report a production issueReview workflow setup