Academy / WAM & Creating Sync Apps / Creating a Slug — Simulating Office Onboarding

Creating a Slug — Simulating Office Onboarding

Lesson 4.2 ⏱ ~8 min

💡 Why This Matters

Creating test offices is something you'll do frequently for development and testing. Every new PMS integration or feature test starts with spinning up a fresh location. Knowing this process end-to-end is a core skill.

🎯 What You'll Learn

  • How to create a new location in WAM using the green '+' icon
  • What fields are required: location name, slug, vertical (dental/vet/etc.), office email
  • The role of Salesforce Account ID in real onboarding (vs. leaving it blank for dev purposes)
  • What happens after creation: a unique LocationId is assigned, a WAM page is created
  • How to compare a newly created (empty) WAM location to an established one with a running SyncApp

Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

Creating a new location in WAM simulates onboarding a new customer. Click the green '+', select 'Dev location', fill in the location name, slug (human-readable URL identifier), vertical (e.g., dental), and email. Salesforce Account ID is required in production but can be left blank for dev testing (will show errors but proceed). After creation, a unique LocationId is assigned and the location appears in WAM. The new location will have no data sources, no SyncApps, and no patients — exactly what you'd expect before any integration is configured.

🏷 Key Concepts

Creating a Location in WAM Slug Location Name Vertical (Dental/Vet/Medical) Salesforce Account ID LocationId Assignment Dev vs. Production Location

Key Takeaways

01Every new office onboarding starts with creating a location in WAM — this is step zero
02Slug is the human-readable identifier you'll use constantly in your daily work
03For dev/test purposes, you can skip the Salesforce ID — the location will still be created
04A freshly created location has zero data sources and zero SyncApps — that's the expected empty state
05Keep your dev location slugs descriptive (e.g., dev-kt-video-infinite-vt) to avoid confusion