Safety and controls
Safe by defaultwith every control in reach
For RevOps and security reviews: the limits Outlevo works within from day one, what you can change, who can change it, and how to stop everything at once.
Outbound rules
One document says who can be contacted
Countries, buyers, channels, daily limits, budget and suppressions, in a file anyone can read. Every workspace starts with a safe default, and every action records the version it ran under.
- The default outbound policy is created at sign-up, with countries read from your website
- Change a limit and it applies to the next action
- Versioned: every action records the policy version it ran under
# Created for you at sign-up; change any line
countries: [US, CA] # read from your website
buyers: [VP Finance, Controller, CFO]
company_size: 200..2000
channels:
email: { mailboxes: 3, per_mailbox_per_day: 40 }
linkedin_ads: { monthly_budget_usd: 1200 }
touches_per_contact: 3
suppress: [customers, open_deals, unsubscribed]
evidence: every_claim_needs_a_source
needs_approval: [] # optional, e.g. [new_segment]
kill_switch: owner_or_adminLimits that protect your domain
Outlevo sends the way a careful person would, and holds anything that could hurt your reputation.
Daily limits per mailbox
A set number of sends per mailbox per day, with new mailboxes warmed up before they send.
Sender checks
SPF, DKIM and DMARC are checked before any send. A sender that fails is held, with the reason, until it is fixed.
Budgets and credits
Ad budgets you set, and a credit cost shown before every piece of metered work.
Suppressions
Never emails the wrong people
Some people are never contacted, whatever a campaign says. The list is checked before anything goes out.
- Your customers and open deals, read from your CRM
- Anyone who unsubscribed or asked not to be contacted
- Hard bounces and addresses that failed verification
- Customersfrom HubSpot · always
- Open dealsfrom HubSpot · always
- Unsubscribedalways
- Hard bouncesafter one bounce
Kill switch
Stop everything in one click
A kill switch per campaign, per channel or for the whole workspace. It takes effect on the next action, and it is recorded with who pulled it and why.
- Owners and admins can pull it, from the app or the API
- Paused work resumes only when someone releases it
- CampaignFinance leaders · paused
- ChannelLinkedIn Ads · running
- Workspaceeverything · running
Audit trail
Every action, on the record
Each email, audience upload, CRM write and setting change is recorded with what ran, when, the sources behind it and the rules it ran under.
- Insert-only: an entry is never edited or deleted
- Who, when and why for every setting change
sent 09:41 · 2 sources · policy v4 · mailbox 2 of 4 · Northwind Analytics (fictional)
Optional for teams
Add a person where you want one
Require a sign-off on the ICP, the first email to a new segment, a new ad audience or anything above a budget. Start without it and add it as you grow.
- Approval steps are off by default and turned on per step
- Approvers sign with a second factor
- Every approval is in the audit trail
Two-factor and scoped access
- Two-factor for sign-offs and outbound policy changes
- Roles per workspace: owner, admin, approvers and members
- Scoped API keys; live keys are refused when sent from a browser
- Staff support access is read-only, time-limited and logged
- Row-level security per customer, field-level encryption for personal data: see security
Safe by default, from the first email
Start with a free ICP from your own website. 60 seconds · No sign-up · No card.