Calling hours, attempt limits and do-not-call
The retry ladder that turns persistence into policy, plus the calling hours and DND block.
只有你点击播放时，播放器才会从 YouTube 加载。
Step by step
After this video you can write your calling rules once and let the app enforce them: when calls may go out, how many times a lead is tried, how long it rests between tries, and who must never be called.
- 1
Set calling hours and days
Settings → Calling policy. Set Calling starts, Calling ends and the calling days. A window can run past midnight for teams calling other time zones. An agent who dials outside these hours is warned; they can still call, and the call is flagged Outside hours in the lead’s call history.
- 2
Close holidays for calling
Dates marked closed in Settings → Working days & holidays block calling for the whole day, so a festival or a company holiday needs no reminder in a group chat.
- 3
Set the maximum attempts
Maximum attempts is the number of not-connected calls after which a lead leaves the queue. It then shows under Leads → Last call → Reached attempt limit for a manager to decide what happens next.
- 4
Build the retry ladder
Wait between attempts sets how long a lead is left alone after each unanswered call, one wait per attempt: After attempt 1, wait; then Add another wait for the next. Every attempt after the last one repeats the last wait.
- 5
What the wait blocks
Until the wait is over, LumaKol does not dial the lead. In the app, Call says from when it can be called, and the queue, auto-dial and Power Dialer move on to the next lead. Click-to-call from the web refuses it too.
- 6
Block leads who asked not to be called
Saving the outcome Requested no contact moves the lead to Lost. While Block calls to leads who asked not to be contacted is ticked, which it is by default, the lead is also marked Do not call and the apps refuse to dial it.
- 7
Mark Do not call by hand
Anyone who logs calls can mark a lead as Do not call from its page or in bulk from the leads list, with a reason. That blocks every call to it, and only owners, admins and team leads can remove the mark.
- 8
Decide on auto-dial
Allow auto-dial next lead lets agents move straight on to the next lead after a call. When it is off, every call starts with a tap, and Power Dialer is off too because it needs auto-dial.
Tips
- The calling hours check uses the clock on the agent’s phone, not the lead’s time zone, so set hours that suit the people being called.
- LumaKol does not check national do-not-call registries. Screen cold lists against the registry that applies to you before you import them.
Read the full guide
The written guide covers the same screens, with every setting explained, so you can follow along at your own pace.
- Calling policy and lead data protectionHours checked before the dial, attempt limits and retry delays; a Do not call mark and a “Requested no contact” outcome that block further calls; number masking, export rights and screenshot blocking for the data.
- Calling policy & DNDCalling hours, attempt limits and a no-contact block
More from 第二部分——日常运营
- 12Masked numbers, recordings and exports4:39
- 13Notes, reminders and voice memos3:15
- 14Lead capture forms4:25
- 15API keys and webhooks5:11
- 16Working calendar, shifts and attendance rules4:58
- 17Notifications, and the four you cannot mute3:51
- 18Build a morning call list with filters4:24
- 19Your profile, language and sessions3:49
- 20Follow-ups in Google, Apple or Outlook5:45
- 21Power Dialer: call a whole list from your phone1:42
- 22Power Dialer for teams: keep callers dialling1:44