Skip to main content

Symphony Core Team Ways of Working

Purpose​

How everyone at Symphony Core works together, whatever the role and however they are engaged. Read it on your first day. It is short on purpose: where a topic has its own standard, this page points to it rather than repeating it.

Applies to: employees, direct contractors, and people placed with us by an agency or vendor. Role-specific practice (how to run a sales call, how to build a website) lives in your role's onboarding, not here.


1. Where things go​

ChannelUse it forDo not use it for
SlackDay-to-day conversation, questions, your daily updateDecisions that need to be found again later. Put those in the ticket
ClickUpThe work itself: tasks, status, evidence, decisions on a taskChat. Comment on the task instead of messaging about it
WhatsAppTime-sensitive only: you cannot start your shift, a system is down, something is urgent todayRoutine updates, files, anything that needs tracking
EmailExternal parties, and anything formalInternal back-and-forth

If it is not in Slack or ClickUp, it did not happen. A decision made on a call or in WhatsApp is written into the ticket or the Slack thread the same day.

How tickets work: ClickUp Ways of Working.


2. Responsiveness and the daily rhythm​

ExpectationStandard
Slack reply during your shiftWithin 2 working hours. If you cannot answer fully, acknowledge and say when you will
Daily updateA short written update in Slack at the end of each working day: what you did, what is next, what is blocking you
AbsenceAt least 24 hours' notice of planned time off. For unplanned absence, message before your shift starts
BlockedSay so as soon as you are blocked. Do not wait for the daily update

Hours and time zones. Your working hours are agreed when you start and recorded in your profile. Due dates are always in US Eastern time unless a ticket says otherwise.


3. How we talk about the platform​

Clients and prospects use our platform at app.symphonycore.com. With anyone outside Symphony Core:

  • Never say "GHL", "GoHighLevel" or "HighLevel". Say "your CRM", "the platform" or "app.symphonycore.com".
  • The mobile app is "the Lead Connector app".

Inside the team, "GHL" is fine. Full rule: Internal Reference.


4. Confidentiality and data​

You will see client and prospect information. Treat all of it as confidential, during your engagement and after it ends.

  • Work only with what you were given. Access is scoped to your role. If you can see something outside it, such as a client record in a list meant for prospects, leave it alone and tell your manager.
  • Data stays in our systems. No exports, downloads or copies to personal devices, personal accounts, or AI or productivity tools we have not approved.
  • Credentials stay private. Turn on two-factor authentication wherever it is offered. Never share a password in Slack, WhatsApp or email. If you need a shared credential, ask, and it will be shared through 1Password.
  • Speak for Symphony Core only as your role allows. Do not make promises about pricing, contracts or deliverables unless your role covers it.

5. When something goes wrong​

Raise it with your manager in Slack. Use these four lines; they get an answer faster than a description:

  1. What you were doing.
  2. What you checked.
  3. What you think is happening.
  4. What you would do.

If it cannot wait two hours — you cannot work, a system is down, a client or prospect is upset — use WhatsApp as well.


6. If an agency or vendor employs you​

Some team members are employed by an agency and placed with Symphony Core. If that is you:

  • Your employer handles your pay, contract, equipment and leave. Your check-ins and any shift or End of Duty reports they ask for go through their channels.
  • Symphony Core directs the work. Tasks, questions, decisions and the daily update stay in Symphony Core's channels (§1), even when your employer's group chat includes us.
  • Tell both when you will be absent.
  • Questions about pay or your contract go to your employer, not to Symphony Core.


Access Level: internal-team

Revision History​

VersionDateChanges
1.02026-10-27Initial version: channels, response standards, platform naming, confidentiality, escalation, vendor-placed team members