Prepare a safe test workspace

Before you start

• Use a demo workspace when training teammates, testing imports, recording tutorials, or trying a new workflow before using production data.
• Demo data should be realistic enough to teach the workflow but safe enough to share internally or publicly.
• Do not include private customer records, real secrets, billing details, or active recipient data in a demo workspace.

Steps

Step 1

Create a separate workspace

Keep demo work separate from production outreach. Use a clear name so teammates do not confuse test campaigns or lists with live work.

Step 2

Add safe sample contacts and lists

Create small sample lists with non-sensitive names, companies, and emails. Use clear segments so training examples make sense.

Step 3

Add safe sending examples

Show email account setup, validation states, and sender rotation concepts without exposing passwords, tokens, API keys, or real mailbox credentials.

Step 4

Create example campaigns and agents

Use draft or paused examples to teach campaign building, validation, agent configuration, and review workflows without triggering real outreach.

Step 5

Review before sharing

Before using the workspace for training or documentation, check every visible page for private names, emails, phone numbers, account details, tokens, and billing information.

What happens next

• Use the demo workspace for screenshots, tutorials, internal onboarding, and workflow testing.
• Refresh demo data when product UI or examples change so guides stay accurate.

FAQ