Skip to main content
Once your topics are ready, Pulse Classifier assigns them to every response in your dataset. Classification runs as an asynchronous background job, so you can close the browser tab and return later. Before committing to a full run, use the preview classification to validate your topic plan on a small sample.

Preview classification

Preview classification runs the AI against a small subset of responses (typically 20–50 rows) so you can check whether the topics are being applied as expected before spending tokens on the full dataset.
1

Confirm your topics

In the Topics editor, click Confirm topics (or the equivalent confirm button) once your code plan is ready.
2

Run a preview

Click Preview classification. The AI classifies the sample and shows results immediately in the codes view.
3

Review results

Scan the classified responses. If topics are being applied incorrectly — for example, too broadly or missing obvious matches — go back to the Topics editor and refine your labels or guidelines.
4

Proceed to full classification

When the preview looks correct, click Classify to launch the full job.
Preview classification is free — it does not count against your token balance. Only the full classification job consumes tokens.

Classification configuration

Before launching a full classification, you can adjust the following parameters in the configuration panel.

Depth

SettingBehavior
L1 onlyAssigns only top-level topics to each response. Faster and cheaper.
L1 + L2Assigns parent topics and their sub-topics. Use when you need granular sub-codes.

Tolerance

Tolerance controls how strictly the AI applies topic assignments, on a scale of 1–5.
  • Low tolerance (1–2): The AI only assigns a topic when it is confident. Fewer topics per response, lower false-positive rate.
  • High tolerance (4–5): The AI assigns topics more freely. More topics per response, but may include weaker matches.
The default tolerance is 2, which works well for most datasets.

Max codes per response

Set a hard limit on how many topics can be assigned to a single response. Set to 0 for no limit. For L1+L2 classification, you can set separate limits for L1 topics, L2 sub-topics per response, and L2 sub-topics per L1 parent.

Consensus settings

Pulse Classifier runs multiple AI passes per response and uses a voting mechanism to decide which topics to keep. This improves accuracy at the cost of additional token usage.
SettingDescriptionDefault
Consensus NNumber of classification passes per response batch.20
Consensus thresholdMinimum votes required to assign a topic.17 out of 20
L1 min votesMinimum votes to keep a parent L1 topic.2
Higher consensus settings improve accuracy but increase token consumption roughly proportionally to the number of passes. For large datasets, consider reducing consensus N if token cost is a concern.

Running the full classification

Click Classify to launch the full classification job. Pulse Classifier submits the job to the background queue and shows a progress indicator in the classification drawer. The drawer displays:
  • Status — Pending, processing, or complete.
  • Progress bar — Percentage of responses classified.
  • Estimated time remaining — Updates as the job progresses.
You can navigate away from the page. The job continues in the background and appears in your Classification history when complete.

Token consumption

Token usage depends on the number of responses, the classification depth, and the consensus N setting. As a rough guide:
  • L1-only classification with default consensus uses approximately 1× the response count in API calls.
  • L1+L2 classification doubles the number of calls.
  • Increasing consensus N multiplies token usage proportionally.
Your current token balance is shown in the account menu. You can top up tokens from the billing page.

Manual corrections

After classification completes, you can correct individual topic assignments directly in the results view.
1

Open the codes view

Click on a classified response row to expand it.
2

Add or remove a topic

Use the topic dropdown on the response row to add a topic, or click the × on an existing topic badge to remove it.
3

Save changes

Changes save automatically. Corrected assignments are reflected immediately in the topic counts.

Resuming interrupted classifications

If a classification job is interrupted — for example, due to a network issue — it appears in your Classification history with a status of Failed or Pending. You can re-open the job from history and resume from where it stopped, or start a fresh classification run. Jobs that remain in a pending or processing state for more than 30–60 minutes are automatically marked as failed.