Skip to main content

Symphony Core Test Accounts

Purpose​

Standard test accounts for QA testing across all client implementations. Use these accounts for testing funnels, forms, calendars, SMS, email delivery, and automation workflows.

Test Accounts​

AccountEmailPhonePasswordUse Case
Test Admin 1testadmin1@symphonycore.com+1 475-323-6801Testadmin1@Primary testing, admin-level tests
Test User 1testuser1@symphonycore.com+1 475-323-6565Testuser1@Standard user testing
Test User 2testuser2@symphonycore.com(none)Testuser2@Email-only testing

Test Address​

For address-required forms and location testing:

800 Main St S
Southbury, CT 06488

Google Groups Access​

Each test account has an associated Google Group for email access:

AccountGroup URL
testadmin1https://groups.google.com/a/symphonycore.com/g/testadmin1
testuser1https://groups.google.com/a/symphonycore.com/g/testuser1
testuser2https://groups.google.com/a/symphonycore.com/g/testuser2

Usage Guidelines​

When to Use Each Account​

  • testadmin1: Use for primary testing when both email AND SMS verification needed
  • testuser1: Use for secondary testing or when testing multi-user scenarios
  • testuser2: Use for email-only tests (no phone number associated)

Testing Best Practices​

  1. Always use test accounts - Never use personal or client contact info for testing
  2. Clean up after testing - Delete test contacts from client sub-accounts after QA
  3. Check both channels - Verify SMS and email delivery when testing automations
  4. Use incognito mode - Test funnels in incognito/private browser windows
  5. Document results - Note any issues found during testing in the client task list

Calendar Booking Tests​

When testing calendar funnels:

  1. Book appointment using test account email/phone
  2. Verify confirmation SMS and email received
  3. Check appointment appears in GHL calendar
  4. Verify reminder workflows trigger at correct times
  5. Cancel test appointment after verification

Form Submission Tests​

When testing lead forms:

  1. Submit form with test account details
  2. Verify contact created in GHL CRM
  3. Check source tagging applied correctly
  4. Verify initial response automation triggers
  5. Delete test contact after verification

Revision History​

DateVersionChange DescriptionAuthor
2025-12-191.0Initial versionSymphony Core Systems Team