Building brand pages with agents (what worked, what still needs a human)

I spent part of this weekend setting up brand pages for two projects: Aspen ESA, a free community handbook and documentation resource for Arizona ESA families, and SchoolTechPartner, my fractional CTO work and K-12 toolkit.

I wanted to see how much of that setup agents could help with. There are a lot of small steps involved in getting a page ready, from gathering the right description and images to deciding what someone should see when they first visit. This gave me a chance to work through those steps with the tools and learn where I still needed to take over.

Getting the pages ready

Once I was signed in to LinkedIn, an agent worked through the SchoolTechPartner Company Page setup: the name, custom URL, website, industry, size, About section, and logo. It used copy from the live site and retried the cover image after the first upload failed.

It also drafted three posts and held them for my approval. The first, about the meeting minutes generator, went live as the Company Page. We scheduled the other two, about a cybersecurity readiness roadmap and a compliance calendar, a few days apart.

Aspen’s Facebook Page work followed a similar pattern alongside the marketing work. Agents helped prepare the material and work through the interface. I reviewed the copy and handled the steps that needed my involvement.

What I found useful was having help carrying the work from one step to the next. I could review what was being prepared and decide whether it represented the project well before anything went public.

Knowing when to take over

We kept a clear handoff for sign-ins, two-factor authentication, and confirmations that I was authorized to create or manage an account. Our workflow also kept workplace or domain verification, payments, and administrative changes with me.

When one of those steps came up, the agent stopped and handed the desktop back. I signed in or completed the confirmation, then let it continue. Passwords stayed out of chat.

Those handoffs are part of the process I want to use with brand accounts. The agent can help prepare and carry out the work, and I need to be available to check it and take responsibility for the account decisions. Planning for that makes the workflow easier to understand.

Giving visitors something useful

I wanted someone visiting the SchoolTechPartner page to understand what we are building and find a few useful examples of the work. The three posts gave us a starting point, and spacing them out gave each one some room.

That was also a useful reason to review the drafts carefully. The page should explain the projects in plain language, with enough detail for someone to decide whether they are relevant to their district. I want the posts to reflect work we can actually discuss with people.

The setup we could not finish yet

We also tried to create a SchoolTechPartner YouTube Brand Account under the domain’s Workspace user. YouTube was already enabled in the Admin console, but the account still showed: “This account is not yet eligible to use YouTube.”

That left the YouTube setup waiting on account eligibility. Enabling a service in the Admin console and being eligible to use it were separate issues in this setup. The agent could help us understand where we were stuck, but we still had an account requirement to resolve before moving forward.

What I am taking from it

I enjoyed seeing how much of the setup we could work through together, including the small problems along the way. The arrangement I want to keep is straightforward: agents help prepare drafts and work through the interface, I review what represents the projects, and publication waits for my approval.

Next is finishing the YouTube setup when the account is eligible and continuing to share the work behind these projects. There is plenty to write about in what goes well, what needs another attempt, and what we learn by doing it.