LetsGoLive Digital

Team Guide

How the tool works, how we use it every week, and how to keep it healthy

1. The product, in plain English

LetsGoLive Digital is a content factory for car dealerships. Pick a dealership, pick a vehicle, and the tool produces a package of roughly twenty search-focused articles around that vehicle: comparisons, buying guides, common questions, and a hub page that links them together. It also produces the images and video that go with them.

Everything then moves through one pipeline: drafted, checked, reviewed by the client, and finally published to their website.

What it produces

Why the team uses it instead of a general AI writing tool

• It knows each store. Copy uses the dealer's real details and brand voice, not placeholders.
• It enforces rules automatically. Only approved media for that vehicle can appear, and links must go to the dealer's own website.
• It handles legal wording by store and page type. Each dealership has its own disclaimer text for new, used and service pages.
• It has client review built in. A client approves or requests changes from an emailed link, with no account needed.
• It outputs something publishable, not a pile of notes that still needs formatting.

Who does what

2. Before any content: setting up a dealership

Every piece of work belongs to one dealership, and the tool always works on whichever dealership is selected in the sidebar. If something is missing, the tool rarely complains, it simply produces weaker output. Set up in this order:

Steps 3 to 9 can be partly auto-filled from the dealer's public website during onboarding. Always review what was pulled in; it is a starting point, not a finished record.

3. Routine workflows, step by step

These are the tasks the team repeats. Follow the steps in order the first few times; afterwards they become second nature.

3.1 Build a vehicle content plan

1. Select the correct dealership in the sidebar. Everything you create lands under the selected store.
2. Open the Go-To-Live Planner.
3. Step 1, choose the vehicle. Pick year, make, model, trim and body style.
4. Step 2, check the competitors. The tool suggests competing vehicles. Remove any that are irrelevant and add missing ones.
5. Step 3, choose the articles. Around twenty article types are recommended. Untick anything the client does not want.
6. Step 4, review the fact sheet, then generate. Read the vehicle facts before generating. Correct anything wrong here, because every article in the plan inherits it.
7. Confirm the new articles appear in the Planner / Deliverables view for that dealership.

3.2 Write and check one article

1. Open the article from Planner / Deliverables or the Page Directory.
2. Read the generated copy in the editor, with the formatted preview beside it.
3. Correct facts first: specifications, offers, contact links. Facts beat style.
4. Adjust tone if it does not sound like the client. If you are correcting the same tone repeatedly, update the brand voice instead.
5. Check the compliance panel. It flags brand-rule conflicts, a missing pricing disclaimer when the copy mentions price, and links pointing outside the dealer's site.
6. If the article mentions price, open the disclaimer panel and insert the dealer's approved text for that page type, then save.
7. Add images only from the approved media for that vehicle, and add product cards where a vehicle should be promoted.
8. Save. The preview and the published output show exactly the copy that was saved, nothing added or removed.

3.3 Produce and approve media

1. Open the Media Library and choose (or create) a folder for the dealership or vehicle.
2. Upload source photos, or generate new images. Generation produces two variations of each concept.
3. Compare the variations, keep the better one, and delete the other so the library stays clean.
4. Tag each asset to the vehicle it belongs to.
5. Approve the assets you want to use. Only approved assets are offered when writing an article.
6. Rejected assets stay in the library but are never used in content.

3.4 Send content to a client for review

1. Open Planner / Deliverables for the dealership and select the items to send.
2. Choose to send for review, give the round a clear name (for example "March vehicle batch"), and add a short note for the reviewer.
3. Enter the client contact addresses and send. The client receives a link; they do not need an account.
4. Watch for the decision. The team is alerted by email and in Slack when a client responds.
5. Read the comment in the article's feedback panel and act on it.
6. Save your changes. The client can reopen the same link if you need a second look.

3.5 Publish an approved article

1. Confirm the client's decision is recorded as approved.
2. Open the article and choose the publishing view.
3. Copy the page title, the page address, the meta description and the formatted page body.
4. Paste them into the dealer's website in those four places, in that order.
5. Mark the article as published in the tool so the team can see it is live.
6. Open the live page once and check the formatting, links and any images.

3.6 Produce video

1. Open Video Studio and choose the format, the length and the destination (website, YouTube, social, paid ads).
2. Write or generate the script from the same vehicle facts used in the articles.
3. Choose the source media: approved images or footage for that vehicle, or dealership photos for general brand content.
4. Generate. Longer videos are built from eight-second shots and assembled automatically.
5. Watch the whole result. Continuity and quality vary between shots, so nothing goes to a client unviewed.
6. If one shot is weak, regenerate that shot rather than the whole video.

3.7 Report results to a client

1. Select the dealership, then open Analytics.
2. Choose the period you want to discuss, for example the last 30 days.
3. Review traffic, search queries and which pages gain visibility.
4. Open Attribution to see calls, form submissions and other leads, split by department where the client's tracking supports it.
5. Note anything unusual before the client call, particularly a sudden drop.
6. If a report is blank, check the dealer's analytics connection before assuming the content underperformed.

4. Maintenance notes

None of this requires technical skill. It is the upkeep that keeps quality high and stops small problems becoming client issues.

4.1 The regular rhythm

4.2 Things to watch

4.3 What only a developer can change

A small number of settings live in the tool's code rather than on a screen. They are easy to forget and worth reviewing during handover:

• the email address that receives review alerts, and its backup address;
• the Slack channel review decisions are posted to;
• the default price recorded when an industry is unlocked;
• the tool's display name, which currently does not match the public brand name.

5. The systems we depend on

The tool is not self-contained. The last column is the one to read during handover: it is what the team notices first when a connection changes hands badly.

6. Handover checklist

Tick an item only once the new owner has confirmed access themselves, not when an invitation has been sent. Two people should be able to do every item before old access is removed.

7. Known limitations

Confirmed by inspecting the tool as it stands today. Listed so nobody is surprised, and so effort goes to the right places.

8. Quick answers

"The analytics reports are empty."

The dealership is missing a tracking connection. Record their analytics and search properties in Business Settings, and confirm both connections are still authorized.

"A link I added disappeared from the article."

Links must point to the dealer's own website, apart from a short approved list of research sources. Anything else is removed on purpose so the dealer is never sent to a competitor.

"The pricing disclaimer is missing from the published page."

Disclaimers only appear when the wording is in the article. Open the article, insert the dealer's approved text for that page type, and save. Preview and publish will then match.

"The article has no images."

The media is not approved, or not tagged to that vehicle. Fix it in the Media Library, then reopen the article.

"Generation stopped working."

Check the AI credit balance first. Nine times in ten that is the cause.

"Stock numbers are out of date."

Check the feed address and interval in the dealership's settings, then check when the last import ran. If the dealer changed website provider, the feed address has changed too.

"A client says they never got the review link."

Check the Slack alert, then resend. Addresses outside the app depend on a paid plan and a connected custom email domain.

"A client can open a review link we did not send them."

Review links are open by design, so anyone holding the link can see that round. Send future rounds to named contacts only.

"Can I undo an approval?"

Ask the client to reopen the same link and change their decision, or record the correction in the article and resend the round. Decisions are kept as a record, so nothing is silently rewritten.

9. Words we use

10. The first two weeks

1. Day 1. Get administrator access to the platform, the code repository and Slack. Open the tool and confirm every sidebar tab loads for one real dealership.
2. Day 2. Read this guide with the tool open beside it, then read the in-app Documentation page.
3. Days 3 to 5. Run one full cycle on a test vehicle: plan, one article, one image set, one review round, publish output. Nothing teaches it faster.
4. Week 2. Re-authorize the Google connections under the new owner and confirm reports still return numbers.
5. Week 2. Work through the handover checklist in section 6 and complete every [CONFIRM] item.
6. Week 2. Agree and record who owns technical changes.
7. Before old access is removed. Move review alerts to a shared inbox, confirm billing is reachable by the new owner, then remove old access.

Sign-off

This section confirms the handover actually happened rather than being assumed.

LetsGoLive Digital, Team Guide. Internal document. Contains no credentials. Do not add passwords, keys or tokens to this file.