How to use SocialMediaBucket

1. Getting started

What SocialMediaBucket is

SMB is your content bucket — a shared library where your brand posts artefacts (images, videos, captions) and your ambassadors find what's new to share. It is not a CRM, not a community platform, and not your messaging channel. You talk to your ambassadors on Discord / Slack / WhatsApp / email — SMB just stores the things they share.

The 10-minute setup

1. Create your org. Add your name, description, logo, social links. The company email field on /org/ is what we pre-fill as the To: address when you notify ambassadors — set it.
2. Buy storage. 5 GB starts at $62/month — enough for ~200 short videos. Yearly is 6% off.
3. Create at least one class. A class is how you group ambassadors (e.g. "Lagos", "September 2025 batch", "Power Users"). One ambassador can be in multiple classes. See Classes below.
4. Invite your first ambassador. Generate an invite link on /ambassadors/, hand it to them, they accept. Done.
5. Upload your first artefact. Pick the classes that should see it. Hit Add to bucket. The post-upload modal asks if you want to notify them — that's the email composer.

Invite a co-admin (optional)

Admins manage artefacts, ambassadors, and billing. Every admin has the same powers — invite, remove, change billing, delete the org. No "owner" tier. The only safeguard is that the last admin can't leave (the org would have nobody to manage it). Add admins from /admins/.

2. Managing artefacts

What makes a good artefact

• Title: short, scannable. Ambassadors see this in their feed.
• Caption: the copy you'd want them to use verbatim. Most ambassadors copy-paste it.
• Body text (optional): longer-form thoughts, alt versions of the caption.
• Platforms: which channels this is intended for (IG / TikTok / X / YouTube / LinkedIn). Ambassadors get to see this when deciding where to post.
• Classes: who should see it. Skip → draft (no ambassadors see it).

Drafts

An artefact with no classes attached is a draft. It's in your bucket but no ambassador can find it. Useful for prepping a batch the night before launch.

Editing + deleting

You can edit title, caption, body, and platforms at any time. Reassigning classes works the same way. Deleting an artefact is irreversible — it's removed from every ambassador's feed and the underlying file is purged from storage.

3. Classes — when to use them

Classes are the routing primitive. Think of them like Slack channels: an ambassador belongs to one or more, an artefact targets one or more, and the intersection is who sees it.

Typical class patterns

• By location: "Lagos", "London", "Accra". Useful when you run regional campaigns or city-specific products.
• By cohort: "September 2025 batch", "Founding 50". Helps you reward longevity without saying so out loud.
• By tier: "Power users", "Casual". The 80/20 rule applies — a small group of ambassadors will drive most of your reach.
• By campaign: "SS26 launch", "Black Friday 2026". Time-bounded; archive the class when the campaign ends (remove ambassadors from it; the class itself stays for the audit trail).

How many classes is too many?

The cap is 340 per org. The practical maximum is closer to 15-20 — beyond that, you're running an internal ops project to manage your ambassadors, not a marketing channel. If you find yourself needing 50 classes, you probably want sub-orgs.

4. Notifying ambassadors

SMB shows ambassadors what's new in three passive ways:

• The bell icon in their dashboard lights up when there's a new artefact in any of their classes.
• If they granted browser push permission, they get a push notification (Chrome / Firefox / Edge / Safari 16.4+).
• The artefact appears at the top of their feed next time they open it.

The "Notify by email" composer

After you upload an artefact, you'll see a modal asking if you want to email the ambassadors. This opens your own mail client — Gmail, Outlook, Apple Mail, whatever you have — with the right To, Subject, BCC, and Body pre-filled. You hit Send.

Why your client and not ours? Two reasons:

1. Deliverability. Email from [email protected] lands in inboxes. Email from [email protected] increasingly lands in spam, especially if you send to 200 addresses.
2. The relationship is yours. Your ambassadors agreed to hear from you. Putting our domain in the From line is us muscling into a conversation that's not ours.

When NOT to use the email composer

If you already have a Discord channel, a Slack workspace, or a WhatsApp community with your ambassadors, use that. It's faster, more native to how they communicate, and avoids ambassador-fatigue from your fifth email this month. Click Skip in the modal and just paste the artefact link into your group.

Pacing

One email per artefact gets old fast if you ship five things a day. Some workable rhythms:

• Per artefact: only for genuinely launch-day stuff.
• End-of-day digest: notify the group at 5pm with all that day's drops.
• Weekly roundup: every Friday, "here's what's in the bucket this week". Lowest friction.

5. Managing ambassadors

Who makes a good ambassador

The honest answer: someone who would share your stuff anyway. Forced advocacy is brittle and obvious. Look for people who:

• Already engage with your brand publicly (replies, shares, tags).
• Have a tone that matches your brand — you're not going to retrain them.
• Post regularly on at least one platform. Volume matters more than follower count.
• Live in your target market (or are credibly aspirational for it).

Onboarding

The invite-link consume page is the first impression. Pair it with a real welcome message in your community channel:

Welcome to the ${'{'}Brand${'}'} ambassador group. Quick things:

— You'll see new artefacts pop up in the bucket. Share what
  resonates with you, skip what doesn't.
— We post about 3-5 things a week. No quotas. No pressure.
— When you share, please tag us — that's how we know it's you.
— Quit any time, no hard feelings. Just leave the channel.

Bucket: https://socialmediabucket.com/amb-feed/
Questions: dm @yourname or post in #ambassador-questions

When to remove an ambassador

• They haven't logged in in 90+ days and don't respond to the nudge.
• They've started representing a competitor (check your terms; not always disqualifying).
• They asked to leave. Honor it immediately.

Removed ambassadors stop receiving artefacts but their past share-actions stay in your analytics (audit trail).

Billing reality check

You pay $0.09 / month per active ambassador. Active means joined ≥ 15 days ago AND active in the last 30 days. So an ambassador who joins and ghosts is free; one who actually engages costs you nine cents a month. Most brands settle around 50-200 active ambassadors.

6. The ambassador relationship

SMB does not enforce a contract between you and your ambassadors. It's a tool, not a binding agreement. Whatever obligations exist on either side are between you, not us. But to keep things clear, here's the soft norm SMB encourages:

What an ambassador agrees to (by accepting the invite)

• They're acting in good faith — they like your brand or its mission, at least somewhat.
• They'll be honest if they ever stop wanting to. They leave the program; they don't bad-mouth anonymously.
• They follow each platform's disclosure rules (#ad, "paid partnership", etc. — even if you're not paying them, an ongoing relationship should usually be disclosed).

What you owe them

• Clarity: what are they expected to share? How often? Is there compensation, recognition, perks?
• Attribution: when they share, you credit them. A regram, a story repost, a thank-you DM — pick one and do it consistently.
• An exit door: they can leave any time. SMB makes that one click.

What you don't owe them

• Equal time. Some ambassadors will get more attention because they share more. That's normal.
• Every artefact. You can curate which classes see what.
• Justification for content choices. It's your brand.

7. FAQ

Can I see what each ambassador shared?

Yes — open any ambassador's profile from /ambassadors/, you'll see their share + view + click history. We track this passively when they hit the Share buttons inside SMB. We don't crawl their public profiles.

Can I edit an artefact after ambassadors have shared it?

The artefact in your bucket updates. The ambassador's already-published post on Instagram / X / TikTok / etc. obviously doesn't — those live on their respective platforms.

What happens to my data if I cancel?

30 days of retention. Sign in within that window and the account restores automatically. After day 30, all data is purged — no recovery. See the Privacy notice for the specifics.

Is SMB a CRM?

No. We track the content side of the relationship (what you posted, what they shared). We don't track the human side (your DMs, contracts, payouts, personal notes). Keep those in a real CRM (HubSpot, Notion, an actual spreadsheet) — link to SMB from there if you want.

Can I export my data?

Ambassadors: Export CSV button on /ambassadors/. Artefacts: Export CSV button on /bucket/. Files: download from the artefact detail modal. Full GDPR-style export of everything, including audit trails: email [email protected] and we'll send you a zip within 14 days.

Is there a mobile app?

No, and not soon. The web app works on phones — open /bucket/ in Safari/Chrome on your phone, hit "Add to home screen" if you want an icon. A native app would force you and your ambassadors into App Store install + update cycles for marginal extra capability; the web works, so we stay there.

Can I use SMB for influencer marketing where I'm paying ambassadors?

Yes — SMB is agnostic on whether the relationship is paid. We just don't handle the payments. Use Stripe Connect, a manual bank transfer, gift cards, whatever your jurisdiction expects. Track it in your accounting system; we have nothing to add there.

What if an ambassador shares something inappropriate?

Remove them from the relevant class (or the org entirely). Their past actions stay in your audit log. SMB has no moderation layer of its own — the ambassador's platform (IG, TikTok, etc.) handles content moderation; you handle relationship moderation.

How do I know if my CompanyEmail is set right?

Try the post-upload notify modal once with a tiny test class. If the To: field in your mail client shows the address you'd want to be the From: when emailing your ambassadors, you're set. Edit on /org/ otherwise.