Aron — Implementation Playbook (DSO)

Aron Implementation Playbook

AI-Powered Marketing & Patient Acquisition Platform for DSOs

---

1. Executive Summary

What Aron Does

Aron is an AI-powered marketing and patient acquisition platform that automates lead generation, campaign optimization, and patient conversion tracking across multiple locations. The platform leverages machine learning to optimize ad spend, personalize patient outreach, and provide unified analytics on marketing ROI at both the location and enterprise level.

Why DSOs Benefit from AI-Driven Marketing & Acquisition

DSOs operating at scale face a fundamental challenge: marketing effectiveness varies wildly across locations, yet most organizations lack the infrastructure to optimize campaigns at the individual practice level while maintaining brand consistency. AI-driven marketing platforms like Aron solve this by:

• Scale Advantages: Aggregate data from 15–50+ locations creates a proprietary learning dataset that improves campaign performance faster than any single practice could achieve alone
• Standardization with Localization: Centrally managed brand guidelines and messaging frameworks deploy automatically while AI optimizes for local market conditions, demographics, and competitive dynamics
• Data Aggregation & Attribution: Unified tracking across all locations enables true multi-touch attribution, eliminating the "which marketing actually works?" problem that plagues decentralized marketing operations
• Resource Efficiency: Replace fragmented agency relationships and manual campaign management with a single platform that scales without proportional headcount increases

Expected Timeline: Decision to Full Deployment

Phase	Timeline	Scope
Pre-Implementation	Weeks 1–2	Infrastructure prep, stakeholder alignment, baseline capture
Wave 1 Pilot	Weeks 3–6	2–3 locations
Wave 2 Expansion	Weeks 7–12	Next 5–8 locations
Wave 3 Full Deployment	Weeks 13–20	Remaining locations
Optimization & Stabilization	Weeks 21–24	Enterprise-wide refinement

Total Timeline: 5–6 months from contract signature to full deployment across all locations

---

2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Hardware

☐ Verify all locations have workstations with minimum specs (8GB RAM, modern browser, stable internet) ☐ Confirm minimum 25 Mbps download/10 Mbps upload speeds at each location ☐ Identify locations with legacy hardware that may need upgrades before deployment

Software

☐ Document PMS versions across all locations (Dentrix, Eaglesoft, Open Dental, or other) ☐ Confirm browser compatibility (Chrome 90+, Edge 90+, Safari 14+) ☐ Inventory existing marketing tools to be replaced or integrated (Google Ads accounts, Facebook Business Manager, CRM systems)

Network & Security

☐ Verify firewall rules allow outbound HTTPS traffic to Aron's domains ☐ Confirm VPN/network segmentation requirements for HIPAA compliance ☐ Document any locations with restricted network environments (hospital-affiliated, mall-based)

Integrations Required

☐ Practice Management System API access or HL7/FHIR capability ☐ Google Analytics/Tag Manager access for all location websites ☐ Google Ads and Meta Business Manager admin access ☐ Call tracking system access (if applicable) ☐ CRM system access (Salesforce, HubSpot, or internal)

Vendor Onboarding Steps

🔵 ☐ Schedule kick-off call with Aron implementation team 🔵 ☐ Establish dedicated Slack channel or communication platform with Aron support 🔵 ☐ Obtain Aron technical documentation and API specifications 🔵 ☐ Confirm assigned Customer Success Manager and escalation contacts 🔵 ☐ Review and sign Business Associate Agreement (BAA) 🔵 ☐ Obtain sandbox/test environment credentials

Key Vendor Contacts to Establish

Role	Purpose	Response SLA
Customer Success Manager	Strategic guidance, QBRs	24 hours
Technical Implementation Lead	Integration support	4 hours during implementation
Tier 1 Support	Day-to-day issues	2 hours
Tier 2 Engineering	Complex technical issues	8 hours

Data/Access Prerequisites

☐ Compile admin credentials for all marketing platforms across locations ☐ Export historical marketing spend data (minimum 12 months) ☐ Export historical patient acquisition data from PMS (new patient counts, sources) ☐ Document current call tracking numbers and routing ☐ Compile website analytics access for all location sites ☐ Export current patient demographic data (de-identified) for AI training

API Keys & Access Required

☐ Google Ads API access (MCC-level preferred) ☐ Meta Marketing API access ☐ PMS API credentials or secure integration credentials ☐ Website CMS admin access for tracking pixel installation ☐ Phone system API access for call tracking integration

Internal Stakeholder Alignment

🟣 Who Needs to Approve

Stakeholder	Approval Required For	Timeline
CEO/COO	Budget, strategic initiative approval	Week -2
CFO	Spend authorization, ROI expectations	Week -2
Chief Dental Officer	Clinical workflow impact (if any)	Week -1
VP of Operations	Rollout plan, resource allocation	Week 1
VP of Marketing	Platform ownership, KPI alignment	Week 1
CISO/IT Director	Security review, integration approval	Week 1
Legal/Compliance	BAA review, data governance	Week 1

Who Needs to Be Informed

☐ Regional Managers — rollout timeline and their role ☐ Location Office Managers — what to expect and when ☐ Front desk staff — patient inquiry handling changes ☐ External marketing agencies (if transitioning away) — sunset timeline

Stakeholder Alignment Map

                    ┌─────────────────────┐
                    │   Board/Investors   │
                    │  (Quarterly Updates)│
                    └──────────┬──────────┘
                               │
                    ┌──────────▼──────────┐
                    │      C-Suite        │
                    │ CEO, CFO, COO, CDO  │
                    │  (Monthly Updates)  │
                    └──────────┬──────────┘
                               │
         ┌─────────────────────┼─────────────────────┐
         │                     │                     │
┌────────▼────────┐  ┌─────────▼─────────┐  ┌───────▼────────┐
│ VP of Marketing │  │  VP of Operations │  │  IT Director   │
│ (Platform Owner)│  │ (Rollout Leader)  │  │(Technical Lead)│
└────────┬────────┘  └─────────┬─────────┘  └───────┬────────┘
         │                     │                    │
         └──────────┬──────────┴────────────────────┘
                    │
         ┌──────────▼──────────┐
         │  Regional Managers  │
         │  (Weekly Updates)   │
         └──────────┬──────────┘
                    │
    ┌───────────────┼───────────────┐
    │               │               │
┌───▼───┐       ┌───▼───┐       ┌───▼───┐
│  OM   │       │  OM   │       │  OM   │
│ Loc 1 │       │ Loc 2 │       │ Loc 3 │
└───┬───┘       └───┬───┘       └───┬───┘
    │               │               │
┌───▼───────────────▼───────────────▼───┐
│        Location Staff & Providers     │
│          (Training & Go-Live)         │
└───────────────────────────────────────┘

Baseline Metrics to Capture

⚠️ Critical: Capture these metrics BEFORE any Aron implementation begins. Without baselines, ROI measurement is impossible.

Standardized Metric Definitions for Cross-Location Comparison

Metric	Definition	Data Source	Capture Frequency
Cost Per Lead (CPL)	Total marketing spend ÷ Total leads generated	Ad platforms + call tracking	Monthly, trailing 6 months
Cost Per New Patient (CPNP)	Total marketing spend ÷ New patients from marketing	PMS + attribution	Monthly, trailing 6 months
Lead-to-Appointment Rate	Appointments scheduled ÷ Total leads	Call tracking + PMS	Monthly, trailing 6 months
Appointment-to-Show Rate	Patients who showed ÷ Appointments scheduled	PMS	Monthly, trailing 6 months
New Patient Volume	Total new patients per month	PMS	Monthly, trailing 12 months
Marketing Spend	Total spend across all channels	Finance/accounting	Monthly, trailing 12 months
Marketing ROI	(Revenue from marketing patients - Marketing spend) ÷ Marketing spend	PMS + Finance	Quarterly
Channel Mix	% of spend and leads by channel	Ad platforms	Monthly
Website Conversion Rate	Form submissions + calls ÷ Website visitors	Analytics + call tracking	Monthly
Average Response Time	Time from lead submission to first contact	Call tracking + CRM	Monthly

Baseline Collection Protocol

☐ Export 12 months of marketing spend by channel by location ☐ Export 12 months of new patient data with source attribution (where available) ☐ Export call tracking data with disposition codes ☐ Run website analytics report for each location site ☐ Document current marketing team headcount and agency spend ☐ Survey regional managers on perceived marketing effectiveness (1-10 scale) ☐ Calculate current metrics using standardized definitions above ☐ Store baseline data in centralized location (recommend shared dashboard)

Time Estimate: 15–20 hours of analyst time to compile across 15–50 locations

Enterprise-Level Requirements

Network Standards Across Locations

☐ Document network architecture (hub-and-spoke vs. independent) ☐ Verify consistent DNS resolution for Aron domains ☐ Confirm SSL/TLS requirements met at all locations ☐ Test API connectivity from representative locations in each region

🟣 Hosting Decision: Centralized vs. Location-Level

Factor	Centralized Hosting	Location-Level
Data aggregation	✅ Native	Requires sync
Configuration management	✅ Easier	Complex
Network dependency	⚠️ Single point of failure	✅ Distributed
Compliance	✅ Unified controls	Per-location audit

Recommendation: Centralized hosting with location-level configuration

Single Sign-On (SSO) Requirements

🔵 ☐ Confirm Aron supports SAML 2.0 or OAuth 2.0 ☐ Document identity provider (Okta, Azure AD, Google Workspace) ☐ Define role-based access control (RBAC) structure ☐ Create user provisioning/deprovisioning workflow

Centralized Credentialing

☐ Establish master service account for Aron platform ☐ Define location-admin vs. regional-admin vs. central-admin permission tiers ☐ Document credential rotation policy ☐ Create offboarding checklist for credential revocation

---

3. Location Readiness Assessment

Scoring Framework

Rate each factor 1–5 for every location, then calculate composite score.

Factor 1: IT Infrastructure Maturity (Weight: 25%)

Score	Network Speed	Hardware Age	PMS Version
5	>100 Mbps	<2 years	Current release
4	50-100 Mbps	2-3 years	1 version behind
3	25-50 Mbps	3-4 years	2 versions behind
2	10-25 Mbps	4-5 years	3+ versions behind
1	<10 Mbps	>5 years	Unsupported version

Factor 2: Staff Tenure & Adaptability (Weight: 20%)

Score	Avg Tenure	Turnover Rate	Tech Comfort	Recent Training
5	>3 years	<15%	High (self-directed)	Multiple tech trainings in past year
4	2-3 years	15-25%	Above avg	1-2 tech trainings
3	1-2 years	25-35%	Average	Some training history
2	6mo-1yr	35-50%	Below avg	Limited training
1	<6 months	>50%	Low (resistant)	No recent training

Factor 3: Patient Volume (Weight: 20%)

Score	Monthly New Patients	Consideration
5	80+	High impact potential, requires robust support
4	50-79	Strong impact, manageable complexity
3	30-49	Moderate volume, good for pilots
2	15-29	Lower volume, less statistical significance
1	<15	May not justify implementation priority

Note: For Wave 1 pilots, moderate volume (Score 3-4) often optimal — enough data to learn, not so much that failures are catastrophic.

Factor 4: Tech Stack Compatibility (Weight: 20%)

Score	PMS Integration	Website Platform	Current Marketing Tools
5	Native Aron integration exists	Modern CMS (WordPress, etc.)	Already using compatible ad platforms
4	API available, documented	Standard CMS	Minor tool transitions needed
3	API available, limited	Older but functional	Moderate transitions
2	HL7/export only	Limited CMS	Significant transitions
1	No integration path	Custom/legacy	Complete rebuild required

Factor 5: Local Champion Availability (Weight: 15%)

Score	Champion Profile
5	Tech-forward provider AND engaged office manager, both enthusiastic
4	Strong office manager champion with provider support
3	Willing office manager, neutral provider
2	No clear champion, but no active resistance
1	Active resistance from leadership, no champion identified

Composite Score Calculation

Composite Score = (IT × 0.25) + (Staff × 0.20) + (Volume × 0.20) + (Tech Stack × 0.20) + (Champion × 0.15)

Score Interpretation

Composite Score	Readiness Tier	Recommended Wave
4.0 – 5.0	Tier 1: Ready	Wave 1 (Pilot)
3.0 – 3.9	Tier 2: Prepared	Wave 2
2.0 – 2.9	Tier 3: Needs Work	Wave 3 (with remediation)
1.0 – 1.9	Tier 4: Not Ready	Defer until remediation complete

Sample Readiness Scorecard

Location	IT (25%)	Staff (20%)	Volume (20%)	Tech (20%)	Champion (15%)	Composite	Recommended Wave
Phoenix Central	4	4	3	5	5	4.05	Wave 1
Scottsdale North	5	3	4	4	4	4.00	Wave 1
Tempe East	3	4	4	3	3	3.40	Wave 2
Mesa South	3	3	3	3	2	2.85	Wave 3
Chandler West	2	2	2	2	1	1.85	Defer

Rollout Sequence Recommendation

☐ Sort all locations by composite score (descending) ☐ Select top 2-3 scoring locations for Wave 1, ensuring geographic/demographic diversity ☐ Assign next 5-8 locations to Wave 2 ☐ Assign remaining locations to Wave 3 ☐ Create remediation plans for any Tier 4 locations before scheduling 🟣 ☐ Present rollout sequence to VP Operations for approval

---

4. Rollout Strategy

Wave Structure Overview

Wave	Locations	Duration	Purpose
Wave 1: Pilot	2–3 locations	4 weeks	Validate integration, refine training, identify issues
Wave 2: Expansion	5–8 locations	5 weeks	Scale validated playbook, build internal expertise
Wave 3: Full Deployment	Remaining locations	6–8 weeks	Complete rollout with proven approach

Buffer between waves: Minimum 1 week for retrospective and playbook updates

Wave 1: Pilot Locations (Weeks 3–6)

Selection Criteria for Wave 1

Wave 1 locations should meet ALL of the following:

☐ Composite readiness score ≥ 4.0 ☐ Identified champion willing to dedicate 5+ hours/week during pilot ☐ Patient volume sufficient for statistical learning (30+ new patients/month) ☐ Representative of broader portfolio (don't pick only urban or only suburban) ☐ Not undergoing other major changes (renovation, provider turnover, PMS migration) ☐ Regional manager actively supportive and available ☐ No upcoming holidays or major schedule disruptions during pilot period

Wave 1 Timeline

Week	Activities
Week 3	Integration setup, data sync verification, test campaigns
Week 4	Champion training, soft launch with limited budget
Week 5	Full campaign activation, daily monitoring, staff training
Week 6	Performance review, issue resolution, playbook documentation

Wave 1 Success Metrics

Metric	Target	Measurement
Integration stability	>99% uptime	Aron dashboard
Data sync accuracy	>98% match rate	PMS vs. Aron comparison
Staff training completion	100%	Training tracking
Lead attribution accuracy	>90%	Manual spot-check
Champion satisfaction	>4/5	Survey

Wave 2: Expansion (Weeks 7–12)

Wave 2 Timeline

Week	Activities
Week 7	Wave 1 retrospective, playbook updates
Week 8	Wave 2 integration setup (batch 1: 4 locations)
Week 9	Wave 2 batch 1 training and soft launch
Week 10	Wave 2 integration setup (batch 2: 4 locations)
Week 11	Wave 2 batch 2 training and soft launch
Week 12	Wave 2 full activation, monitoring

Wave 2 Efficiency Targets

By Wave 2, expect:

• Integration setup time: 50% reduction vs. Wave 1
• Training time: 30% reduction (leverage materials from Wave 1)
• Issues encountered: 60% fewer (known issues pre-addressed)

Wave 3: Full Deployment (Weeks 13–20)

Wave 3 Approach

With proven playbook and trained champions, Wave 3 moves faster:

☐ Deploy in batches of 5–7 locations per week ☐ Leverage regional managers to cascade training ☐ Champions from earlier waves support new locations ☐ Centralized war room for rapid issue resolution

Wave 3 Timeline (Example: 30 remaining locations)

Week	Locations Deployed	Cumulative
Week 13	6	6
Week 14	6	12
Week 15	6	18
Week 16	6	24
Week 17	6	30
Week 18-20	Stabilization and optimization	All 30

Go/No-Go Criteria

🟣 Criteria to Advance from Wave 1 to Wave 2

Category	Go Criteria	No-Go Trigger
Technical	Integrations stable for 5+ consecutive days	>2 hours cumulative downtime in final week
Data Quality	Lead attribution >90% accurate	<80% attribution accuracy
Staff Adoption	All staff using platform daily	>20% of staff not logging in
Champion Feedback	Net Promoter Score >6	Champion requests pause
Financial	CPL within 20% of baseline	CPL >50% above baseline
Patient Experience	No patient complaints related to platform	Any HIPAA or patient data incident

Go/No-Go Decision Meeting

🟣 Attendees: VP Operations, VP Marketing, IT Director, Regional Managers (pilot regions), Aron CSM

Agenda:

1. Wave 1 metrics review (30 min)
2. Technical stability report (15 min)
3. Champion feedback summary (15 min)
4. Issues encountered and resolutions (15 min)
5. Playbook updates for Wave 2 (15 min)
6. Go/No-Go decision (15 min)

Rollback Plan

If a Wave Fails

Immediate Actions (within 24 hours): ☐ Pause all campaigns in affected locations ☐ Revert to previous marketing workflows ☐ Notify affected location staff ☐ Document all issues in detail 🔵 ☐ Escalate to Aron engineering team

Assessment Period (24–72 hours): ☐ Root cause analysis with Aron team ☐ Determine if issue is isolated or systemic ☐ Create remediation plan with timeline 🟣 ☐ Decision: Retry wave vs. pause entire rollout

Communication: ☐ Regional manager notification within 4 hours ☐ Affected staff notification within 24 hours ☐ C-suite briefing within 48 hours

Criteria for Rollout Pause:

• Same critical issue occurs in 2+ locations
• HIPAA or data security incident
• Financial impact exceeds 2x projected budget
• Champion resignation or escalation to HR

Isolation Protocols

⚠️ Critical: Ensure issues at one location don't cascade to others

☐ Aron configuration should be location-isolated (no shared campaigns without intent) ☐ Location-specific API credentials (not shared keys) ☐ Monitoring alerts set per-location, not just aggregate ☐ Rollback capability at location level, not just wave level

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration

Dentrix Integration

🔵 Step 1: API Access Setup (Day 1-2) ☐ Contact Dentrix support to enable API access for each location ☐ Obtain API credentials and documentation ☐ Verify Dentrix version compatibility (G7.4+ recommended) ☐ Confirm eServices subscription status (required for some integrations)

⚠️ Common Issue: Dentrix API requires per-location activation; plan for 3-5 business day lead time

Step 2: Aron Connector Configuration (Day 2-3) 🔵 ☐ Provide Dentrix credentials to Aron implementation team ☐ Configure data sync parameters (patient demographics, appointments, production) ☐ Define sync frequency (real-time vs. batch) ☐ Enable new patient flag for attribution tracking

Step 3: Validation (Day 3-4) ☐ Run test patient record sync ☐ Verify appointment data flowing correctly ☐ Confirm new patient attribution mapping ☐ Test bi-directional sync (if applicable)

Eaglesoft Integration

🔵 Step 1: Patterson Technology Services Contact (Day 1-2) ☐ Request Eaglesoft API access through Patterson ☐ Complete Patterson integration agreement ☐ Verify Eaglesoft version (21.0+ recommended)

Step 2: Database Connector Setup (Day 2-3) 🔵 ☐ Aron team installs secure database connector ☐ Configure read-only access to required tables ☐ Set up secure tunnel (VPN or SSH) ☐ Define data extraction schedule

Step 3: Validation (Day 3-4) ☐ Compare Eaglesoft patient count to Aron sync count ☐ Verify appointment statuses mapping correctly ☐ Test production data accuracy ☐ Confirm insurance information sync (if using)

Open Dental Integration

Step 1: API Key Generation (Day 1) ☐ Navigate to Setup > Program Links > API in Open Dental ☐ Generate API key with appropriate permissions ☐ Document key securely (do not email) ☐ Verify Open Dental version (22.1+ recommended)

🔵 Step 2: Aron API Configuration (Day 1-2) ☐ Enter Open Dental API key in Aron admin panel ☐ Configure webhook endpoints for real-time sync ☐ Set up patient matching rules (phone, email, DOB) ☐ Enable new patient source tracking

Step 3: Validation (Day 2-3) ☐ Create test patient in Open Dental, verify appears in Aron ☐ Schedule test appointment, verify attribution ☐ Test patient matching across sources ☐ Verify HIPAA minimum necessary compliance

Marketing Platform Integrations

Google Ads Integration

Step 1: Account Access (Day 1) ☐ Add Aron service account to Google Ads MCC (or individual accounts) ☐ Grant "Standard" access level minimum ☐ Enable auto-tagging in Google Ads settings ☐ Verify conversion tracking tag manager access

🔵 Step 2: Aron Configuration (Day 1-2) ☐ Connect Google Ads account in Aron platform ☐ Import existing campaigns and structure ☐ Configure Aron optimization rules ☐ Set budget guardrails per location

Step 3: Conversion Setup (Day 2) ☐ Install Aron conversion pixel on all location websites ☐ Configure phone call tracking numbers ☐ Set up form submission tracking ☐ Define conversion values (lead value, appointment value)

Meta (Facebook/Instagram) Integration

Step 1: Business Manager Access (Day 1) ☐ Add Aron partner to Meta Business Manager ☐ Grant access to ad accounts for all locations ☐ Verify pixel installation on websites ☐ Enable Conversions API access

🔵 Step 2: Aron Configuration (Day 1-2) ☐ Connect Meta accounts in Aron ☐ Verify pixel event firing correctly ☐ Configure audience sync (if using CRM data) ☐ Set up location-specific ad account structure

Call Tracking Integration

Step 1: Existing System Assessment ☐ Inventory current call tracking numbers by location ☐ Document current call flow and routing ☐ Export historical call data for baseline

🔵 Step 2: Aron Call Tracking Setup (Day 2-3) ☐ Provision new tracking numbers (or port existing) ☐ Configure call routing rules ☐ Set up call recording (with proper disclosures) ☐ Enable AI call scoring/transcription

⚠️ Common Issue: Number porting can take 5-10 business days; plan accordingly

Step 3: Website Number Swap ☐ Implement dynamic number insertion script ☐ Update offline marketing materials (signage, direct mail) ☐ Test call routing for each location ☐ Verify call attribution in Aron

Test Environment Setup

Centralized Test Environment (Recommended)

🔵 ☐ Request Aron sandbox environment credentials ☐ Create test location that mirrors production config ☐ Load sample data (de-identified patient records) ☐ Configure test PMS connection (if available)

Validation Checklist

Test Case	Expected Result	Pass/Fail
Website lead submits form	Lead appears in Aron within 5 minutes	☐
Phone call tracked	Call logged with recording and disposition	☐
Lead converts to appointment	Appointment synced from PMS to Aron	☐
Campaign budget change	Change reflected in ad platform within 1 hour	☐
New patient shows	Attribution captured end-to-end	☐
Report generation	Accurate data across all metrics	☐
User access control	Permissions enforced correctly	☐

Data Migration

Historical Data Ingestion

☐ Export 12-24 months of historical marketing data ☐ Format data per Aron import specifications 🔵 ☐ Submit data to Aron for ingestion ☐ Validate historical data appears correctly in dashboards ☐ Reconcile totals with source systems

Data Mapping Document

Create mapping document showing:

• Source system field → Aron field
• Data transformation rules
• Default values for missing data
• Exception handling procedures

Security & HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

🔵 ☐ Business Associate Agreement (BAA)

• Verify BAA covers all Aron services
• Confirm BAA addresses subcontractors
• Document BAA execution date and signatories

☐ Data Governance

• Document what PHI Aron accesses (minimum necessary)
• Confirm data encryption at rest and in transit
• Verify data retention and destruction policies
• Document data subject access request (DSAR) procedures

☐ Access Controls

• Implement role-based access control (RBAC)
• Enable audit logging for all PHI access
• Configure session timeout (15 minutes recommended)
• Implement MFA for all admin accounts

☐ Security Assessment 🔵 - Request Aron SOC 2 Type II report 🔵 - Review Aron penetration test results

• Document any compensating controls required
• Complete vendor security questionnaire

☐ Incident Response 🔵 - Document Aron breach notification procedures

• Establish joint incident response protocol
• Test incident communication pathway

Standardized vs. Location-Specific Configuration

Standardized Configuration Template

Settings that MUST be identical across all locations:

Setting	Standard Value	Rationale
Conversion tracking events	Form, call, chat, appointment	Consistent measurement
Attribution window	30-day click, 1-day view	Cross-location comparison
Lead quality scoring model	Aron default + DSO customization	Standardized lead value
Reporting date ranges	Calendar month	Executive reporting
Budget alert thresholds	90% and 100% of monthly budget	Financial controls
User permission levels	Admin, Manager, Viewer	Governance
Brand guidelines	Approved ad templates	Brand consistency
Call tracking settings	Recording on, AI scoring on	Quality assurance

Location-Specific Configuration

Settings that CAN/SHOULD vary by location:

Setting	Why Location-Specific
Monthly budget	Market size, growth goals
Geographic targeting	Local service area