Cooldowns & Blocklist
Stop spamming your users and prevent outreach to at-risk or high-touch customers.
Cooldowns
Orbital provides a set of cooldowns to make outreach safe and simple for everyone on your team:
- In-App Cooldown Period: Days to wait before attempting to recruit in-app once the intercept is dismissed
- Email Cooldown Period: Days to wait before attempting to recruit via email after receiving a discovery invitation by email
- Interview Cooldown Period: Days to wait before attempting to recruit via any channel after a completed interview session
Blocklist
While cooldowns are temporary, the blocklist permanently prevents users from being contacted by Orbital.
To add users to your blocklist, you can do that either individually from the users table or by bulk upload.
Blocklist upload (csv)
To add users to the blocklist in bulk, you can upload a CSV consisting of either email
's or userId
's.
How it works:
- Only the first csv column will be read.
- If the users already exist within Orbital, they will be flagged as blocked, otherwise new blocked users will be created the provided attribute.
- We validate each row individually and skip those that fail validation. For
userId
, missing and empty rows are skipped. Foremail
, rows are also checked for a validity.
For example:
email
john@doe.com
jane@smith.com
jeremy@dune.com
…
or
userId
806510ed-f6ff-48a4-926e-1ed3045b1741
4360b2ac-19b8-49f4-862e-bfe18e6c411f
c07c0b9a-9534-4e29-be98-d0dd01df601e
…
Known limitations
- No support for blocking based on a set of filters, eg. set of companies (on roadmap)