Configure the run time
For each seat, complete these steps:1
Select the representative
Choose the sales rep whose LinkedIn and email accounts will execute outreach.
2
Enable or disable the schedule
Toggle Schedule enabled on to run automatically, or leave it off to run only on demand via Run Now.
3
Choose active days
Select the days of the week the seat should run.
4
Set the start time
Pick the time of day the run begins.
5
Confirm the timezone
Verify the timezone matches the representative’s working location.
Set daily action limits
Limits are per seat and reset each calendar day. Use them to control pace during warm-up and to stay within comfortable activity levels.
The Next run count shown on the Home dashboard is the smaller of your eligible contacts and the relevant daily limit. Contacts beyond the cap remain queued and are picked up in a later run.
Start with conservative limits and increase them gradually through the warm-up period. A normal Sales Navigator plan supports roughly 100 contacts per week per account as a ceiling. Higher SSI may allow more, but neither reach nor account safety is guaranteed. keinsaas applies available safety measures; you remain responsible for following LinkedIn hygiene rules.
Choose the channel behavior
For each seat, select one of these channel modes:- Always — both LinkedIn and email run as configured.
- Off — no LinkedIn actions are taken; email can still run.
- Prioritize emails — email outreach runs first; LinkedIn follows only afterward.
Configure follow-ups
The client-wide maximum follow-up counts are:- up to 3 email follow-ups
- up to 1 LinkedIn follow-up
0 to turn it off entirely. Follow-ups are spaced by working days, not calendar days:
A reply on either channel stops all automated follow-ups across both channels for that prospect.
Save and verify
After saving your schedule settings, return to Home and confirm:- Schedule shows Active for every seat you intended to enable
- Daily limits reflect the combined capacity across active seats
- Approval shows the delivery mode you configured
- Next run count reflects the expected caps