AI and lead usage records

What you used.Different purposes, viewed separately.

Keep separate usage records for different purposes.

LDG-075Awaiting operational validation
See how to use it
Real crop of the AI-points and lead-points tabs in Lingdonggu membership center
AI and lead point categories· Real system screenshot

Only the two point-type entry points remain, without balances, actual transactions, or order IDs. No points spent or purchased and no specific entitlement confirmed. Check usage conditions in the actual account.

AI usage with records.
Lead usage with balance checks.

Keep separate usage records for different purposes.

This feature's focus2

point-usage record categories

Source: AI and lead record directories. Official dual-wallet migration, settlement, and entitlements still require operational acceptance.

See this feature's highlights.

real work.
Details worth exploring.

Lead usage with balance checks.

Review today’s contact, email, and tool usage overview for the account.

See the actual steps

Confirm actual entitlements against published rules.

Check remaining entitlements against actual published rules.

See how to check

Understand the tool and human handling separately

What the tool handles.
What you decide.

Feature assistance

AI usage with records.

Keep separate usage records for different purposes.

Review today’s contact, email, and tool usage overview for the account.

Your review

3 key points.
After confirmation, continue.

  1. Do not combine different purposes into a single balance.
  2. The overview should correspond to specific usage records.
  3. Formal dual-wallet migration, settlement and benefits still require operational acceptance.

This compares feature handling scopes. Scenarios explain the sequence, not measured efficiency or completed customer cases.

Explain the feature through real work

This time.
separately.

Suppose a lead view and an AI assistance task happen on the same day.

Hypothetical scenario · Feature explanation, not a customer case or completed AI result
Previous handling steps

Treat both as using the same type of credit.

With this feature

Check purposes and records separately, then review remaining-benefit rules.

When to use it

Prepare first.
Make this task specific.

To understand current usage, review AI and lead usage separately and compare them with the account overview.

01

Usage scope

the two credit balances and their corresponding records.

02

Daily context

contact, email sending and tool usage.

Complete steps

From the start.
To the next step.

View balances and records for 2 credit types: AI and leads. The account overview also shows today's contacts, emails and tool usage. Dual wallets are a candidate delivery; migration, settlement and entitlements still need validation.

01

View AI and lead point balances and usage records.

02

Review today’s contact, email, and tool usage overview for the account.

03

Check remaining entitlements against actual published rules.

Connect the work from step to step

Make this step clear.
Connect the next step.

For questions, investigate using the event time and actual task context. Do not infer final settlement from a proposed delivery directory.

Return to Accounts and team workspace for the complete workflow

Understand before use

Bring the actual conditions.
Continue this step of the work.

Dual wallets are a proposed delivery. Official migration, settlement, and entitlements still require operational acceptance.

Product facts and FAQsBack to the product feature directory

More details in this product

AI credit consumption and return records

Charges and returns have records, providing specific references for usage issues.

Explore this feature on its own