Get startedQuickstart
Quickstart
Your first hour, then your first month. SAGARIS tracks activation as a real checklist with day targets, and this page is that checklist with the reasoning attached: what each step unlocks, what the product refuses to do until it is done, and what to expect when you do it.
Sign in with your company email
Use your work address. A personal mailbox domain is refused at sign-in with a message asking for your company email, because the domain is what matches you to your organization.
The first person to arrive on a domain creates the organization, and their suggested role is the workspace's highest: super admin. Everyone who arrives afterwards on that same domain joins the existing organization, suggested as a sales rep. That is a default rather than a ceiling, and an admin can change any member's role afterwards.
Connect your business mailbox. Day 1, and it is required
This is the one step that is not optional. SAGARIS proposes next steps, creates tasks and suggests next best actions from the live correspondence with your prospects and customers. Without the mailbox it cannot see that correspondence, and a system that proposes next steps while blind to half the conversation is not being cautious, it is being wrong.
Supported today: Google Workspace (Gmail), Outlook, Yahoo Mail, iCloud Mail, and AOL Mail. Gmail and Outlook connect over OAuth. Yahoo, iCloud and AOL connect with an app-specific password over IMAP and SMTP; the password is encrypted before it is stored.
Required does not mean locked out. Nothing throws, 4xxs or removes access while the mailbox is missing. A workspace cannot be reported as activated without it, its absence shows as a critical and undismissable health flag, and any feature that depends entirely on the mailbox mirror says what it cannot see rather than returning an empty result that reads like an all-clear.
A SAGARIS-managed sending identity does not satisfy this. The requirement is your own business mailbox: a workspace whose only mailboxes are platform-procured senders reads as not connected, deliberately.
Get your contacts in
Import from CSV under CRM, or create contacts through the API. The import wizard previews the file before anything is written: it maps your columns, and it shows which rows already match a contact in the workspace so you can see what would be created against what would be updated. Matching is on the email address, lowercased and trimmed.
- 50,000 rows
- The most a single import may submit. Split a larger dataset into batches.
- 25 MB
- The largest file the wizard will read, and the largest import request body the API accepts.
Launch a play
You do not have to write a cadence from scratch to start. The workspace ships with canonical sequence templates, each a complete cadence with its emails already written, that you can launch against an audience and then edit.
- Cold to meeting
- The flagship cold-to-meeting cadence. Email touches are seeded as concrete copy; LinkedIn, SMS and phone touches run from the channel-aware timeline.
- B2B Enterprise
- Value-led cold cadence for senior buyers at companies over 100 employees, building credibility before asking for time.
- SMB fast-track
- Compressed cold cadence for owners and GMs at companies under 50 employees, built to match how fast an SMB buyer decides.
- ABM multi-stakeholder
- Coordinated account-based cadence for a buying committee of three or more stakeholders, working toward one discovery call.
- Re-engagement
- Win-back cadence for contacts who finished a sequence without converting, or lost deals where the timing was wrong. Each touch leads with something new.
- Inbound lead fast-track
- Warm follow-up for contacts who viewed pricing, downloaded content, joined a waitlist or replied to a campaign, paired with same-day SMS and call tasks.
Before a sequence can reach anyone, the workspace's outbound gate has to be open, the contact has to be off the suppression list, and any action your autonomy level does not let an agent take alone has to be approved. See Introduction for what each of those holds is.
The first thirty days
Activation is measured over a thirty-day window and the product shows you where you are in it. The day targets are not deadlines; they are the ramp the checklist is built on, core setup in week one, engagement signals in week two, pipeline and team habits by week four.
- Day 1
- Connect your business mailbox. Configure your ICP, the ideal-customer profile that targets every campaign.
- Day 2
- Launch your first campaign: put a sequence live against your ICP audience.
- Day 3
- Connect your calendar, so prospects book without the back and forth.
- Day 5
- Get your first reply. A real human response is what confirms the messaging lands.
- Day 7
- Place your first dialer call, so the motion is multichannel rather than email only.
- Day 10
- Start an A/B test, so the engine has something to learn from.
- Day 14
- Book your first meeting.
- Day 16
- Advance a worked contact to Lead and into the pipeline.
- Day 18
- Record a meeting, so it can be summarized and coached from.
- Day 21
- Build a go-to-market plan on a target account.
- Day 25
- Set a quota, so forecasting has a goal to measure against.
- Day 30
- Invite a teammate or connect your CRM.
Only the mailbox is a hard requirement. The other twelve are correlates: a workspace that never runs an A/B test is less likely to survive, but it is not misconfigured. While the mailbox is outstanding the workspace reports as blocked no matter how many of the other rows are ticked.
Behaviour on this page is read from
- src/lib/activation-checklist-taxonomy.ts
- src/lib/mailbox/corporate-mailbox-readiness.ts
- src/lib/mailbox/provider.ts
- src/app/api/mailbox/connect/route.ts
- src/lib/org-signup.ts
- src/lib/import-limits.ts
- src/lib/import-dedupe.ts
- src/lib/canonical-sequence-templates.ts
Was this page helpful?