Launch your first automation safely
Plan, test with yourself, launch to a small group and improve. A simple four-step routine for automations, AI agents, emails, forms and pages.
Before anything in Spacebrain contacts real customers, run through four simple steps: plan it, test it on yourself, launch to a small group, then review and improve. This guide walks you through that routine with a worked example. It's for whoever builds or approves automations, AI agents, email campaigns, forms and pages.
Use the same routine again whenever you make a big change, such as a new audience, a new sender, new AI instructions or a new schedule.
Before you begin
- A test contact: yourself, with an email address or phone number you can check. Label it clearly, for example
Test – Maya (internal). - The right workspace: check the name at the top of the left sidebar.
- Any account the automation needs is connected, such as your email in Inbox → Email accounts or a phone number in Chat & Voice → Phone Numbers.
- Permission to contact the people you'll eventually send to, and the opt-out wording your region requires.
- A second person who can pause things if you're not around.
Step 1: Plan it
Write down, in one or two sentences, what should happen. Be specific.
- Too vague: "Send a follow-up."
- Clear: "When someone fills in the quote form, create a task for Priya to call them within one business day."
Then answer these questions:
| Question | Example answer |
|---|---|
| What starts it? | A new lead is created from the quote form |
| Who is it for? | New leads from the website only |
| What should happen? | Create a follow-up task assigned to Priya |
| How will I know it worked? | A task appears in Priya's Tasks list, linked to the lead |
| Who can pause it? | Priya or Sam |
| When should we pause it? | If it creates duplicate tasks, or tasks for the wrong people |
Start without customer messages
Your first version doesn't need to email or text anyone. Creating a task or updating a record is a safe way to prove the trigger works. Add customer messages once that part is reliable.
Step 2: Test it on yourself
- Build the automation, agent, form or page.
- If there's a preview or dry run, use it first. For automations, select Run dry test to see which path your contact would take without changing anything.
- Run it once for real, using only your test contact.
- Wait a minute, then check that the result is there (see the table below). Don't run it again until you've checked. A slow result isn't always a failed one, and running twice can create duplicates.
- Also try one thing that should not work, such as a contact with no email address, or someone who has opted out. Make sure nothing is sent.
Where to check the result
| You built... | Check here |
|---|---|
| An automation | Automations → Runs for the run and its status, then the record or task it should have created |
| A message or reply | Inbox, in the conversation with your test contact |
| An AI voice or chat agent | Chat & Voice → Recordings or the agent's test call, plus the lead or task it created |
| A form, page or funnel | The form's Responses, then the lead in CRM → Leads |
| A task handoff | Tasks, checking the assignee, due date and linked record |
| Something in a connected app | Spacebrain's result and the item in the other app (for example, the event in Google Calendar) |
You're ready to move on when the result appears once, in the right place, for the right person, and nothing unexpected happened.
Previews are different from real tests. A form preview only shows how it looks. Some tests create real records, messages, calls or even payments, so read what a test button does before you select it.
Step 3: Launch to a small group
Don't jump from one test to your whole audience.
- Choose a small group first, such as today's new leads or 10–20 contacts.
- Note the start time and who's watching.
- Decide in advance when you'll pause, for example after two errors, one complaint, or any message sent to the wrong person.
- Switch it on. For automations, select Publish. For forms, select Publish.
- Keep the results page open (for example Automations → Runs or the Inbox) while the first few go through.
How to pause quickly
- Automations: open the automation and select Pause.
- Forms: open the form and select Unpublish.
- Email automations: pause the automation from Email → Automations.
- AI agents: remove the agent from the phone number or chat widget it's connected to.
Make sure the person watching knows how to do this without asking the builder.
Step 4: Review and improve
After the small group has gone through, compare what happened with your plan. Ask these questions in order and stop at the first "no":
- Did the right people or records start the automation?
- Did Spacebrain do each step once?
- Did the connected app (email provider, calendar, phone) accept it?
- Did the customer or teammate get what they needed?
- Were errors, opt-outs, complaints and credit use within your limits?
Fix the first thing that went wrong, and only that. Changing several things at once makes it hard to tell what worked. Then test again on yourself (Step 2) before you widen the audience.
Early numbers can mislead. With only a few contacts, one result swings the percentage a lot, and some reports take time to update. Look at the actual records as well as the charts. See reports and analytics.
Worked example: follow up with every new lead
Sam wants every new website lead to get a call from Priya.
- Plan: "When a lead is created, create a task called Review new lead, assigned to Priya, due in one day."
- Build: In Automations → All Automations, Sam selects New Automation, then Describe with Orbit, and types the sentence above. Orbit prepares a plan. Sam reviews it and selects Save draft. (Orbit AI uses credits.)
- Test: Sam selects Run dry test, then publishes and adds a test lead named
Test – Sam (internal). In Automations → Runs, the run shows as complete. In Tasks, Priya has one task linked to the test lead. - Check for surprises: Sam confirms the test lead received no email or text (this version only creates a task) and that exactly one task was created.
- Launch: They leave it running for one day and check every run.
- Improve: Priya asks for the lead's phone number in the task title. Sam changes only that, tests once more, and leaves it running.
Want a ready-made version? See the lead follow-up automation recipe.
If something goes wrong
| What you see | Likely cause | What to do |
|---|---|---|
| Nothing happened | The trigger didn't match, or the automation is still a draft | Check Automations → Runs. If there's no run, check the trigger and that the automation is published. |
| The run failed | A step is missing information or a connection | Open the run to see which step failed and why. Fix that step, then test again. |
| Two of everything | It ran twice, or you retried too soon | Pause, check the runs, and remove duplicates. Next time, wait and check before retrying. |
| Message sent but not received | The email provider or phone carrier delayed or blocked it | Check the conversation in Inbox and the connection in Integrations. |
| Upgrade to activate or Start trial to activate | Your plan limits active automations | Upgrade in Settings → Billing, or pause another automation. |
For a step-by-step checklist, see the troubleshooting guide.
FAQ
Do I need to do all four steps for small changes?
For small wording fixes, a quick test on yourself is usually enough. Repeat all four steps when you change who receives it, which account sends it, the AI's instructions, the schedule or anything involving payments.
Is it safe to test with real customers?
No. Always test with yourself or a teammate who has agreed to receive test messages.
What if my plan doesn't include the feature I want to test?
You'll see an upgrade message, such as Upgrade required or Upgrade to activate. Plans differ in what they include and how many automations can be active at once. Check Settings → Billing for your plan's limits.
Next step
Pick the guide for your role in Quick starts by role.
Next step
Keep moving
Open the relevant Spacebrain screen or contact support if you need help.
Last updated on
Workspace and team setup
Name your workspace, switch between workspaces, invite teammates, pick the right role, set module permissions, transfer ownership and remove access.
Quick starts by role
Pick the short setup path that matches your job (owner, sales and support, builder and marketer, or agency) instead of learning every module at once.