Write and send your client’s first posts

1. A post. Open the client, then Posts and New post. Posts carry text and images today; video is not supported yet. You can write posts before the client connects.
2. A tag. Open Groups, tick the groups and press Add tag. A tag is reusable: pick it when you schedule, and every group with it gets the post. Each tag belongs to one of the client’s Facebook accounts, the profile or one of their Pages, and that account is who posts.
3. An automation. Open Automations and press New automation. Choose its group list and posts, and set when it runs with Repeats, the date and the time. Press Create automation.

A new automation is created switched off. It runs only after you switch it on and push.

Only groups the client’s Chrome has reported can go on a list. Their Chrome reports the groups saved in their Group Posting extension, one Facebook account at a time, shortly after they connect. In practice the groups usually appear within a few minutes, while their Chrome is open.

If Groups still says “No groups reported yet”, press Refresh their groups. It takes up to 5 minutes, between their posts, while their Chrome is open. You can ask for 2 refreshes a day for each client.

A group the client has not joined cannot be added. Ask them to join it, then refresh.

1. Switch the automation on. The message after you create it has a Switch it on button, and the Automations list has a switch on each row. Nothing reaches the client’s Chrome yet.
2. Press Send changes at the top of the page. It shows how many changes it will send, for example “Send changes (2)”. On a new client, this first push installs everything switched off, whatever the switches say. The Automations tab says so: “First push installs everything switched off. Once their Chrome has it, push again to start.”
3. Wait until their Chrome has it. The status beside the button changes from Pushing… to Received and then Up to date. That is usually within a minute while their Chrome is open.
4. Push again. Now the automation starts, and its Next run shows.

The same two steps apply again if your client later moves posting to a different computer.

Run now posts an automation once, straight away, instead of waiting for its time. It posts for real, to every group on the automation’s lists, so test with a short list the client is happy to post to.

1. Push first. Their Chrome must have the automation, or the dashboard says “Their Chrome doesn’t have this automation yet. Push your changes, then try again.” Run now works even while the automation is still switched off, so you can test after the first push.
2. In Automations, press Run now on its row.
3. Read the confirm. It shows how many groups, which Facebook account posts and the earliest time the run will finish. Press Post it now.

If their Chrome is closed, the request waits until it opens. After 15 minutes it expires and nothing is posted. Each client can have 6 Run now requests a day.

Open the client’s Activity. Each group shows one of five results:

• Posted: the post is confirmed.
• Held for approval, also called an approval queue: the post is waiting for the group admin to approve it, or the client is not a member of that group.
• Unconfirmed: Facebook accepted the post but did not confirm it. It may be waiting for admin approval. Look in the group before you send it again.
• Failed: it did not post. The reason is shown.
• Not attempted: the run ended first.

A run that has started is only a start. Approval queues and unconfirmed posts are counted separately from confirmed posts.

No. The dashboard has no client approval step. Your client agrees once, on the connection sheet, that you can schedule posts for them, and can pause or disconnect at any time. After that, a post goes out once you switch it on and push.

If your client wants to see the plan first, share it with them your own way before you push.