Section 4 of 9

Demo

Show them their page

The walk-through

Draft script

Step 1: Open their page
Show the page MeanScoop already built from public posts about them.
On screen: Their business page on your phone.
Step 2: Listen to their response
Give them time to explore the page and share their thoughts.
On screen: The same page — let them scroll.
Step 3: Ask what is coming up
One question. Note any dated event and its start time.
On screen: Their upcoming listings, if any.
Step 4: Hand over the page
Offer ownership of the page. It is free.
On screen: The ownership QR for this business.

v1 handbookCarried over while this section is restructured.

"Keep posting where you already post" is the promise. This page covers what happens after they post: how a post becomes a listing, what tagging other accounts does, and the few habits that decide whether their next event shows up correctly. This is the coaching an owner gets from you and from nobody else. Every line here is labelled by what the running code actually does.

Nobody types listings into MeanScoop. Everything on the map comes from real public posts on Instagram, TikTok and Reddit, passed through the same pipeline and review gate. We never hand-edit a listing. If a listing is wrong, we fix the part of the pipeline that read it wrong. So the best thing an owner can do is make their posts easy to read. Asking us to change the row does not work.

How a post becomes a listing

  Public post (IG / TikTok / Reddit)
        │   found three ways: an account we watch · a hashtag/keyword search · someone sends it to us
        ▼
  Read it ─── the caption, plus the text on the flyer or image (we read images)
        │
  Market check ─── is this Tahoe / Reno? If not, it stops here
        │
  Work out WHAT · WHEN · WHERE ─── title, date + start time, venue
        │
  Review gate ─── clear posts publish on their own; unclear ones wait for a person
        ▼
  Listing on the map / feed ─── linked to the business when we're confident it's theirs

We launch in Tahoe and Reno only. A post about somewhere else is dropped at the market check, however good it is.

Coach the post: five habits that get an event listed right

These come straight from how the extractor works. Each habit prevents a failure we see in real data.

1. Date AND start time, with am/pm

Write "Fri Oct 10, 7pm" or "7:00–10:00 PM". Leave out the time and the listing reads "Time TBD". We would rather show that than guess. A time with no am/pm (just "7:00") is ambiguous. A window like "1–4 PM" is read as starting at 1 PM.

2. Name the venue and the town

"@ The Hangar, South Lake Tahoe" beats "at the usual spot". Tagging an account is not an address. If the only place named is a tagged handle, we may know the town but not the room.

3. Put the details in text, not only in the video

We read the caption and the words on a flyer image. Details that are only spoken in a video, or only in a story, are much less likely to make it through. Stories disappear and we don't collect them.

4. One event per post

A "this week at the bar" post listing five nights is hard to split cleanly. Splitting one post into several events is being tested and is not switched on yet. Until it is, one post per event is the reliable way.

5. Repeating nights: say the pattern

"Trivia every Tuesday, 7pm" is understood as a repeating event. "Trivia tonight!" each week works too, but each post has to be read again.

Public accounts only. A private account, a Close Friends story or a post behind a login is invisible to us. Nothing we do works around that, and you should never offer to.

What tagging actually does

When a post we read tags, @mentions, or co-authors (IG Collab) another account, we record that account as evidence, not as a trusted source. Mentions that keep coming from different places make an account a candidate. A person on our team then decides whether to watch it every day.

1. Evidence — the tag is recorded

Every account named in a post is logged against that post, once. Reposting or re-reading the same post does not inflate the count.

2. Candidate — enough independent evidence

An account qualifies for review when any of these hold: it was an IG Collab co-author on a post, it was tagged in a photo, two different accounts mentioned it, or it posted twice in our market. A single mention from one account stays as evidence and is never acted on alone. Accounts outside Tahoe/Reno, and big national brands, are filtered out.

3. Watched — a person approves it

Only an approval from someone on our team turns a candidate into an account we check every day. A tag never does that on its own, so nobody can tag their way into the feed.

Where this stands today (2026-09-30). Caption @mentions have been recorded for a while, but the old counting double-counted reposts. The version above adds IG Collab co-authors and photo tags, one-time counting, the evidence floor, and team approval. It is in review and not live yet. A dry run over real Tahoe/Reno posts found about 1,600 accounts past the evidence floor. When we checked the most-referenced ones by hand, most were genuine local venues (The Alpine, Grand Sierra, Cargo, Reno Public Market). Don't promise an owner that tagging will get them watched. Say it helps us find them.

How to use tagging with an owner

Use IG Collab for joint events. If a band plays their bar, a Collab post with the band is the strongest signal we get. It tells us both accounts are real and local.
Tag the venue in event posts, and put the venue's name in the caption too (see habit 2). The tag helps us find the account; the written name helps us place the event.
Tagging can't hurt a listing. A tag never moves an event to a different business, never claims a page, and never publishes anything by itself.

Tagging @meanscoop does nothing yet. We don't read our own mentions or DMs on Instagram. That needs Meta's business verification and API approval, which we don't have. Don't tell owners to tag us. Tell them to send us the link (below).

"Send us a scoop" — the direct route

Anyone can paste an Instagram or TikTok post link at /scoop on the site. No account is needed. Sent posts jump the queue ahead of routine discovery, and the sender gets a receipt that reports what happened. Possible outcomes: being checked, now in MeanScoop, outside the area we cover, already happened, or couldn't read it.

Use it for

An owner's upcoming event that isn't on the map yet.
A venue you walked into whose account we clearly aren't watching.
Checking a post: the receipt tells you honestly whether the pipeline could read it. That's useful coaching feedback for the five habits above.

It does not

Publish anything. The post goes through the same checks and review as every other post.
Claim the business, or link the event to it.
Sign the account up for daily checks. At most it counts as evidence toward that.
Skip the Tahoe/Reno check. Nobody's link can override it from /scoop.

It is rate-limited to 10 links an hour and 30 a day per person. Send the posts that matter, not the whole grid.

Coming, not built: sharing straight from the Instagram/TikTok share sheet into the MeanScoop app. The backend is ready; the app side is not. Until then, copy the link and paste it at /scoop.

When a listing is wrong

There is no self-serve edit or correction button, and that is deliberate (see the truth callout at the top). Do three things:

Note the listing and what is wrong: time, venue, title or business.
Send it to the operator team. We trace it to the step that read it wrong and fix that step, which fixes every similar post too.
Coach the owner's next post with the five habits. That is usually where the fix really lives.

An owner who has claimed their page sees their listings in the business console. Each one shows whether it is visible, whether it has finished, and whether we're confident it's theirs. The console may show "worth checking" on a listing. That means our own pipeline wasn't sure the listing belongs to them. It is not a fault on the owner's side.