Autopilot plans posts for a location on a schedule. For each one it picks a topic from the business facts, writes a draft on your AI key, adds a photo from the location's library, and sends the draft to the approvers. Nothing is published until a person approves it.
Go to Posts -> Autopilot and click Set Up Autopilot. Autopilot runs only where the customer's plan sets Autopilot to Enabled, for you as well as for the customer.
What it does
- Plans one post per period:
Once a weekby default,Every two weeks, orOnce a month (every four weeks), on a chosen day and time - Writes each draft ahead of its time (5 days by default, from
Ask for approval this many days ahead) and sends it for approval - Rotates through the services. Each post is about one service, with one supporting fact such as proof or availability
- A confirmed offer or event takes that week's post shortly before it starts (7 days ahead for offers, 14 for events), instead of adding an extra post
- Every draft waits for approval. Customers see Autopilot's posts as
Written for you
The seven setup steps
- You can move between steps. A step that must be finished first says
Finish stepwith its number and title - Customers reach the setup with
Create and schedule postsaccess and theManage publishingpermission. A plan that setsAutopilottoUpgradeshows the upgrade prompt instead
| Step | What you do |
|---|---|
1. Check the Profile | Turn on publishing for the location, if it is not on yet |
2. Business Facts | Confirm the facts. Fill from the Profile suggests them from the Google profile |
3. Voice | Adjust length, emoji, hashtags, sign-off and the preferred button for this location, then Keep These |
4. Schedule | How often, Day, Time and Time zone, then Save and Continue, which saves the schedule and confirms the time zone |
5. Photos | Choose from Library, then Add to Autopilot, or Upload Photos in Media. At least 5 photos are recommended, each with a description. Continue Without Photos is allowed |
6. Approval | Approvers, notice addresses and timing, as on the Approvals and Notices tab |
7. Samples | Write Three Samples, then choose one to start with |
This is a customer-side screen. Because you are in your agency account, you can reach it two ways: go to Business -> Customers -> Manage Customers and click Open dashboard on the customer: you go into their dashboard with nothing locked, even features their plan hides, and a bar at the top shows whose dashboard you are in (handy for done-for-you setups or granting access beyond a plan); or choose View as customer on the same page to see their dashboard exactly as they see it, with their plan's limits. If your sidebar shows the Agency / Customer switcher, the Customer tab plus the location switcher is a shortcut to the same place.
The defaults, and why
| Setting | Default | Why |
|---|---|---|
| How often | Once a week, Tuesday at 09:00 | Google's own advice is to post at least once a week |
| Posting days and hours | Monday to Friday, 09:00 to 17:00 | Posts go out inside business hours |
| Length | 40 to 80 words (characters in Japanese and Chinese) | The point fits the first lines a customer sees |
| Topics | One service per post, offers and events only from confirmed facts | One clear topic reads better than a list |
| Photos | Real photos from the library, never stock | Google's photo guidance asks for real places and work. A photo is not reused at a location within 30 days |
| Photo location | On: the business's town, name and services are added to each photo sent with a post | The photo in your library is not changed, and the camera's own location is removed. See Photo Location below |
| Hashtags | None, unless you set a fixed list under Hashtags | Posts read cleanly. A fixed list is added to the end of each post |
| Contact details | Never in the text | Google may remove posts with phone numbers or emails. The Call button carries the phone number |
| Approval | Every post | Google's rules ask for the business's consent before automated changes to its profile |
Photo Location
With Photo Location on (the default), each photo sent to Google with a post is tagged with the business's town, name and services. Your photos in Media are never changed, and the camera's own location is removed. This applies to every post, written by Autopilot or by a person.
- For a business whose address shows on Google: the centre of the town in its address. For a business whose address is hidden on Google: the centre of the first town it serves there, or else the first confirmed area served that is a town. A hidden address is never used
- Change it per location under
Posts -> Settings,Publishingtab,Photo Locationcard.Choose Town, the per-photo setting and the details for agencies are in Photo Library and Photo Location
Business facts
Autopilot writes only from facts someone confirmed under Posts -> Settings, Business Facts: services, proof, availability, offers, events and areas served. Fill from the Profile suggests them from the Google profile, and nothing is saved until you check it.
Autopilot writes about a service once it has two confirmed facts: the service and one more about it.
Writing instructions
How posts are written comes from three layers: your agency playbook (Business -> Publishing, Playbook tab), the location (Posts -> Settings, Voice and Instructions tab), and a single post (the topic typed for it).
A value set on the location wins over the playbook, and customers see your playbook's values as Set by followed by your agency name.
The first post
In step 7, Write Three Samples writes three posts on different topics. They count toward the month's AI drafts, and only the one you choose becomes a post. On the sample you want: Approve and Start approves it and turns Autopilot on; Send for Approval sends it to the approvers, and Autopilot starts when they approve it.
- The
Autopilottab has the same samples underShow Me Three, whereKeep as a Draftsaves one underPostswithout starting anything, andDiscardremoves it from the screen - Every Autopilot post after the first also waits for approval
One draft at a time
While a draft waits for approval, Autopilot plans no further post for that schedule: A draft is waiting for approval. The next post is planned once it is approved. A draft still waiting 7 days after approval was requested expires, and the next post is planned.
What customers see
- Autopilot's posts read
Written for youin the post list, on the post page, in emails and on the approval page - The
Autopilottab sums up its state in one line, such asOn, the schedule, who approves and the date of the next draft, orPausedwith the reason - Customers never see the AI provider, the model or the playbook name. Problems only you can fix read as
Askfollowed by your agency name
Limits and the AI key
- Each draft, sample and rewrite counts toward
AI drafts per location per month(30 by default). Autopilot's own drafts for the month are set aside first, so other AI writing cannot use them up - Each post counts toward
Posts per location per monthwhen the plan sets one. At the limit Autopilot waits until the next month - Without an AI provider Autopilot plans nothing:
AI provider required. Autopilot plans nothing until one is set up in AI settings. - Autopilot pauses itself after three posts in a row at the location are not approved by Google, and when the location's channel is disconnected. It stops after several drafts in a row could not be written.
ResumeorTurn Onrestarts it once the cause is fixed
Pause Autopilot or hold every post
- Pausing stops new drafts only. Posts already approved still go out
- To stop approved posts too, use Hold All Posts. Every post at the location waits until
Lift Hold
How often each service comes round
Autopilot rotates through services, so the more services in rotation, the longer each one waits. Twelve services at one post a week come round about every 12 weeks; at one post every two weeks, about every 24 weeks. The Autopilot tab shows the figure for each location, for example 12 services are in rotation: each comes round about every 12 weeks.
When that is longer than 60 days the page suggests fewer priority services, or more posts.