Q4Launch Policies

  • Customer Payment Form Processes | PCI Compliance

    To ensure Q4Launch is compliant with our security standards in storing customer billing information, new processes are going into effect on how we are internally sharing and storing payment information (Example: ACH and credit card forms). Basics of PCI Compliance: https://www.pcicomplianceguide.org/faq/#1 Q4Launch Processes New Logo/New Customer Onboarding Upon receiving a verbal from a potential new … Continued

  • Q4Launch Policy: Website Launch Guideline & Playbook

    Launching a website is our most critical process at Q4Launch If something goes wrong during launch then we missed a step or didn’t do enough to prep for success. Even if the failure was out of our control but the customer is upset with us, then we likely didn’t provide enough support and communication during … Continued

  • Customer Domain Registration / Registrar Transfers

    Q4Launch does not maintain domain registrations for customers. Please advise customers that want to transfer a domain to us to instead create an account at: GoDaddy: https://www.godaddy.com/offers/domains/domain-transfer https://www.godaddy.com/domains/bulk-domain-transfer.aspx or Google: https://domains.google.com/m/registrar/transfer https://support.google.com/domains/answer/3251236?hl=en Once the customer has an account, with a credit card on file, if they have issues they should contact support from that service … Continued

  • Q4Launch Policy – WordPress Core / Plugin Installation & Updates, List of Approved Plugins

    WordPress Core / Plugin Installation & Updates Policy Only Dev is responsible for installing and running WordPress Core and Plugin Updates because only dev has the ability to restore a site if something breaks during an update. There isn’t a reason for anyone else to run an update. If you have a question about installing … Continued

  • Q4Launch Out of Office Procedures For CSM’s and CC’s

    For all employees: Request time off with as much advance notice as possible. Once approved, add to your Google calendar. Line up someone to be your OOO contact. Communicate dates you’ll be out and your OOO designee to team members. Set the expectation as to whether you’ll be checking email/reachable. On-going projects will be handled … Continued

  • Q4Launch Policy for Creation of In-House SEO Content Creation for OSRs

    Netvantage doesn’t create content. Instead, they edit and optimize what’s already there. However, in the OSR (on-site review), Netvantage sometimes recommends creating pages that don’t exist on customer sites. If NetVantage recommends creating content for a page that doesn’t exist, you have three options to manage the creation of that content: 1. Ask the customer … Continued

  • Q4Launch Official Cookie Policy

    Below is the official cookie policy for any Q4Launch customer, who uses one of the Q4Launch websites! If your customer needs one or is insist we have one you can use the below text. **Please change out the links below.    This website uses cookies to help us enhance your browsing experience.  By using this website … Continued

  • A Complaint Free World – Video and Notes

    The Function of Complaining, Responses, & How to Break the Habit Complaining Defined: Complaining is NOT bringing attention to a problem. It has a “how dare you” quality to it, takes things personally. It is an end unto itself and does not seek a solution. A Constructive Alternative: Start with “You may not be aware of [problem]”, … Continued

  • Q4Launch Policy for Managing Customer’s Extreme Weather Emergencies

    Overview The following is a framework for how we can/will respond to emergency situations for our clients. Content and CEM team members will collaborate on the appropriate plan for their individual clients. CEMs will contact the clients regarding our SOP to customize and approve a plan based on their needs. Some clients will have their … Continued

  • Q4Launch Policy for Using Non-Q4Launch Software (ie: Websites)

    For a customer who will not / cannot launch website that’s being designed by another provider If blog content cannot be posted, we store it as Google Drive Docs and let them know that we’ll add billable hours for updating and posting blogs once the site launches Content Creators will create an estimate for time … Continued

  • Q4Launch Policy for Website Launch Dates

    For customers who will not give approval to launch Q4 website: We publish a Q4-designed site 30 days after the scheduled launch date, providing all of the pertinent pieces of the puzzle are in place. This policy is included in all contracts implemented as of September 1, 2018

  • Q4Launch Policy for Customers That Require Approval of Content

    For customers who fall behind on content approval (blogs, email, social content) Create content and notify client that it’s ready for approval. Publish within 48 hours if we don’t hear back, regardless of response from customers Be sure to notify customers of this policy as close to the start of marketing at possible

  • Q4Launch Policy for Customers That Fall Behind on Monthly Payments

    Once we receive notification that a customer has stopped or missed a payment, We: Stop work (blogs, emails, Facebook, dev, etc.) until payment is received. While we wait for payment to resume, team members will use allotted time to work ahead on other projects. This will help create time on the back end to resume … Continued