Profiles and versions
A scoring profile is the complete description of a good lead for one business, or one line of business: what to extract, which criteria give how many points, the tiers, and what counts as junk. It's the only source of a lead's score — Leadveyor has no hidden opinion of its own.
What a profile contains
| Part | What it says |
|---|---|
| Description | A few sentences on the business and its best customers, read with every message |
| Fields | What to extract beyond contact details: event date, guests, budget… with types |
| Criteria | Scored, rule, exceptional and disqualify criteria, with answers and points |
| Scoring | How answers combine (points by default) and the tiers |
| Dimensions | Groups for the breakdown (Who / What / When…) |
| Junk rules | Extra rules in plain words, always-junk and never-junk domains |
A profile is one JSON document; the console edits it with forms, and the API accepts it as is. Profiles work for any business and any language — the same engine scores a caterer, a law firm in Spanish, or a B2B software company qualifying by budget and timeline.
Criteria in plain words
You don't need to write rules or prompts. Describe a criterion as you'd explain it to a new employee — "Bigger events are better: more than 200 guests +25, 100–200 +15, fewer than 100 +5" — and AI drafts the question, the instructions for reading messages and the answers with points. You review and adjust before anything is used.
Drafts, versions, rollback
The diagram shows three published versions: v1 scored leads 101 and 102, v2 scored leads 103 to 105, v3 is active and scored lead 106; a draft below is being edited and is used for nothing until it is published.
- Draft — changes are made in a draft, which scores nothing. It can be saved, reviewed, tested and discarded.
- Publish — turns the draft into a new, numbered version that is frozen forever and becomes active: every new message is scored with it.
- Every lead remembers its version. Publishing never rescores existing leads silently; yesterday's scores stay as they were, explained by the version that produced them. To apply a new version to an older message, process it again on purpose.
- Rollback — making an older version active again is one click; nothing is lost.
Test without risk
The console's Test panel — and the API's POST /v1/evaluate — score any message with any profile, including an unsaved draft, and store nothing. The usual cycle: change criteria, test on a handful of real messages (a great lead, an average one, a poor one), adjust, publish.
One profile or several
Most businesses need one profile. Use several when lines of business judge leads differently — weddings and corporate events, residential and commercial jobs — and pick the profile per source. The workspace's default profile scores messages from sources that don't name one.