FireRock Marketing · Internal

FireRock Internal SOP

Standard operating procedures for creating tickets, submitting campaign requests, and setting up new client accounts. Follow these so every request can be started without back and forth.

1. How to Create a Task

So the specialist can start it immediately, with no follow up questions.

The one rule: every ticket must answer four things before you hit Create. Which client, What to do, Why or the goal, and Where the assets are. If a ticket cannot answer all four, it is not ready to submit.

Required fields (every ticket, no exceptions)

FieldWhat to putWhy it matters
Client / accountExact business name as it appears in the CRM, for example "D&C Home Care", not "the home care one"Same work in the wrong sub-account is wasted and risky
Task typePick one: Form connection, Form edit, Workflow, Notification email, New sub-account, OtherTells the specialist which checklist applies
What / outcomeOne sentence: what should be true when this is doneRemoves guesswork about scope
Assets / linksThe live URL, form link, ad link, or screenshot the task refers to"The form" is not findable, a link is
Notify whoFull name and email address of anyone who should get lead alertsMissing email stalls the task, every time
Priority / deadlineUrgent, This week, or No rush, plus any hard dateLets the specialist sequence correctly

Copy-paste ticket template

Paste this into the description of every new ticket and fill each line. Write "N/A" if a line truly does not apply.

Client / account:
Task type:
What should happen (one sentence):
Why / goal:
Asset link(s) or screenshot:
Notify (name + email):
Priority / deadline:
Extra notes:

Task-type add-ons (include on top of the template)

Good vs bad (same request)

Bad, bounces back "Connect the FB form to the CRM."
Good, starts immediately Client: D&C Home Care
Task type: Facebook Lead Form
What: New Facebook leads flow into the CRM and tag as FBLEAD
Asset: Page "D&C Home Care", form "Careers Aug 2026", ad is Active
Notify: Laurence Smith, laurence@dchomecare.com
Priority: This week

Before you click Create (10-second check)

  1. Did I name the exact client?
  2. Did I paste a link or screenshot of the asset?
  3. Did I give a full email address for notifications?
  4. Would someone who has never seen this account know what to do?

If any answer is no, the ticket is not ready.

2. How to Submit a Zoho Email Campaign Request

A campaign cannot be scheduled without send dates.

The one rule: a campaign request is not ready until it has both the copy AND the send schedule. Copy alone cannot be scheduled, so a doc with no dates stalls the campaign every time.

Why this exists

The last campaign docs contained the email copy only. No send dates were provided, so the campaign could be built into the Library as a template but could not be scheduled to go out. Every campaign request from now on must include when it should send.

Required fields (every campaign request)

FieldWhat to putWhy it matters
Client / accountExact business name as it appears in the CRMSends to the wrong list are hard to undo
Campaign nameA clear internal name, for example "June 2026 Newsletter"Keeps the Library organized
Send date + timeExact date and time for each email, including time zoneThis is the field that was missing. Without it nothing can be scheduled.
Recipient list / segmentWhich contact list or segment receives itDetermines who gets the email
Subject lineThe exact subject line textPart of the email, not optional
Preview / preheader textThe short line shown after the subjectImproves open rates
Email copyFull body copy, final and approvedWhat actually sends
From name + reply-toThe sender name and reply addressControls how it appears in the inbox
Links / CTAsEvery button or link URL used in the copyBroken or missing links delay the send

Copy-paste campaign request template

Paste this into the request doc or ticket and fill every line. Write "N/A" only if a line truly does not apply.

Client / account:
Campaign name:
Send date + time (with time zone):
Recipient list / segment:
Subject line:
Preview / preheader text:
From name:
Reply-to email:
Links / CTAs (label + URL):
Email copy:
Notes (A/B test, follow-up sends, etc.):

For a multi-email sequence

If the campaign is more than one email (a series or drip), give the schedule as a table so each send has its own date.

#Email nameSubject lineSend date + time
1
2
3

Good vs bad (same request)

Bad, cannot be scheduled "Here's the copy for the newsletter." (copy only, no dates)
Good, ready to schedule Client: [account name]
Campaign: June 2026 Newsletter
Send: June 18, 2026, 9:00 AM ET
List: All active subscribers
Subject: Your June update is here
Preview: What's new this month
From: [name] / Reply-to: [email]
Copy: [full approved body]

Before you submit (10-second check)

  1. Did I include a send date and time for every email?
  2. Did I name the recipient list?
  3. Is the copy final and approved (not a draft to be edited later)?
  4. Are all links in the copy present and correct?

If any answer is no, the request is not ready.

3. How to Request a New GHL Sub-Account

Every new client gets a sub-account. This is the info we need and the steps that follow.

The one rule: the specialist cannot create the account until the business name, owner email, and address are confirmed. Missing any of those three means the request sits until they are provided.

Required info (provide all of these in the ticket)

FieldWhat to putWhy it matters
Business nameFull legal name exactly as it should appear in the CRM (e.g. "Kinetic Marine Solutions")This becomes the sub-account name. Fixing it later requires support.
Owner nameFirst and last name of the primary account ownerShows on the account and in the welcome email GHL sends automatically
Owner emailThe email address the owner actively checksGHL sends a welcome/setup email here on creation. Wrong email means the owner never gets access.
PhoneMain business phone numberStored on the account for caller ID and notifications
AddressFull street address, city, state, ZIPRequired by GHL for location setup and A2P registration
WebsiteThe business website URLUsed for branding and reference
TimezoneThe client's timezone (e.g. "Eastern", "Central", "Pacific")Controls when scheduled messages and workflows fire. Defaults to Eastern if not specified.

Copy-paste ticket template

Paste this into the ticket description and fill every line.

Client / account: [new]
Task type: New sub-account
Business name:
Owner name:
Owner email:
Phone:
Address (street, city, state, ZIP):
Website:
Timezone:
Priority / deadline:
Extra notes:

What happens after you submit

  1. Account created. The specialist creates the sub-account in GHL under the FireRock agency.
  2. Snapshot applied. The standard FireRock automation snapshot is imported automatically. This takes about 5 to 10 minutes to finish loading.
  3. Welcome email sent. GHL sends a setup email to the owner's email address. The owner uses this to set their password and log in for the first time.
  4. Confirmation. The specialist confirms the account is active and reports back with the account name and any next steps.

Good vs bad (same request)

Bad, cannot start "Set up a GHL account for the new roofing client."
Good, starts immediately Client: [new]
Task type: New sub-account
Business name: Kinetic Marine Solutions
Owner: Greg Boehmcke, gregb@kineticmarinesolutions.com
Phone: (617) 777-0275
Address: 500 E Broward Blvd 9th Floor, Fort Lauderdale, FL 33394
Website: kineticmarinesolutions.com
Timezone: Eastern
Priority: This week

After the account is live (account manager checklist)

  1. Confirm the owner received the GHL welcome email and can log in.
  2. Verify the business name, phone, and address look correct in the sub-account settings.
  3. If the client needs a custom domain, Facebook integration, or phone number, create a follow-up ticket for each. Those are separate tasks.

Before you submit (10-second check)

  1. Did I include the full legal business name?
  2. Did I include the owner's email (not just their name)?
  3. Did I include the full address with city, state, and ZIP?
  4. Would someone who has never spoken to this client have everything they need?

If any answer is no, the ticket is not ready.

Copied to clipboard