Features

What the platform does

social.9of.de · on fleek GmbH

on fleek Social accompanies a post from the first idea to the moment it goes live: plan it, check the media, have the client approve it and publish it on every linked channel. The people working in it are the on fleek team and the contacts at the companies we look after — each company with its own login and its own separate set of data.

The sections below describe the features exactly as they exist in the application.

Editorial planning

Every post has a date, and every date is visible — for the agency across all the companies it looks after, for the client across their own channels.

Month and week view

The calendar shows scheduled posts either as a monthly grid or as a single week. Every entry carries the time, the title, the platform and the client; the calendar can be filtered by platform and by status, so it is immediately clear what is still waiting for approval and what is already scheduled.

Drag a post to another date

A post can be dragged onto a different day in the calendar; the scheduled time changes with it. Once publishing has started, the date is locked — whatever is going out right now is no longer moved.

Europe/Berlin time zone

Times are shown in Europe/Berlin throughout and stored in UTC. The switch to and from daylight saving time therefore never shifts a scheduled post.

Overall calendar and client calendar

The agency team has one calendar spanning every company it looks after, plus the calendar of an individual client next to it, both filterable by platform and status. In their own login, the client gets a month view of their own posts — without filters and without dragging.

Posts and formats

A post is created once and can serve several target accounts at the same time, across platform boundaries. Which formats are available depends on the channel.

  • Instagram: image, carousel, reel and story.
  • Facebook Pages: image, carousel, video, reel, story and link post.
  • TikTok: video and photo post.
  • YouTube: video and short.
  • A post has one base caption. It can be overridden for each target account whenever the same content should sound different on one channel than on another — a short hook on TikTok, say, and a longer text on Instagram.
  • A post also holds the selected media, the scheduled date and the list of target accounts. From that point on, each target account is tracked separately, with its own status and its own result.

Media

Images and videos are uploaded before a post is scheduled — and checked against the rules of the intended format right there and then.

Uploading images and videos

Files go into the media library of the respective company and stay available there for further posts. Folders and freely chosen tags keep larger libraries in order; every image can be given alternative text.

Validation on assignment

Format, aspect ratio, duration and file size are checked as soon as a media file is assigned to a post — not only at publishing time. Anyone picking a landscape video for a reel finds out immediately, rather than days later at the scheduled date.

Rules per platform and post type

The limits depend on the combination of channel and format: a reel, a story, a TikTok photo post and a YouTube short each expect different aspect ratios, durations and file sizes. The application knows these rules and names the one that has been broken while the media file is being assigned.

Access for authorised users only

Media files are not sitting openly on the web. They are delivered through a route that verifies the login and the membership of the company first.

Approval

Nothing appears on a client channel without having been approved first. Approval happens inside the client login, not in a chain of emails.

Comments per post

The agency and the client contacts write in a shared thread attached to the post, each entry with author and timestamp. Change requests therefore sit exactly where they are acted upon.

Versions

Every submission freezes the state of the content as a version. If the post is reworked after a change request and submitted again, a new version is created — the client can see what changed compared with the previous one.

Reminder emails

If an approval is left sitting, a reminder goes out to the registered contacts after a period configured per client (48 hours by default). In the other direction, change requests and publishing failures notify the agency.

Client drafts

Clients can create their own drafts with text and media. The agency picks them up, finalises them and submits them for approval in the regular way.

Publishing

One post on four channels means four independent jobs. That is deliberate: when one platform is having a bad day, it does not hold up the others.

One job per target account

At the scheduled time, each target account gets its own publishing job with its own status. A single target can later be retried on its own, without touching the rest of the post.

Queue

Due jobs are processed from a queue that the application polls itself, once a minute. Each job is picked up exactly once, even when several runs overlap.

Retries on failure

If a call fails because of a temporary problem, it is retried with growing intervals, three attempts per channel at most. After that the channel in question is marked as failed and the agency receives an email.

Error messages stay visible

When a platform rejects a post, its message is stored and displayed on the post — in the platform's own wording. Errors are never swallowed quietly; otherwise there would be no way to tell why something did not appear.

Partial status

If only some channels go through, the post counts as partially published. The successful targets stay successful, and the open ones remain individually visible and individually retryable.

No duplicate posts

Before every call, the application checks whether a result already exists for that target account. Intermediate states such as upload sessions are stored so that a second attempt resumes instead of posting a second time.

Where things stand

The figures the application shows today describe the state of the work: what is open, what is coming up and what went wrong.

  • Agency view: client approvals still open, client drafts that have been submitted, the posts scheduled for the current week and the publications that failed — across every company we look after, plus the list of the dates coming up next.
  • Client view: what is waiting for their own approval, what is scheduled for the next seven days and what was published most recently.
  • When an account is linked, its follower or subscriber count is taken over and shown on the account card (Instagram, Facebook Pages, YouTube).
  • Channel metrics such as reach, impressions and interactions are not evaluated in the application at the moment; the analytics part is in preparation.

AI assistance

Text suggestions, not autopilot. The AI helps with wording; decisions and approvals are made by people.

Brand voice per client

For each company we look after, the application holds how it sounds: tone of voice, things to avoid, example captions and fixed hashtag sets. That information goes into every text suggestion as context, so suggestions sound like the client rather than like a template.

Caption suggestions

A briefing or a handful of bullet points turns into a suggested caption. The uploaded media are taken into account, so the text refers to what can actually be seen.

Adapting to the channel

Variants for the individual target accounts can be derived from the base caption — an Instagram text reads differently from a TikTok description or from a YouTube title with its description.

Polishing

For an existing text there are suggestions for the opening line, for hashtags and for the call to action, plus a length check against the limits of the respective platform.

Every suggestion is a draft: it is accepted, reworked or discarded. Nothing happens with it until a person puts it into the post — and nothing is published before the post has been through approval anyway.

Roles and visibility

Two views of the same application, with cleanly separated sets of data.

  • Agency view: the on fleek team works across all the companies it looks after — linking accounts, creating posts, scheduling, publishing and answering client comments.
  • Client view: the contacts at a company only ever see their own company — calendar and posts, comments, approvals and their own drafts.
  • Whether posts go through the approval loop is configured per company.
  • Logins are set up by the agency; there is no open self-registration.
  • Every status change of a post is logged — who submitted it, who approved it and when it was published all remain traceable.

Questions about a particular feature?

on fleek GmbH · Industriestr. 10 · 92360 Mühlhausen · Germany. We answer questions about the application, about linked accounts and about the deletion of data.

info@agenturonfleek.com