Approval and publishing
Writers draft,
a person approves,then it publishes.
That sentence is the product, and the order of it is the point. A writer drafts each post about a week ahead, an owner or a manager reads it before it goes out with your name on it, and FABLS publishes it at the slot's time. Autopilot exists, per channel in a campaign, and it is off until a manager deliberately switches it on.
Due
The slot comes up about a week before its date.
Drafted
By the slot's writer, for its channel and format, briefed with the campaign and your brand facts.
Caveats
What a person should check, listed by the writer.
Waiting
The approval gate. Nothing moves without a person.
Published
At the slot's time, through your own key.
Comments
Comments, messages and reviews come back to one inbox, each with a reply drafted by the same writer.
Counted
Each platform's numbers, an hour later, then after 1, 3, 7 and 28 days.
Slots are drafted ahead of their date on purpose. A draft that appears an hour before it is meant to publish is not something you approve, it is something you rubber-stamp; a draft that appears a week early is something you can disagree with — rewrite it with a note, or edit it by hand.
Editors write; an owner or a manager approves each post. Editing before approving is the normal case rather than the exception. Drafting spends the brand owner's castomAPI AI tokens.
Pictures are yours, or drawn from an idea. Upload one in the app — it is kept public, so the platform can fetch it — paste the address of one that is already online, or press Make a picture on a draft and FABLS draws one in your brand's colours, billed to the brand owner's castomAPI tokens. Nothing draws a picture by itself.
The gate, and the switch
Approval is per channel, in each campaign. A manager can put Instagram on autopilot and leave the blog on approval, because a caption is a small commitment and a blog post reads as an official statement.
Switching a channel to autopilot is deliberate, and it is a manager's decision: FABLS then approves that channel's drafts itself. Never turning it on is a supported way to run this rather than a failure to graduate. A channel can also be drafts only — FABLS writes for it and never publishes to it.
Video goes out by itself too. Facebook and Instagram reels, YouTube videos and TikTok videos are drafted and approved like everything else, and published at the slot's time from a video you uploaded in the app. A post to a channel set to drafts only is the one thing FABLS never publishes.
On X and LinkedIn, FABLS keeps the schedule itself — X has no publish-later of its own. An approved post waits in FABLS and goes out at the slot's time.
Ads have a gate of their own. A Google Ads campaign, a Meta ad or a boost starts paused and spends nothing until an owner or a manager approves it; ads never go on autopilot, and the money comes from your own ad account, not from castomo.
- 1Instagram · OlaPublished at 08:30. A manager set this channel to autopilot.
- 2Blog · The editor1 140 words, a featured picture, two caveats to check.
- !CaveatThe Facebook draft names a price. The writer asks a person to check it.
- 3Facebook · MarekEdited by hand: one sentence cut.
- 4TikTok · OlaApproved. FABLS posts the video at the slot's time.
Approve, rewrite with a note, or editOwners and managers approve
The honest bit: the approval gate is real work. Ten slots a week is ten things to read, and the businesses that get value here are the ones that treat those ten minutes as the job rather than as an obstacle. If nobody is going to read the drafts, autopilot on every channel is not the answer — a smaller plan is.
The week it publishes without being asked.
When it goes wrong
Repairs happen in the open
Platforms refuse things. Tokens expire, an image is the wrong aspect ratio, an API is down for ninety seconds at four in the morning. What matters is not that it never happens but that you are never guessing about it.
Nothing publishes twice
When FABLS cannot tell whether a post went out — the platform's answer was lost — it does not try again by itself. It marks the post and asks a person to check. The failure mode of a nervous scheduler, the same post appearing three times, is the one this is built to avoid.
A failure is visible, not silent
If a platform refuses, the post is marked as not gone out, in the platform's own words, and the owner and the managers hear about it through the bell. It is not quietly dropped and it does not sit pretending to be scheduled.
The queue says where each post is
Every post sits in one of four places on the publishing queue: waiting for approval, going out, didn't go out, or published. And when a post should not wait for its slot, there is "Publish now".
The inbox
The comments come back.
The writer drafts the reply.
When people comment under a post, or write to the account, FABLS collects it through castomAPI into one inbox: comments on Facebook, Instagram, Threads, YouTube, TikTok, LinkedIn, X and WordPress, including under posts made outside FABLS, mentions and tags, private messages on X, Messenger and Instagram, and Google and Facebook reviews. On WordPress it takes only the comments the site has approved, and a private message is read only once a person has switched messages on for that channel.
It looks by itself, once an hour for the channel as a whole and more often for a new post, and on Facebook and Instagram the platform reports a comment as it is written. "Check for new comments" looks again whenever you press it. Each look is a castomAPI call on the wallet of whoever connected the channel.
The post's writer reads each comment — a question, praise, a complaint, a lead, spam or something else; how it feels; whether it touches money, health, safety, the law or personal data — and drafts a reply in the commenter's language, on the brand owner's AI tokens.
Only an owner or a manager sends a reply, and it goes out once: when nobody can tell whether it went out, FABLS asks a person to check before it sends again. When comments wait or a reply didn't go out, the team hears about it in the app's bell, and by e-mail for anyone who asked for a digest.
- 1OffThe comments are collected; nothing is drafted.
- 2DraftThe writer drafts every reply, and a person sends it.
- 3AutopilotA reply to a plain question or thanks goes out by itself, when the comment is not negative or sensitive, was read with confidence and leaves nothing to check. At most 20 an hour per channel.
- !Always a personComplaints and leads wait for a person, whatever the setting.
- ·SpamSet aside by itself, and brought back with one press.
Owners and managers sendEach reply goes out once
What is kept of a commenter: the name the platform shows and their words. Never an e-mail address, an IP address or a platform id — none of them is needed to answer.
Publishing goes through your own key
FABLS posts through castomAPI with a key that belongs to your account. Your WordPress site, your Facebook Page, your Instagram business account, your TikTok, your X account, your LinkedIn profile or Page, your Pinterest, Threads, YouTube and Google Business Profile. The permissions are yours, the rate limits are yours, and if you revoke the key, publishing stops that minute with nothing else to unwind.
Reports The plan