Implementation Journey
In this article you'll find a detailed step-by-step of a ticket through the Implementation process.
Onboarding Pipeline
New Client
This is the very first step of the client's project journey. Whenever the Sales team moves the Deal to the "Closed Won" status, a ticket for the "Onboarding Pipeline" will be created.- When the ticket enters the "New Request" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Assign OB Specialist" | Onboarding Lead |
| ✏️ Task: "QA HubSpot Company & Contact" | Intern |
| ✏️ Task: "Create WhatConverts Profile" | Intern |
- The Onboarding Lead will assign the ticket to an OB Specialist by updating the property field "OB Specialist", once this property field is known, the following actions will be triggered:
| Action | Assignee |
| ✏️ Task: "Create Slack Channel" | Onboarding Specialist |
| ✏️ Task: "Create Folder in MOBY" | Onboarding Specialist |
OB Form Sent
- Once the OB Form has been emailed to the client, the OB Specialist will manually drag the ticket to the "OB Form Sent" status.
OB Form Received
- Once the OB Form has been received, the OB Specialist will manually drag the ticket to the "OB Form Received" status.
- When the ticket enters the "OB Form Received" status, the following actions are triggered:
| Action | Assignee |
| 🗒️ Ticket: "Creative Pipeline (Web)" | Owner: Creative Lead |
Required Fields
- Onboarding Form: Attach the PDF file.
- Starting Project Type:
- Expected Due Date:
Optional Fields
- Digital Marketing URL:
- Design Theme:
Intro Call Scheduled
After receiving the OB Form, the OB Specialist will:
- Contact the client and schedule the meeting.
- Announce in the client's slack channel the "Intro Call" has been scheduled.
- Manually update the status to "Intro Call Scheduled"
Required Fields
- Is the client doing mail?
- The following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Update "Onboarding Data Checklist" Property Field" | OB Specialist / Ticket Owner |
- If the property field "Is the client doing mail?" status is updated to "Yes", the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "New Client Onboarding - Create Mail Plan" | Direct Mail CSM |
- When the property field "Mail Plan File" is known, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Share Onboarding Mail Plan" | Ticket Owner / Onboarding Specialist |
Web Project Started
- Once all the assets have been collected and provided in the "Canvas" of the Slack channel for the project, the OB Specialist will manually drag the ticket to "Web Project Started".
- The OB Ticket will stay in this status during the whole buildout of the "Starting Project Type"
Required Fields
- Design Theme:
Optional Fields
- Focused Google Ads Services:
🏁 Copy Property
When the property "Design Theme" is known, the property will be copied to the Company associated.
Pending Domain Access
This status should be used if there are any roadblocks preventing us from verifying domain access. The ticket should be moved to 'Domain Access Verified' only after we have successfully done so
Domain Access Verified
Required Fields
- Digital Marketing URL
- Domain Registrar
- Domain Name Servers
- Domain Registrar Username
- Domain Registrar Password
- Domain Notes
- Digital Marketing URL:
The web address used for all marketing activities. - Domain Registrar:
The company responsible for registering and managing the domain name. - Domain Name Servers:
The servers that translate your domain name into an IP address, allowing users to access your website by its domain name rather than the numerical IP address. - Domain Registrar Username:
The username used to log in to the domain registrar account, giving one access to manage your domain settings and configurations. - Domain Registrar Password:
The secure password required to access your domain registrar account, ensuring only authorized users can manage your domain. - Domain Notes:
Any additional notes that are relevant.
Note: If the access was not provided, please fill this with " Client this"
Possible Scenarios
|
Fill all properties with "N/A". In "Domain Notes", write: "Client did not provide access to the domain - upon launch process please contact OB to contact the client. " |
|
Fill all properties with "N/A - Access Delegated". Fill "Domain Registrar Username" with the name of the account. |
🏁 Copy Property
- When the property field "Digital Marketing URL" is known, the property will be copied to the Company associated.
- When the property fields related to Domain Access are known, the property will be copied to the Company associated.
- The following action will be triggered:
| Action | Assignee |
| ✏️ Task: "Add domain to Google Search Console" | Creative Lead |
Project Sent for Approval
- When the Starting Project's soft launch is announced in the Slack channel (#soft-launch), the client is emailed the preview and Pastel link to review the project, once that is done the ticket should be updated manually to "Project Sent for Approval".
Client Edits
- If the client requests edits during the Soft Launch Process, the ticket should be dragged to "Client Edits".
Required Fields
- Pastel Link
- Range of Client Edit Numbers in Pastel
- Once the status has been updated to "Client Edits" the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Client Edits - New Launch" | Creative Lead* |
* Task will be reassigned based on workload.
- Once the Web Dev has finalized the edits, the property field "Web Designer - Are All Client Edits in Soft Launch Completed?" will be updated to "Yes" and the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "QA Client Edits (Web)" | Creative Lead |
🏁 Ticket Status Update to "QA Client Edits"
When the property field equals "Yes"
- Web Designer - Are All Client Edits in Soft Launch Completed?
QA Client Edits
- The Creative Lead will QA and request any necessary adjustments, once the request has successfully completed, the Creative Lead will manually update the status to "Ready To Share" and the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "QA Client Edits (Web)" | Creative Lead |
Ready To Share
- When the ticket enters the "Ready to Share" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Notify Client - Web Edits Completed" | OB Specialist / Ticket Owner |
| ⚡ Clear Property Value "Web Designer - Are All Client Edits in Soft Launch Completed?" | |
A cycle will begin in these three stages:
- Client Edits
- QA Client Edits
- Ready to Share
Once the project is 100% approved, the OB Specialist will manually update the ticket status to "Wooflyance"
Wooflyance
- When the ticket enters the "Wooflyance" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Send Project to Wooflyance" | Creative Lead |
- For more information on the actions here, check the "Creative Pipeline (Web) Wooflyance" Status.
Project Launched
- Once the site launch is announced in the Slack Channel #splash, the OB Specialist will manually update the ticket status to "Project Launched" and the following actions will be triggered:
| Action | Assignee |
| ✏️ Task: "Submit Billing Adjustment - New Launch" | OB Specialist / Ticket Owner |
| ⚡ Copy Property Values to Company | |
| 🗒️ Ticket: "Home Page LP" / "Final Project" Ads Launch* | Paid Marketing Lead |
* If it is not a Final Project, the Ads Launch will be triggered from the "Creative Pipeline (Web)"
Required Fields
- Is this a starting project?
- Focused Google Ads Services
- Google Ad Budget
Optional Fields
- Facebook Ad Buget
- Ads Live Date
Final Web Proj Started
- Once the tasks for "Project Launched" are completed, the OB Specialist will manually update the status to "Final Web Proj Started". No actions are triggered here.
- Based on the SEO Analysis of the pre existing website, the Creative Lead will announce the expected due date for the final project in the Slack channel of the client.
Required Fields
- Starting Project Splash Date
- Final Project Type
- Focused Ads Services
Final Proj Sent for Approval
- Once the Final Project is announced in the #soft-launch Slack channel, and the OB Specialist has sent the project for approval, the ticket will be manually updated to this status. The ticket should remain here until any feedback is provided.
Final Proj Client Edits
- If the client sends any edit requests, the OB Specialist will manually update the ticket status to "Final Proj Client Edits" and the following actions will be triggered:
| Action | Assignee |
| ✏️ Task: "Client Edits - New Launch" | Creative Lead* |
* Task will be reassigned based on workload.
Required Fields
- Pastel Link
- Range of Client Edit Numbers in Pastel
- Once the Web Dev has finalized the edits, the property field "Web Designer - Are All Client Edits in Soft Launch Completed?" will be updated to "Yes" and the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "QA Final Proj Web Edits (Web)" | Creative Lead |
| ⚡ Clear value for: "Web Designer - Are All Client Edits in Soft Launch Completed?" |
🏁 Ticket Status Update to "QA Final Proj Client Edits"
When the property field equals "Yes"
- Web Designer - Are All Client Edits in Soft Launch Completed?
QA Final Proj Client Edits
- The Creative Lead will QA and request any necessary adjustments, once the request has successfully completed, the Creative Lead will manually update the status to "Final Proj Client Edits Ready To Share" and the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "QA Client Edits (Web)" | Creative Lead |
Final Proj Client Edits Ready to Share
When the ticket enters the "Final Proj Client Edits Ready to Share" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Notify Client That Their Edits Are Ready to Review" | OB Specialist / Ticket Owner |
| ⚡ Clear Property Value "Web Designer - Are All Client Edits in Soft Launch Completed?" | |
A cycle will begin in these three stages:
- Final Proj Client Edits
- QA Final Proj Client Edits
- Final Proj Client Edits Ready To Share
Once the project is 100% approved, the OB Specialist will manually update the ticket status to "Final Project Wooflyance"
Final Project Wooflyance
- When the ticket enters the "Wooflyance" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Send Project to Wooflyance" | Creative Lead |
- For more information on the actions here, check the "Creative Pipeline (Web) Wooflyance" Status.
Final Proj Launched
When the ticket enters the "Final Proj Launched" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Submit Billing Adjustment - Final Launch | OB Specialist (Ticket Owner) |
Note:
The task to update Ads Campaign URLs for Final Projects is triggered from the "Creative Pipeline (Web)".
Closed
Final status for all completed projects.
Required Fields
- Ready for Citation Bursts?
- When the property "Ready for Citation Bursts?" is updated to "Yes", the following actions will be triggered:
| Action | |
| 🏁 Copy Property | Ready for Citation Bursts?" to the Company |
| ✏️ Task: "Submit Task for Citation Bursts to HyperTask for new client" | CSM / Company Owner |
Closed - Lost (Back to Sales)
This status is used for any client sale that is dropped/lost during the OB process. The OB Specialist will move it manually and announce it in the Slack channel created for the project.
On Hold
This status is used if there are any road blocks or the client is unsure to proceed with the deal agreement.
The OB Specialist should update the "Ticket Description" with any necessary notes explaining the "Hold" reason.
Required Fields
- Ticket Description
Creative Pipeline (Web)
New Request
Whenever the Onboarding team moves their ticket to the "OB Form Received" a ticket for the "Creative Pipeline (Web)" will be created.
When the ticket enters the "New Request" status, the following actions are triggered, based on this possible scenarios by project type:
|
Scenario |
Action |
Assignee |
|
✏️ Task: "Buildout | Coming Soon LP"* |
Creative Lead |
|
✏️ Task: "Create Call Tracking # and Update WhatConverts Script" ✏️ Task: "Create Typeform" ✏️ Task: "Add Ticket Property Fields" |
Content Creator |
|
✏️ Task: "Create Content Outline Task" |
Content Creator |
|
✏️ Task: "Create SEO Analysis" |
Content Creator |
- When the property field "SEO Analysis" is known, the following action is triggered:
| Action | Assignee |
| ✏️ Task: "SEO Analysis & Expected Due Date Review/Expectation" | Creative Lead |
- When the property field "Digital Marketing URL" is known, the following action is triggered:
| Action | Assignee |
| ✏️ Task: "Create GTM" | Paid Search Marketing Lead |
Send to Buildout
When the ticket enters the "Send to Buildout" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Buildout Setup" | Creative Lead |
- The Create Lead will create the "QA Checklist" and add to the property field "QA Checklist Link"
- Drag the ticket to "Buildout Phase 1"
- Based on workload and priorities will update the "content" and "buildout" task date, and finally assign the "buildout" task to a web developer.
Buildout Phase 1
- When the ticket enters the "Buildout Phase 1" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Create Content Document" | Content Creator |
| ✏️ Task: "Buildout | Design" |
Creative Lead* |
| ✏️ Task: "Create 12 Blog Posts" |
Content Creator** |
* Task will be reassigned based on workload.
** This will be created only for Full Sites (FS Startups, FS No Home Page and FS Refresh)
- Once the the web developer completes the design of the project, the property field "Pastel Link" will be updated and the following action will be triggered:
| Action | Assignee |
| ✏️ Task: "Design Approval" | Creative Lead |
| 🗒️ Ticket: "Open Now Setup" | Technology - Ignacio B. |
- If the design is not approved, the Creative Lead will update the property field "Design Approved" to "No" and the following action will be triggered:
| Action | Assignee |
| ✏️ Task: "Design Edits" | Creative Lead* |
* Task will be reassigned to owner of the Design task.
🏁 Ticket Status Update
When both property fields are known:
- Content Document
- Design Approved
The ticket will be updated to "Buildout Phase 2"
Buildout Phase 2
- When the ticket enters the "Buildout Phase 2" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Upgrade Hosting Plan" | Creative Lead |
| ✏️ Task: "Buildout | Data Entry" | Creative Lead |
| ✏️ Task: "Buildout | Graphics Entry" | Web Dev - Daniel R. |
| ✏️ Task: "SEO Compliance Task"* | Content Creator |
*Task created once the property field "Data QA Checklist Completed" is "Yes"
🏁 Ticket Status Update to "Compliance"
When both property fields are known:
- Data QA Checklist Completed
- Photography QA Checklist Completed
Compliance
- When the ticket enters the "Compliance" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Content Compliance" | Compliance Lead |
- If there are compliance edits, the Compliance Lead will update the property field "Content Compliance Edits" to "Yes" and the following action will be triggered:
| Action | Assignee |
| ✏️ Task: "Content Compliance Edits" | Creative Lead* |
* Task will be reassigned to owner of the Data Entry task.
- The web developer will work on the edits request and once completed, the web developer will update the "Content Compliance Edits" to "No" and the following action will be triggered:
| Action | Assignee |
| ✏️ Task: "UX Compliance" | Compliance Lead / Compliance Team Member |
- If there are UX compliance edits, the Compliance Lead will update the property field "UX Compliance Edits" to "Yes" and the following action will be triggered:
| Action | Assignee |
| ✏️ Task: "UX Compliance Edits" | Creative Lead* |
* Task will be reassigned to owner of the Design task.
🏁 Ticket Status Update to "Last Review"
When both property fields are updated to "No"
- Content Compliance Edits
- UX Compliance Edits
Last Review
- When the ticket enters the "Last Review" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "Last Review" | Creative Lead |
- If there are "Last Review edits", the Creative Lead will update the property field "Last Review Edits" to "Yes" and the following action will be triggered:
| Action | Assignee |
| ✏️ Task: "Last Review Edits" | Creative Lead* |
* Task will be reassigned to owner of the Design task.
- Once the final review edits are completed, the Creative team will review and manually create a task for the Implementation team for the "Final Look."
- If there are any further edits, the Implementation Lead will mark the "Last Review Edits" as incomplete and update the due date.
- This cycle will continue until the project complies with all requested edits.
Soft Launch
- When the ticket enters the "Soft Launch" status, the following actions are triggered:
| Action | |
| 🔈 Slack Notification | #soft-launch |
| 🗒️ Ticket: "Final Project" | Owner: Creative Lead |
| ✏️ Task: "Ready for Soft Launch - QA & Share" | Ticket Owner |
- At this status the project management will go back to the Onboarding Pipeline:
- "Project Sent for Approval" for Starting Project Type "Home Page LP"
- "Final Proj Sent for Approval" for all projects that have a finaly project type or full sites with no home page LP and refresh.
- It's is the Creative Lead to announce the expected due date based on the soft-launch date and SEO Analysis review.
Required Fields
- Soft Launch Date
- Webflow Temporary Link
- Pastel Link
Optional Fields
- Final Project Type
- Close date
🏁 Ticket Status Update to "Wooflyance"
- For this status change, the Creative Lead will need to manually drag the ticket once assigned the task created from the OB Pipeline.
Closed - Wooflyance
- When the ticket enters the "Wooflyance" status, the following actions are triggered for Starting Projects:
| Action | |
| 🔈 Slack Notification | #wooflyance |
| 🗒️ Ticket: "Launch" | Owner: Technology |
- When the ticket enters the "Wooflyance" status, the following actions are triggered for Final Projects:
| Action | Assignee |
| ✏️ Task: "Update Home Page for Final Project to Go Live" | Creative Lead* |
- Once the project has been updated to the final project, the web developer will update the property field "Main Home Page Updated" to "Yes", the following actions are triggered:
| Action | |
| 🔈 Slack Notification | #wooflyance |
| 🗒️ Ticket: "Launch" | Owner: Technology |
Required Fields
- Digital Marketing URL
Post Launch
- When the ticket enters the "Post Launch" status, the following actions are triggered:
| Action | Assignee |
| ✏️ Task: "WhatConverts Tracking Compliance" | Paid Search Marketing Analyst |
| ✏️ Task: "GMB Optimization" | Paid Search Marketing Analyst |
| ✏️ Task: "Post Launch Compliance" | Creative Lead / Compliance Lead |
| ✏️ Task: "QA/Add Full Site to Google Search Console" | Creative Lead / Compliance Lead |
| ✏️ Task: "Create Website Live Pastel Link" | Compliance Team Member |
| ✏️ Task: "QA & Schedule Blog Posts Monthly" | Compliance Team Member |
| ✏️ Task: "Setup Typeform Email Automations" | Compliance Team Member |
- Additionally, if the Final Project Type is known, the following action will be triggered:
| Action | Assignee |
| ✏️ Task: "Update Ad URLs" | Paid Search Marketing Lead |
Closed - Lost
This status is used for clients that were lost in the onboarding process.
Closed
Final status for all completed projects.
Trade Desk Pipeline
New
- When the ticket enters the "New" status, the following actions are triggered based on conditions established based of the task name:
Home Page LP
| Action | Assignee |
| ✏️ Task: "New Ads Launch - Home Page LP" | Paid Marketing Lead |
| ✏️ Task: "1st Audit" | Paid Marketing Lead |
Update Ad URLs
| Action | Assignee |
| ✏️ Task: "Update Ad Campaigns from Home Page LP to Final Project" | Paid Marketing Lead |
Final Project
| Action | Assignee |
| ✏️ Task: "1st Audit" | Paid Marketing Lead |
FB Ads
| Action | Assignee |
| ✏️ Task: "Launch FB Ads" | Paid Marketing Lead |