Learn Mokapen

Feed

The Feed is where the organization publishes posts for the team and, when needed, for clients on their portals. It is Mokapen's internal board: a time-ordered stream of updates to read in a glance, comment on, and — when you want — also show outside the CRM, on the client portal home.

The main advantage: instead of sending the same notice on chat, email and phone (and then not knowing who saw it), you have one place everyone can see, and you choose who sees it: the team only, selected portals only, or both.

A post is a message with formatted text, an optional image, and a destination. It is not a job to close, not a document to sign, not an ads campaign: it is day-to-day communication — the kind that today often lives on WhatsApp and gets lost.

What it is for and why it helps

Teams constantly have “everyone should know” messages: hours, closures, a new price list, a delivery delay, the Monday briefing, a notice for one specific client. In chat, whoever was offline misses them; in email, they mix with everything else. With the Feed in Mokapen:

• One reading point for everyone — open Marketing → Feed and see the latest team posts, without asking “did you see it?” on three different channels.
• The same message, different audiences — a notice can stay internal (CRM only) or appear on the home of one or more client portals, without rewriting it.
• Who should publish, publishes — not everyone needs to write on the board. You choose the authors (marketing, owner, reception); the rest of the team reads, comments and reacts.
• The client only sees what is for them — the portal shows posts published to that portal, not the company's whole internal life.
• A record over time — posts stay in the stream, can be searched and filtered. They do not vanish in a chat scroll.

In short: you use the Feed to let people know; you use the rest of Mokapen to get the work done (tasks, deals, tickets).

How to access

• Main menu → Marketing → Feed.
• You need: the Feed application on for the organization (Settings → Applications) and a Premium Medium plan (or higher). If the plan does not include it, the medal icon appears in the menu.
• On the home page you can add a Feed card (Home customization): it shows the latest posts without opening the full page — useful for the owner and reception who want a glance when they log in.

How to use the Feed page

The page is a stream, not a table: newest posts at the top. Each post shows who published it, the text, the image if any, where it is visible (Feed and/or portal names), and comments and reactions below.

At the top you find:

• Search — filter by words in the text or type (e.g. “closed”, “price list”, “event”).
• Destination filters — if you have portals: All (everything you can see), Feed (internal only), then one pill per portal. That answers “what is client Rossi seeing right now?”.
• + Post — only if you are an author (or the owner).
• Settings — who can publish (organization owner only).
• Reports — charts on volume and destinations.

From the post menu you can edit, delete or copy the link to send a colleague (“look at this notice”).

Writing a post

Press + Post. There is no title to fill in: the post is the text. Write as you would on a physical notice board — clear, visible, with bold, lists and links if useful.

You can add:

• An image — a photo, a flyer, a screenshot of the price list. Keep the file reasonably light (up to 1 MB).
• Type and subtype — labels so you can find posts later (e.g. Notice, Event, Price list, Closure). You create them on the fly and reuse them. They help search and reports; they are not a title.

Before you publish, choose where it should appear (see below). An internal post seen by a client by mistake is the classic error: check the boxes.

Publish to: team, portals, or both

Every post has a destination. That is the core of the Feed, because it decides who the audience is.

• Feed — visible to people in the organization in the CRM. This is the default: internal briefings, process changes, team notices.
• Portals — one checkbox per client portal. The post appears on that portal's home for clients who sign in there.

Typical combinations:

• Feed only — “new office hours from Monday”: colleagues must know, clients should not.
• One or more portals only — “your order ships Thursday” on that client's portal; the rest of the team may not need it in the internal stream — or they may: you decide.
• Feed + portals — “closed 15 August”: the same notice to team and clients, one publish.

If you tick no portal, the post stays in the CRM only. It does not appear on a portal by itself.

Who can publish

This is not a group chat where anyone writes. The organization owner opens Feed settings (cog) and chooses the authors: usually marketing, the owner, whoever manages clients, or reception.

If the authors list is empty, only the owner can publish. That is the safest start: turn the Feed on, publish the first notices yourself, then add two or three trusted people.

Who is not an author still sees the stream and can comment and react. Sales can write “ok, client X notified” under the post without becoming an author.

Comments and reactions

Under each post the team can comment or react. That closes the loop without opening a ticket: “seen”, “already sent to the client”, “hours confirmed at reception”.

The home card has no like counters: the point is to read the latest notice, not to rank posts. For volumes (how many posts, how many comments) use reports.

Feed reports

From the Feed page (chart icon) or Reports → Marketing → Feed you see whether communication is alive and where it goes:

• total posts and posts this month, comments;
• trend over the last 12 months — if July had no posts, you see it;
• breakdown by type (how many notices, events, …);
• how much stayed internal vs went to portals (Feed, portals, or both).

Useful at month end: “did we notify clients, or did we only talk among ourselves?”.

Limits to know

• A post is not a job — it does not replace a task, ticket or deal. If the notice creates work (“call portal X clients”), create the activities from there.
• The portal does not guess — without the portal checkbox, the client sees nothing. Always check Publish to.
• Few authors — if everyone can publish, the board becomes noise. Start with the owner, then widen.
• Plan and app — Premium Medium (or higher) and the Feed application on in Settings.

Use cases

• Monday briefing for the team — every week one Feed-only post: week's priorities, who is off, what must not slip. Late arrivals still find it; they do not have to scroll Saturday's chat.
• Closure or new hours (team + clients) — “closed 15 August, 9–13”. Tick Feed and all client portals: one publish, two audiences. Reception and clients see the same text.
• Notice to a single client — delivery delay, moved appointment, a file to download. Publish only on that client's portal. Other clients do not see business that is not theirs; the team can still see it in the Feed if you also tick the CRM.
• New price list or promotion — post with a flyer image on the portals of the clients it concerns (or all of them). Keep it on the Feed internally so sales and the counter know what already went out.
• Studio / agency with several clients — each client has a portal. Filter the Feed on the “Rossi” portal and in ten seconds check what the client is seeing before a call.
• Shop or workshop with pickup — “pickup until 18 today”, “workshop closed for inventory”. Clients read it on the portal home; floor staff stay aligned on the Feed.
• Onboarding a new colleague — this is not a course: it is “where you read what is going on”. They open Marketing → Feed and catch up on recent notices without asking everyone.
• Home card for the owner — when Mokapen opens they see the latest posts (arrows if there are several) and know if there is an urgent notice without entering the module.
• Operational comment under the post — the author publishes “call clients with Monday appointments”. Sales comments “done, Rossi ok / Bianchi not answering”. The notice stays the reference; comments are the status.
• Month-end report — in Reports → Feed you see whether you talked to clients (portal posts) or only internally, and which types you use most (too many “notices” and zero “events”?).

Frequently asked questions

Q: What is the Feed for?

A: To publish updates for the team and, if you want, for clients on portals — in one searchable place, instead of scattered across chat and email.

Q: Do clients see every team post?

A: No. The portal only shows what you ticked for that portal. Feed-only posts stay internal.

Q: Do I have to write a title?

A: No. The post is the text. If you need to classify it (notice, event, price list), use type and subtype.

Q: Who can publish?

A: The authors chosen in settings. If you choose none, only the organization owner. All colleagues can still read, comment and react.

Q: Which plan includes the Feed?

A: Premium Medium and above. Then turn the application on in Settings → Applications.

Q: How do I see what a client sees?

A: On the Feed page, use the filter with that portal's name. Only posts published there remain.

Q: Can I use the Feed instead of tasks?

A: No. The Feed informs. If the notice requires work (calls, deadlines, assignments), create activities or tickets as you usually do.

Q: Where are the charts?

A: Report icon on the Feed page, or Reports → Marketing → Feed: volumes, types, and how much went out to portals.