Accounts (Beta)

Accounts group contacts, visitors, conversations, and product activity by company or application tenant. Use them to understand engagement across all the people associated with the same organization.

How accounts are created

Aimdoc creates and links accounts automatically from:

• A contact's confirmed work-email domain
• Company data discovered through visitor enrichment
• An account or tenant identity sent by your application through the Aimdoc SDK

Personal email domains are not used to create domain-based accounts. For users with personal email addresses, send a stable account external_id through the SDK.

Account status

The Accounts table shows how Aimdoc knows each account:

• Confirmed — at least one contact with a work email at the account's domain has been observed
• Identified — your application supplied an account external ID, but a matching work-email domain has not been confirmed
• Enriched — the account is known from visitor enrichment only

An account's status does not change the provenance of each visitor. Anonymous visitors remain labeled Enriched until they are associated with an identified contact.

Browse accounts

Open Accounts from the main Aimdoc navigation. Search by name or domain, sort the list, and change the number of accounts shown per page.

The table summarizes:

• Account name and domain
• Identity status
• Contact and visitor counts
• Daily active users (DAU)
• DAU/MAU stickiness
• Most recent activity

Review an account

Select an account to see its company context and activity in one place:

• Industry, employee count, estimated revenue, and LinkedIn details when available
• Matched HubSpot or Salesforce account and owner
• DAU, MAU, stickiness, active people, and frequently viewed pages
• Linked contacts and enriched visitors
• Recent sessions
• Objective progress when your agents define journey goals

Aimdoc assembles company facts from the freshest linked contact and enrichment records. Accounts are behavioral records, so deleting a contact does not delete the account.

Activity metrics count Aimdoc conversations and in-app product browsing. Anonymous website browsing alone does not count toward DAU or MAU.

Objectives

When agents have published objectives, the account page shows progress for that company:

• Account-level objectives can be updated manually from the account page
• Person-level objectives summarize status across the account's contacts

Progress can also come from the agent during conversations or from signed SDK identify claims.

CRM account owners

When Salesforce or HubSpot is connected, Aimdoc can match an Aimdoc account to the corresponding CRM account by domain and surface the CRM account owner on the account detail page.

That match also personalizes notifications for your team:

• Email and Slack alerts for new visitors, new contacts, active sessions, escalations, and visitor identification can include the matched account and account owner
• If the CRM owner's email matches an Aimdoc user who has that notification enabled, the email subject and body call out that the visitor belongs to an account they own (for example, Your account Acme: New contact)
• Slack can @mention the matched owner when Slack can resolve their email
• Confirmed matches (work-email domain) are treated as trusted; enriched matches include a disclaimer that the association is a signal, not proof

For human escalations, each skill can define how the matched owner participates: assign an available owner directly, notify them as an FYI while another rep is assigned, or show their name as context without notifying them. An owner assigned directly can be outside the skill's rep pool. See Route human escalations.

For Salesforce, Aimdoc uses the agent's configured Account Match Field to find the CRM account by domain. Connect Salesforce under Integrations and configure Account matching in the agent Actions tab.

Account-owner personalization requires:

1. Salesforce or HubSpot connected for the organization
2. A domain Aimdoc can resolve (confirmed work email or enrichment company domain)
3. The CRM owner email matching an Aimdoc teammate with the relevant notification preference enabled

See Visitor Identification for how enrichment can trigger owner-aware visitor alerts, and Notifications for user-level preferences.

Identify app accounts

For App Mode on the Activate plan, include an account object when you call identify. The account external ID should be the stable ID for the customer, workspace, or tenant in your application.

Every identify call containing account data or objective claims must include a valid user_hash, even if organization-wide identity-verification enforcement is disabled. See Identity Verification.

See SDKs for the account payload and App Mode for Activate availability.

To pull accounts programmatically, use the External API (GET /api/v1/accounts) or the MCP Server (list_accounts, get_account, get_account_activity). Conversations, contacts, and visitor profiles accept an account_id filter on both surfaces.