Course · Module 6: Running the Loop with GBPly
Lesson 6.3: Notifications, pictures, posts and reviews in one flow
Transcript
In the last lesson, we gave the client one place to do their part. But a portal only works if the client remembers to use it.
You can build a beautiful workflow for pictures, posts, customers and reviews. The Loop still stops if the things it needs never arrive.
So GBPly can email the client a reminder every seven, fourteen or twenty-eight days. And the important part is that the reminder is dynamic. It looks at what's actually outstanding.
If pictures are missing, it asks for pictures. If a post is waiting, it asks for the approval. If customer details are needed, it asks for those. And once something's done, it stops asking. If nothing's outstanding, no reminder goes out at all.
Here's why that matters. Say you've got fifty clients, and you chase each one once a week for something. That's fifty follow-ups a week. Over a year, that's two thousand six hundred.
That's time your account manager could spend improving profiles, making decisions, building client relationships, and solving hard problems. GBPly asks for what's missing. The client provides it. The system moves the work forward. That's Consistency turned into a system.
Let's follow each P through. Pictures first. The client has the photos, so they upload them straight into their portal, with a short description if they want.
You review what's arrived, and decide what represents the business best. Good photos move into the schedule, at the time you've chosen. No downloading from one place, renaming in another folder, and uploading again later. If nothing arrives, the reminder brings it back to the client.
On your side, the Images page shows the upload and schedule area, and the posting schedule. And if you switch on automatic scheduling for client uploads, the photos they send are queued on the cadence you choose.
The technology does the chasing, organising and remembering. You decide what gets published.
Posts work the same way. Writing one post isn't hard. Running a reliable post process across fifty clients is. In GBPly, you create the post, or generate it with A I.
If the client needs to sign it off, it waits in their portal, where they can approve it, edit it, or reject it. Once it's approved, it carries on to its scheduled date. Nobody has to dig the approval out of an email chain.
For Harbour Roofing, a storm repair post goes to Dave on a Tuesday. He approves it on his phone, and it goes live on Friday morning, as planned.
You still decide whether a post is accurate, useful and right for the business. GBPly just removes the movement around that decision.
Reviews have the same problem. Most businesses ask for reviews for a week or two. Then everyone gets busy, and six months later, somebody notices it stopped.
In GBPly, real customers can go into the review request process, including through the client's portal, one at a time or in bulk. Then the requests keep going, without anyone remembering every customer.
The portal can bring reviews back to the client too. Where it makes sense, they can read reviews and reply, with A I suggestions to get them started.
The rules from the Praise lesson still apply. Real customers only, a neutral request, and Google's policies. Automation makes the honest process easier to run. Serious complaints still go to the person who makes the judgement.
So that's one flow for all three. GBPly asks for what's missing. The client provides it. The system moves it forward. And you make the decisions.
In the next lesson, we look at measurement, bulk tools, and what all this changes for your agency. See you there.