Open original guide with interactive examples →
The short version A rep logs a result in LeadPerfection. Within 15 minutes (7 AM to 9 PM Central) we read the latest result on that lead, compare it with the rules you saved, and, if it matches and we haven’t acted on that call before, we either mark the contact Do Not Contact or pause their automation. Every call is acted on once.
The journey of one call result
Five steps happen between a rep clicking Save in LeadPerfection and your campaigns going quiet for that customer. You only do step 3 (once). Everything else is automatic.
- 1A rep logs a resultIn LeadPerfection, after a call. For example COMP, “Bought Comp”.
- 2We check for new activityEvery 15 minutes, 7 AM to 9 PM Central, every day.
- 3We read your rulesThe list you saved under Settings → Lead Perfection: Nothing, Do not contact, or Pause.
- 4Three checksIs there a rule? Is the call new enough? Have we already acted on it?
- 5The contact changesMarked Do Not Contact, or paused until a date. Recorded once.
When we check
Checks run on a fixed 15-minute rhythm, every day of the week. A result is normally acted on at the next check after the rep logs it, so the wait is at most about 15 minutes, plus the few minutes a check takes to run.
Evenings and overnight There are no checks between 9 PM and 7 AM Central. A result logged late at night is picked up at the 7 AM check. Your campaigns’ own quiet hours still apply to texts in the meantime.
Only the latest call counts
A lead can have many calls. We act on the most recent result only, so a “No Answer” from Monday never overrides a “Bought Comp” logged on Wednesday.
Mon · 9:12 AMNANo Answerolder, ignored
Tue · 1:40 PMLTMLeft Text Msgolder, ignored
Wed · 3:05 PMCOMPBought Complatest, counts
↓
Your rule for COMP Pause automation for 365 days
ExampleCodes and times are illustrative. Your own LeadPerfection codes appear in the rules table.
The three checks before anything happens
A matching result is not enough on its own. Each result passes three gates. Fail any one and the contact is left exactly as it was.
1Do your rules say something for this code?
No The code is set to Nothing (the default). Nothing happens.
2Was the call logged after you last saved your rules?
No Older calls are not acted on automatically. Use Preview and Apply to include them.
3Have we already acted on this exact call?
Yes It is skipped. A call is never applied twice, however many times it is checked.
All three pass The rule runs.
Do not contactLead status becomes DNC, text and email opt-ins are turned off, the conversation is closed, running automation is cancelled, and it is added to your do-not-contact log.
Pause automationRunning text sequences and flows are cancelled, and most automated texts are held until the end date. A banner on the conversation shows the date.
How the pause date is worked out
The pause counts from the day the call was logged, not from the day we noticed it, and it ends at midnight in the contact’s own time zone.
Call loggedTue, Nov 3Result: NI, rule says Pause 30 days
+ 30 days
Pause endsThu, Dec 3 · 12:00 AMIn the contact’s time zone
+ 1 day
Outreach hold untilFri, Dec 4Only if that option is on
ExampleThe Outreach hold until date is the day after the pause ends, so a date trigger on it can restart follow-ups on the first day texts are allowed again.
What “Contacts with code” means
In the rules table, the Contacts with code column tells you how many of your contacts currently have that code as their latest result. It is the same number Preview uses, so what you see here is what Preview would act on.
CodeLP descriptionContacts with codeAction
APAppointment_120_Nothing
NANo Answer (3days)_105_Nothing
COMPBought Comp (1yr)_4_Pause automation · 365 days
- If a lead’s latest call changes from one code to another, it moves to the new code’s count.
- The number is not how many times a code was ever used. It is how many contacts sit on it today.
- Codes set to Nothing still show a count, so you can see what each code would affect before you choose an action.
Good to know
| What | What to expect |
|---|---|
| Pause is not a total stop | It stops text sequences and flows running now and holds most automated texts. It does not stop AI phone calls, emails sent by newer flows, or single scheduled sequence steps. Use Do not contact when a customer must never be called. |
| Results logged late at night | Picked up at the 7 AM Central check. |
| Results your own automations write back | Results written to LeadPerfection by your automations (Add Call History) are not seen by the 15-minute check. They apply when the contact is refreshed or by the longer background check. |
| Changing your rules | New rules apply to calls logged after you save them. Use Preview and Apply for older leads. |
| Undoing a pause | Click Resume on the contact. A resumed contact is not paused again for the same call. |
| Undoing Do not contact | Contact support. It is locked on purpose so a customer who asked not to be contacted is not re-enrolled by accident. |
Questions
Does anything happen before I save rules? No. Until you save rules the section is inert.
How fast is “automatic”? Normally within one 15-minute check after the rep logs the result, between 7 AM and 9 PM Central.
Which result counts if a lead has several calls? The latest one.
Can one call be acted on twice? No. Each call is acted on once.
Do I need to set a time zone? No. LeadPerfection call times are read in your workspace’s time zone, and each pause ends at midnight in the contact’s own.
How do I check a single contact right now? Use the refresh icon next to them on the Lead Perfection contacts page.
Where do I set the rules? Settings → Lead Perfection → When LeadPerfection records a call result. The full setup guide is Call Result Rules: client guide and SOP.
Channel Automation · Help · Last updated 2026-11-05. Questions? Ask your account manager, or open Help Docs inside the app.