Getting started as an Admin
Your first week as an 11x workspace admin: connect your CRM, configure Alice or Julian, invite your team, verify deliverability, and go live.
As an 11x workspace admin, your first week has five jobs: connect your CRM, invite your rollout team, configure one digital worker, verify deliverability, and launch at limited volume. Do them in that order — the CRM connection gates everything else, and deliverability problems are much cheaper to prevent than to repair.
Who this applies to: 11x workspace Administrators. If you're a rep who will receive meetings from Alice or Julian, read Getting started as a User instead.
Before you start
You'll need:
| Requirement | Why |
|---|---|
| Admin access to your CRM | To authorize the connection and map fields |
| DNS access for your sending domain | To publish SPF, DKIM, and DMARC records (Alice only) |
| Your ICP definition | Target industries, sizes, geographies, and titles |
| Your positioning and product materials | To build the knowledge base |
| Calendar access for receiving reps | So meetings book against real availability |
The single most common cause of a stalled rollout is not having CRM admin access lined up. Confirm who owns it before day 1.
Day 1 — Connect your CRM and invite your team
Connect your CRM
Open Settings → Integrations and connect Salesforce or HubSpot. Use a service account with API access and permission to the objects you want synced, rather than an individual's personal credentials.
Detailed guide: Integrate Salesforce. Having trouble? Cannot connect CRM.
Map your fields
Confirm which objects and fields 11x reads and writes. At minimum, map account ownership and opportunity state — these drive the exclusion rules that stop a digital worker contacting an account a rep already owns.
Invite your rollout team
Add:
- One RevOps owner — owns CRM mapping, routing rules, and reporting
- One messaging owner — owns the knowledge base and ICP definition
- The receiving reps — who will get the meetings
Set notification preferences
Decide who gets alerted on what. Connect Slack so booked meetings and escalations reach the right channel and the right rep.
Day 2 — Choose and configure a digital worker
Start with one. Running both on day one splits your attention and makes it harder to tell which configuration is working.
| Start with | If your problem is | Setup guide |
|---|---|---|
| Alice | Not enough qualified pipeline entering the funnel | Set up Alice |
| Julian | Inbound leads going cold before a rep reaches them | Set up Julian |
Work through Set up Alice:
- Authenticate your sending domain (SPF, DKIM, DMARC)
- Build the knowledge base — positioning, product detail, differentiation, objections, proof points, and boundaries
- Define your ICP — firmographics, roles, and exclusions
- Configure your first sequence — channels, cadence, exit conditions
- Enable the Qualification Agent
Budget real time for the knowledge base. It's the input that determines whether Alice's outreach reads like a rep wrote it, and it's the step teams most often rush.
Work through Set up Julian:
- Provision phone numbers and enable Connection Boosts
- Connect your lead sources — forms, chat, inbound line, and Dynamic Triggers
- Define qualification criteria and scoring thresholds
- Build a call flow — opening, discovery, boundaries, objections, outcomes
- Configure routing rules and connect rep calendars
Connect lead sources directly rather than relying on CRM sync to surface new leads. If Julian learns about a lead late, nothing downstream recovers the time.
Day 3 — Verify deliverability
Do this yourself before launching. Don't assume the records are correct because you added them.
Verify each independently:
| Check | Tool |
|---|---|
| Everything at once | Domain health checker |
| SPF resolves | SPF record checker |
| DKIM signs validly | DKIM checker |
| DMARC policy in place | DMARC checker |
| Not blocklisted | Email blacklist checker |
| Gmail reputation | Google Postmaster health check |
Then confirm the Deliverability Engine is pacing volume upward on any new mailbox rather than starting at target rate.
- Confirm your numbers are local to the geographies you sell into
- Confirm Connection Boosts is enabled
- Place a test call and confirm it connects without a spam label
- Confirm your call recording disclosure is configured where required
Day 4 — Test end to end
Run a test through the full path
For Alice: pull a sample of prospects and read the drafted messages and the research behind them. For Julian: submit a real form with a phone number you control and confirm he responds within 60 seconds.
Test both outcomes
Confirm the qualified path books and routes correctly, and the disqualified path logs cleanly without creating a meeting.
Verify CRM write-back
Check that interactions, transcripts, scores, and outcomes land on the objects and fields your reporting expects. Fix this now — backfilling misplaced data later is painful.
Confirm the rep handoff
Ask a receiving rep whether they got enough context to run the meeting. A calendar invite with no qualification context wastes the qualification.
Day 5 — Go live at limited volume
Launch below target volume
Start at a fraction of your intended volume. Confirm deliverability, reply quality, and qualification accuracy hold before scaling.
Review daily for the first week
Not weekly. Early signal tells you whether the ICP is too broad or the messaging is off, and both are cheap to fix before volume builds.
Collect rep feedback formally
Ask receiving reps to flag any meeting they'd consider unqualified. Their disagreement is your best signal for tuning thresholds.
Then scale
Once the metrics hold at limited volume, increase. Add the second digital worker only after the first is stable.
What to watch in the first week
| Metric | What a problem looks like | Where to look |
|---|---|---|
| Inbox placement (Alice) | Falling placement rate, rising bounces | Mailbox health in analytics |
| Connect rate (Julian) | Calls not connecting or labelled as spam | Call deliverability in analytics |
| Reply / response quality | Replies from the wrong people | Sample the replies directly |
| Qualification accuracy | Reps disputing booked meetings | Rep feedback + disqualified transcripts |
| CRM data integrity | Missing or misplaced fields | Spot-check records |
Ongoing admin responsibilities
- Keep the knowledge base current. New product, new positioning, new competitor — update it, or output drifts.
- Review disqualifications monthly. Good leads wrongly disqualified disappear silently.
- Watch domain and number reputation. Reputation degrades gradually and is slow to repair.
- Manage users and access as the team changes.
- Follow the changelog for new capabilities worth enabling.
Troubleshooting
Next steps
Set up Alice
Full outbound configuration.
Set up Julian
Full inbound configuration.
Integrations
Slack, calendars, and webhooks.
Getting started as a User
Share this with your reps.
Still need help
Email support@11x.ai with your workspace name, the worker involved, and any error message. For rollout planning, book time with the team.