Multi-rep team
Draw the territory, route the signals, score the doors — every rep working their own block
When more than one rep is in the workspace, Afterplots adds Territories, Team messages, and role-aware Profile so every signal already knows who owns it the moment it lands. The proprietary Neighbor Lead Score and Neighbor List behave the same for the team as they do for the operator — just with routing and visibility built in.
A growing team needs routing, not more meetings
Two reps and one map is a daily 'who's working that block?' conversation. Afterplots replaces the standup with a drawn territory, an assigned rep, a deterministic priority on overlap, and a chat thread inside the same workspace where the signals are.
Playbook
- Step 1
Draw and assign territories
Workspace admins draw rectangle or polygon territories, set priority for overlap, and assign reps. The same listing, permit, and neighbor pins from Property Search and Neighbor List are then routed to the right teammate's view.
- Step 2
Score consistently across the team
Every rep opens the proprietary 0–100 Neighbor Lead Score on the doors inside their territory; the rationale, source-labeled evidence, and quick compare don't drift between operators. The whole team works from the same number.
- Step 3
Coordinate in Team messages — and turn it into work
Workspace-scoped chat keeps the conversation about a territory or a Neighbor List row inside Afterplots — not in a side channel that loses context on Monday. The Tasks & activity panel on the Territories screen converts the chat into assigned work: admins and full seats assign mail, calls, and visits; open tasks pin to the top until someone marks them done; activity entries (listing outreach, permit follow-ups, neighbor contacts) land in the same shared feed so the team's week has one timeline.
- Step 4
Automate and report from one place
Run automations on shared triggers; ship signed CRM webhooks, Slack alerts, and audience exports from Integrations. Profile manages roles (Viewer, Full, Admin) so the right tabs appear for the right teammate.
A typical week
What a week looks like when the spine is running unattended — here it is for a Charleston roofer with two reps.
Devon · West Ashley · Maria · Mt. Pleasant
- Monday
Owner sets up the workspace
The owner draws two territories on the map — West Ashley to Devon, Mt. Pleasant to Maria — and Slack starts posting fresh signals into #afterplots-leads.
- Tuesday · 8:14 AM
A signal stacks on Devon's block
A ranch two streets from one of Devon's recent jobs goes pending, and a neighbor on the next block pulls a Permit listing for a re-roof — lighting up High Area activity on his Signal data table (not Maria's). His console already shows 38 same-era ranches within four blocks, ranked by how well each fits a re-roof job for this team.
- Tuesday · 2:30 PM
One click → 38 different postcards
Devon pings the owner in team messages to confirm the offer, hits Create Lead, and Afterplots auto-generates 38 different postcards — each keyed to that street and era, each with a QR pointing to a landing page built for that home. On rows where the public record names the owner, he clicks Lead enrich and Afterplots adds an owner phone and email to each one.
- Thursday
The cards hit mailboxes
The artwork prints with the company logo and phone. Each QR opens a landing page built for that house — the mailbox story and the phone story stay one continuous experience.
- Friday afternoon
Warm follow-ups, not cold calls
Two scans and one form fill ping the CRM and Slack in real time and route to Devon's seat. The enriched contacts let him follow up warm on three more homes from the same batch — same play they'd run by hand if they had a full marketing team.
This walkthrough uses a Scale workspace; the same spine runs on every paid tier with the team and integration features the tier supports.
Run your first Tuesday in 10 minutesPlan considerations
Territories and Team messages live on the Scale tier. Automations and Integrations (including Audiences retargeting packs) require Growth or Scale; conversion lookalike seeds require Scale. Mailed postcards, lead credits, and team management surface in Profile once the corresponding tier and admin role are in place.
Same spine, scaled up
Nothing about the underlying workflow changes when a workspace adds reps. Property Search, the Neighbor Lead Score, Neighbor List, and the postcard + landing pair stay identical — Territories and Team messages add the routing and the conversation, that's it.