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.
So the specialist can start it immediately, with no follow up questions.
| Field | What to put | Why it matters |
|---|---|---|
| Client / account | Exact 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 type | Pick one: Form connection, Form edit, Workflow, Notification email, New sub-account, Other | Tells the specialist which checklist applies |
| What / outcome | One sentence: what should be true when this is done | Removes guesswork about scope |
| Assets / links | The live URL, form link, ad link, or screenshot the task refers to | "The form" is not findable, a link is |
| Notify who | Full name and email address of anyone who should get lead alerts | Missing email stalls the task, every time |
| Priority / deadline | Urgent, This week, or No rush, plus any hard date | Lets the specialist sequence correctly |
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:
If any answer is no, the ticket is not ready.
A campaign cannot be scheduled without send dates.
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.
| Field | What to put | Why it matters |
|---|---|---|
| Client / account | Exact business name as it appears in the CRM | Sends to the wrong list are hard to undo |
| Campaign name | A clear internal name, for example "June 2026 Newsletter" | Keeps the Library organized |
| Send date + time | Exact date and time for each email, including time zone | This is the field that was missing. Without it nothing can be scheduled. |
| Recipient list / segment | Which contact list or segment receives it | Determines who gets the email |
| Subject line | The exact subject line text | Part of the email, not optional |
| Preview / preheader text | The short line shown after the subject | Improves open rates |
| Email copy | Full body copy, final and approved | What actually sends |
| From name + reply-to | The sender name and reply address | Controls how it appears in the inbox |
| Links / CTAs | Every button or link URL used in the copy | Broken or missing links delay the send |
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.):
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 name | Subject line | Send date + time |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 |
If any answer is no, the request is not ready.
Every new client gets a sub-account. This is the info we need and the steps that follow.
| Field | What to put | Why it matters |
|---|---|---|
| Business name | Full 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 name | First and last name of the primary account owner | Shows on the account and in the welcome email GHL sends automatically |
| Owner email | The email address the owner actively checks | GHL sends a welcome/setup email here on creation. Wrong email means the owner never gets access. |
| Phone | Main business phone number | Stored on the account for caller ID and notifications |
| Address | Full street address, city, state, ZIP | Required by GHL for location setup and A2P registration |
| Website | The business website URL | Used for branding and reference |
| Timezone | The client's timezone (e.g. "Eastern", "Central", "Pacific") | Controls when scheduled messages and workflows fire. Defaults to Eastern if not specified. |
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:
If any answer is no, the ticket is not ready.