Follow-ups that run on their own. From your own mailbox.
Build a workflow once. Omniscient sends each email your team approved from the owner's own mailbox, at a steady pace, and stops when someone replies.
14 days free. No credit card required.
SlackWorkflows on a canvas
Start from a trigger and add steps: send an email, wait, branch, update a field, notify the owner, call a webhook or stop. Keep your workflows in folders.
Start from what happens in a deal
A workflow can start when a record or an opportunity's stage changes, a meeting is held or missed, an email gets a reply, a proposal is viewed or a contract is signed. It can also run on a schedule, or for people you add in bulk.
Every email approved before Publish
Write each email with merge fields, or ask Otto, the AI in Omniscient, to draft it. Every email starts unapproved, changing its words asks for approval again, and Publish waits until each one is approved.
Gmail
Microsoft 365Sent from the owner's own mailbox
Emails go from the record owner's Gmail, Microsoft 365 or IMAP mailbox, as a new email or a reply in the same thread. Each one ends with a one-click unsubscribe link.
A steady pace from each mailbox
Each mailbox sends only in its owner's working hours, with a random gap of 2 to 6 minutes between emails and a daily cap. A newly connected mailbox starts at 20 emails a day and adds 10 a day.
Rina Sato
Marcus Lee
Dana OrtizA reply stops the run
When someone replies, their runs stop in every workflow. A bounce stops the run and an unsubscribe stops every run, and workflows skip that address from then on.
Follow up on proposals and contracts
Deal Room starts workflows too: a proposal viewed, a contract sent or signed, a renewal notice coming up. Wait until a set time before the next meeting, branch on whether they opened Deal Room, or notify the owner in Slack.
Everything in Automation
- Workflows on a canvas
- Folders for workflows
- Record and stage triggers
- Meeting and email triggers
- Proposal and contract triggers
- Schedules and Add to workflow
- Email, wait, branch and update steps
- Approval before Publish
- Replies and unsubscribes stop runs
- Working hours, caps and warm-up
Does anything send before we approve it?
No. Every email in a workflow starts unapproved, and Publish waits until someone on your team approves each one. Changing an approved email's words asks for approval again.
Which mailbox sends the emails?
The record owner's own mailbox: the opportunity's owner, or else the workflow's owner. Gmail, Microsoft 365 and any mailbox connected over IMAP and SMTP can send.
What stops a run?
A reply from the person stops their runs in every workflow. A bounce stops the run, and an unsubscribe stops every run for that address. Workflows skip a bounced or unsubscribed address from then on, and you can stop a run or take a person out by hand.
How fast does it send?
Only in the owner's working hours and days, with a random 2 to 6 minute gap between emails. Each mailbox has a daily cap, 100 by default and 50 for a free Gmail address, and a newly connected mailbox starts at 20 a day and adds 10 a day.
Can Otto write the emails?
When you ask. Otto drafts or rewrites an email step and it's marked as his. It still needs a person's approval before the workflow can go live.
Can someone go through a workflow twice?
You choose: once, or again after a gap once their last run has ended. A person is never in the same workflow twice at once.
The rest of the platform
InviteTry Automation free for 14 days.
No credit card required.