Posting to Facebook groups

The service doesn't do anything you couldn't do by hand: the software posts listings to the Facebook groups you're already a member of, under your own account. When you sign up, you accept the terms and take full responsibility for your Facebook account. It's important to understand: Facebook does have rules against posting too frequently, so we deliberately keep a human pace (random pauses, a post limit, separated time windows) - but we can't guarantee Facebook will never restrict your account. The service is intended for users 18+.

The software posts to groups roughly from 07:00 in the morning until midnight (in practice the window stretches to 02:00 at night), Israel time. In your dashboard this is shown in simplified form as "07:00-00:00". At night the Facebook software sleeps - that's when the separate Marketplace software takes over. The hours are set to hit the active time of day, when there are more people in the groups.

You set a daily post RANGE rather than a rigid per-hour number - on the server card, "Facebook software settings (groups)" block, the "Posts per day - range (from-to)" field. The software builds a smart hourly plan on its own (shown in the "Schedule form", where you can fine-tune it per hour), then "Save". The new value takes effect from the next day; there's no need to restart anything.

That's warm-up. After a Facebook restriction or on a new account the program doesn't jump to full speed - it starts with a small number of posts a day and over a few days climbs gradually to your range. On the server page you'll see a note like "Today's plan - N, usually A-B posts a day. The number grows gradually; from DD.MM the program posts as usual". Your range is saved and switches on by itself when warm-up ends - nothing to re-enter.

You can raise the daily range, but we strongly advise against going above ~50 posts per day - the interface explicitly warns about this with a yellow banner. The more often the account posts, the higher the risk that Facebook temporarily restricts posting (at peak hour the software won't exceed ~11 anyway). It's better to keep a calm pace (≈50/day, about 4 per hour): posts go out more steadily and without blocks. Chasing volume in the moment usually doesn't pay off.

In each hourly cycle the software takes a few of your listings (based on the "posts per hour" number) and spreads them across the enabled groups, shuffling the list at random. It won't post to the same group more often than once every 4 hours - that's a built-in safeguard against spamming one group in a row. This makes your posts look more natural and less likely to run into restrictions.

Each server is automatically assigned its own 12-minute "slot" within the hour (for example :00, :12, :24, :36, or :48), and the software posts precisely in its slot. This is done on purpose, so that not all servers post at the same time - the load is spread out more evenly. You can't pick a specific minute; it's calculated automatically, and there's no need to get involved.

For Facebook groups, your listing text is NOT changed - the software posts it as is and only appends a short three-line contact block at the end: 📲 phone, 💬 WhatsApp link, and 🌐 link to your site/Telegram. That's the "footer". (AI rewriting of the text happens only on Marketplace and on reposts, but not in groups.)

Most often the reason is harmless: the Chrome browser didn't launch on the server (usually due to a temporary lack of resources), and the software simply skipped that slot - it will try again the next hour. It's a one-off skip, not a malfunction. But if skips happen back to back, check whether there's a rate-limit pause or whether your Facebook session dropped (more on that below).

It means Facebook has temporarily limited posting from your account (a so-called rate limit). The program waits it out on its own - 12, 24 or 48 hours depending on how many limits came in a row - and then runs for a few days at a gentler pace with fewer posts (warm-up). This is a Facebook restriction, not a service failure. The pause can't be shortened; a calmer posting pace helps prevent it.

After starting or resuming, the first post usually goes out within 5-15 minutes - the software waits for the beginning of its 12-minute slot in the hour and only then posts. This isn't a freeze, and you can't speed up that first post. After that, posts will go out on schedule in every cycle.

No, there's no way around the limit - the "posts per hour" field is hard-capped to the 1-15 range both on the site side and on the server side, so a "tweaked" request won't get through. You don't change the window hours or the slot yourself either. This is intentional: strict pace limits are part of protecting your account from Facebook blocks. If you really need more volume, it makes more sense to order another server (a second account) rather than push one harder.

On some servers a separate mode (FBMP) is enabled for buy-and-sell groups - the ones that have a "Buy and Sell" tab or a "Sell" button. In such groups, instead of a regular post, the software creates a listing via Marketplace (type, rooms, price, location, photos, description). For you it counts as a regular slot post; there's nothing extra to set up.

If, on entering a group, the software sees that it's blocked or the post falls under restrictions, it doesn't keep "banging" against it endlessly - after several attempts in a row, that group goes into a blacklist for a day, so as not to waste a slot on it or risk the account. The next day it takes part in the rotation again. This is automatic protection; no need to intervene.

Not necessarily. Red highlights lines with an error or a failed posting attempt, but many of them are routine: a group skipped due to restrictions, a one-off browser failure, and so on. It's worth worrying if you see a consistent pattern - for example, a rate-limit pause or a message about logging in to Facebook. There's no need to react to individual failed attempts within an hour that was successful overall.

Facebook processes the clip first and only then shows the post. The software allows for this: it waits for processing and checks its own page in the group several times. While the post is not visible, no screenshot goes to Telegram; it arrives later, once the post appears. If the post has not surfaced within forty minutes, the software sends a screenshot of the group page and says the video is still being processed.