Lead strength

Lead strength is a label Ari puts on every contact: Very strong, Strong, Good, Weak or Very weak. It answers one question—how likely is this person to become a paying client—judging fit and warmth together. Nobody types it and nobody edits it. Ari fills it in from what is already on the contact and keeps it current as the relationship changes.

It is a normal field, so it sits in the Contacts table next to everything else, and filters, sorting, saved views and workflows work with it the same way they work with Status or Owner.

The five levels#

Every workspace starts with these descriptions, and an owner or admin can rewrite them in the words your team actually uses. Ari measures each contact against them, so they are the definition, not decoration.

• Very strong Asked for pricing or a proposal, a meeting happened or is booked, they can decide, and they replied within the last two weeks.
• Strong Real interest and a live conversation: replied recently and said what they want, but budget or the decision maker is not confirmed.
• Good Some interest with no clear next step: one exchange, or a meeting that has not landed yet.
• Weak Little interest, or no reply for weeks. The offer or the budget does not fit well.
• Very weak No engagement at all, the wrong contact, or they said no.

A contact Ari cannot judge yet reads Not enough info yet instead of being pushed to Very weak. Ari makes that call itself; it is not a rule about how many notes a record needs. A contact Ari has not reached yet reads Not rated yet.

Where you see it#

• The Contacts table. Lead strength is one of the columns you start with, between Status and Owner. Your column layout is your own, so if you had already changed it, add Lead strength with Add column at the end of the table, like any other field.
• The contact record. It appears in Record details and as a Highlights tile on Overview, and in the side panel when you choose Open preview from the list.
• The popup. Choose the label anywhere it appears and Ari shows the panel: the label, when Ari last checked, how sure it is (“Ari is 91% sure”), and a bar with a percentage for each of the five levels so you can see how close the call was. Not enough info yet shows only when Ari checked; Not rated yet has no popup.

There is no written reason and no Re-check button: rating happens in the background, on Ari’s own schedule. When Ari saves a new label, open screens update on their own. Deals do not have a Lead strength—it is about the person, not the deal.

What Ari reads#

Ari reads the contact as the whole team sees it, and nothing else:

• The contact’s fields — the built-in ones and your custom fields, including ones you add later. Attachment, Linked record, Lookup and Button fields are left out.
• How those fields changed — what moved, from what to what, and roughly when, such as a status that went from Lead to Qualified two weeks ago.
• Notes — the full text, newest first.
• Tasks — open ones and recently completed ones, with due dates and assignees.
• Meetings — titles, dates and who was invited, past and upcoming, found through the contact’s email address.
• Email subject lines — who wrote to whom, when, and the subject, found through the contact’s email address.
• Texts and calls — where Quo or Dialpad is connected: who texted or called and when, and how each call ended. Ari reads the wording of texts only on lines set to Everything, where the whole team can read them.

Ari never reads email bodies—Ariyel does not store them. A mailbox set to Participants and timestamps is left out entirely, its emails and meetings alike, and internal-only threads and protected or blocked-address rules hide messages from Ari exactly as they hide them from teammates. On a Quo or Dialpad line set to Just who and when, Ari sees that a text or call happened, never what was said, and numbers on a line’s blocklist are left out. It does not read files, and it does not read its own summaries. Deals are not part of the rating today: not the stage, and never the value.

This list is fixed. The What Ari may read switches under Summaries apply to summaries only.

Every part of that list is optional. No connected mailbox, no texting, no meetings, no custom fields: those parts are simply left out and the contact is rated on the rest. Missing information is normal, never an error. On a very busy record Ari reads the newest activity first, so the oldest items may fall outside what it reads.

When Ari checks#

• After something happens. A reply, a note, a text, a completed task or a field edit marks the contact, and Ari checks once things go quiet—about ten to fifteen minutes later—so a busy hour costs one check, not twenty.
• As things go quiet. Ari also re-checks on its own as recent activity ages, which is how a lead that stops replying slides down without anyone touching the record.
• When it first reaches your contacts. Every contact gets a first label. On a long list this takes a while, and contacts read Not rated yet until Ari reaches them.
• The night after you rewrite a level. Changing what a level means re-rates every contact overnight, starting at midnight UTC, at most once a night.
• After a change to what the team can see. A mailbox’s sharing, a Quo or Dialpad line’s visibility, a blocklist or a contact field’s name changing makes Ari look over the workspace again. Contacts whose information did not change are skipped.

A label only moves when the new level clearly leads, so a contact sitting between two levels does not flip back and forth every night. That is why a label can sit a few points behind another level’s bar in the popup.

If nothing Ari reads has changed since its last check, Ari skips the check: no lead check is used and the checked time stays as it was.

Filter, sort and save it in a view#

Lead strength behaves like a single-select field. Filter on it to pick out the five labels, sort by it to rank contacts from Very weak up to Very strong, and save the filter into a view—for example a Hot list view filtered to Very strong and Strong. A view keeps only its filter; sorting by strength is your own View settings choice and isn’t saved into the view. Contacts without a label match is empty; they come first when you sort from Very weak up, and last when you sort from Very strong down. See Filters and views.

A sequence’s exit criteria (When a contact matches these conditions) and contact reports can use it the same way—see Sequences and Reports.

The field is read-only everywhere. It cannot be typed into on the record or in the table, set through the API, or written by a workflow, and it cannot be used as a lookup source. Only Ari writes it.

Use it in a workflow#

Because it is a field, the Field value changed trigger works on it: when Lead strength becomes Very strong, create a task to call them, or add them to a sequence. The trigger fires on any change to the label, so add a Filter for the level you want right after it. You can also use the label inside a workflow’s text and conditions. Nothing extra has to be built—see Workflows.

One rule protects you from a mass mailing. Whether workflows run depends on why a label moved, not on how many labels moved at once:

Either way the label saves and the contact’s Activity feed records the change, with Ari as the one who made it.

Set up Lead strength#

Lead strength is on in every workspace, with no switch to turn it off: the column is on Contacts, and every contact reads Not rated yet until Ari reaches it. To manage it, an owner or admin opens the company-name menu, then Workspace settings, then Ari → Lead strength:

1. Read The five levels and edit any description that does not match how your team talks. Describe situations, not degrees—“replied this week and asked for pricing” beats “very interested”. Each description takes 1 to 2,000 characters.
2. Choose Save descriptions. The page confirms Saved. Contacts will be updated overnight.

Each save re-rates every contact that night and uses one lead check per contact, so settle the wording in one go.

If This month shows Usage unavailable, choose Retry. Only an owner or admin can open this page; members are not offered Lead strength in Settings.

This month shows Credit allowance: the lead checks used against the workspace’s monthly allowance, such as 123 / 10,000 checks used, and the date it resets (UTC). The allowance is 10,000 by default. Every check Ari runs uses one, including each contact’s first label and each overnight re-rating; a check skipped because nothing changed is free. Those checks are counted separately from Ari Credits: Summaries never spends them, and they never spend Ari Credits. If the month’s allowance runs out, checking pauses until the reset, every label stays exactly as it is, and nothing else changes. Contact Educo to raise the allowance; checking resumes as soon as it is raised.

What leaves your workspace#

To rate a contact, Ariyel writes out the parts listed above as plain text, together with your five level descriptions, and sends it to TypeSafe AI, the company behind the model that scores it. Ariyel keeps the label, the five percentages, how sure Ari was and when it checked—not a copy of the text it sent, and never anything the record does not already hold.

The privacy rules your workspace already has apply unchanged: a private mailbox stays private, what was said on a Quo or Dialpad line set to Just who and when is never read, and nothing outside your workspace is ever part of a rating.

If something looks off#

• No Lead strength column. You had already changed your own columns; add it with Add column.
• Everything says “Not rated yet”. Ari is working through the list; long lists take a while. If it stays that way, check that this month’s allowance is not used up.
• “Not enough info yet” that will not move. There is too little on the record to judge. Add the call note, log the reply, fill in the fields you know—Ari re-checks minutes after the record settles.
• A label looks wrong. Ari rates what the record says, so start with the record: something missing or out of date there explains most surprises. Fix it and the label follows. If several labels feel wrong in the same direction, rewrite the level descriptions instead.
• A label has not moved since a change. Checks wait for a quiet moment, a small shift is not enough to move a label, and checking pauses for the rest of the month if the allowance is used up. It also pauses on Ariyel’s side while the scoring service is unavailable. Existing labels stay readable throughout.
• “Settings changed” when you save descriptions. Someone else saved first, or your access changed. Copy any wording you want to keep, choose Reload saved descriptions, then make your edit again.
• The five levels don’t load. If the page shows an error such as Could not load descriptions. or Lead strength settings are unavailable. Check your workspace access. instead of the levels, choose Reload saved descriptions.