Get started
Go from a new workspace to your first tracked signup from cold email, yourself or through your coding agent.
A new workspace has one job to do before cold email turns into users: know who signed up and who paid. The Get started checklist gets you there in four steps and checks each one against your live workspace, so it ticks itself off whether you do the work in the dashboard or your agent does it through the API.
First sign-in
After you create an account, onboarding asks two things:
- About you. Your name, the workspace name, and optionally the page where people sign up for your product. The Reply Agent sends interested prospects to that link, and you can change it later under Settings > Workspace.
- How you want to set up. Hand setup to your coding agent (recommended), follow the checklist yourself, or look around first. Every choice leaves you with a working workspace, and the checklist stays on your home page until it is done.
Hand it to your agent
Copy setup prompt puts one prompt on your clipboard for Claude Code, Codex, Cursor, or another agent. The agent installs the Sendsets skill, signs in, and works through the four steps below in order, confirming each with you before the next. Because it can read your codebase, it adds the signup and payment events where your product creates accounts and takes payments, writes the Reply Agent's knowledge from your README, docs, and pricing, and tests both. It asks before anything that costs money or emails a real prospect.
Each step on the checklist also has Copy the prompt for this step, for when you want to do most of it yourself and hand off one part.
The four steps
Open the checklist from Get started in the header or the card on Home. A step shows as done only when the workspace proves it, and as waiting when it is configured but not yet tested.
| Step | Done when |
|---|---|
| Connect your mailboxes | At least one sending mailbox is connected. See Mailboxes. |
| Connect signups and revenue | A primary signup goal exists and an event it matches has arrived from your product. A primary paid goal is optional until you charge. |
| Set up the Reply Agent | A signup URL and offer are set, at least one knowledge source is saved, drafting is on, and the agent has drafted a reply. |
| Launch your first campaign | A campaign is active or has completed. |
Connect signups and revenue
Send signed_up from your backend when someone creates an account, and paid with an amount in minor units and a currency on their first payment, each with an identity carrying the user's email and your user id. Then add a signup goal and a paid goal from the checklist or under Acquisition > Tracking > Goals. The Dry run button calls POST /events/test, which shows how an event would resolve and which goals it would match without storing anything. The step completes when a real event arrives. See Acquisition for the event contract.
Set up the Reply Agent
Set the signup URL and a one-line offer, turn on reply drafting, and add product knowledge under Settings > Workspace. To test it, reply "Sure, send it over" from an address you own to an email one of your mailboxes sent. The drafted reply appears on the checklist within a minute or two and waits for your approval in the inbox. Drafting needs a paid plan; automatic sending is a separate opt-in. See Inbox agent.
Skipping and coming back
Nothing on the checklist blocks the rest of the product. Hide the card on Home with its close button (it stays hidden in that browser) and reopen the checklist any time at /app/get-started. The header shows your progress until every step is done.