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
| Account | Phone | Password | Use Case | |
|---|---|---|---|---|
| Test Admin 1 | testadmin1@symphonycore.com | +1 475-323-6801 | Testadmin1@ | Primary testing, admin-level tests |
| Test User 1 | testuser1@symphonycore.com | — (see note) | Testuser1@ | Standard user testing |
| Test User 2 | testuser2@symphonycore.com | (none) | Testuser2@ | Email-only testing |
Test User 1 no longer has a phone number.
+1 475-323-6565was listed here until 2026-10-29, when it was reassigned as the inside-sales caller's live prospecting line. Do not use it for testing — it places real calls to real prospects and carries its own reputation. Current roles for every Symphony Core number are in the SC Phone Number Register.
Test Address
For address-required forms and location testing:
1204 Main St #921
Branford, CT 06405
Google Groups Access
Each test account has an associated Google Group for email access:
| Account | Group URL |
|---|---|
| testadmin1 | https://groups.google.com/a/symphonycore.com/g/testadmin1 |
| testuser1 | https://groups.google.com/a/symphonycore.com/g/testuser1 |
| testuser2 | https://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
- Always use test accounts - Never use personal or client contact info for testing
- Clean up after testing - Delete test contacts from client sub-accounts after QA
- Check both channels - Verify SMS and email delivery when testing automations
- Use incognito mode - Test funnels in incognito/private browser windows
- Document results - Note any issues found during testing in the client task list
Calendar Booking Tests
When testing calendar funnels:
- Book appointment using test account email/phone
- Verify confirmation SMS and email received
- Check appointment appears in GHL calendar
- Verify reminder workflows trigger at correct times
- Cancel test appointment after verification
Form Submission Tests
When testing lead forms:
- Submit form with test account details
- Verify contact created in GHL CRM
- Check source tagging applied correctly
- Verify initial response automation triggers
- Delete test contact after verification
Related Documents
Revision History
| Date | Version | Change Description | Author |
|---|---|---|---|
| 2026-10-29 | 1.2 | Test User 1 loses its phone number. +1 475-323-6565 was reassigned as the inside-sales caller's live prospecting line, so it must not be used for testing — it places real calls to real prospects and carries its own reputation. The cell is cleared and a note points at the SC Phone Number Register | Symphony Core Systems Team |
| 2025-12-19 | 1.0 | Initial version | Symphony Core Systems Team |