Social24 CRM

Social24 CRM

Mailbox-first

Nano context

Semantic recall

Workspace-safe

Creator outreach that remembers the whole relationship.

Social24 CRM turns Nano lists, mailbox conversations, creator profiles, and template history into one focused outreach cockpit.

Review inbox

1 inbox

for every creator thread

0 duplicate

contact ownership

15 min

default sync rhythm

Outreach cockpit

Hot creators

42 contacts

Awaiting reply

18 threads

Needs follow-up

9 reminders

NEXT BEST ACTION

Reply with the right creator context

Synced

Social24 found 3 useful signals

Latest reply mentions pricing and product usage.

Nano profile labels match this campaign segment.

Template history suggests a shorter follow-up.

Open rate

64%

Replies

31

Queued

128

From creator list to clean follow-up in three steps

The workflow starts where the team already works: Nano lists and real mailbox history.

  1. Step 1

    Bring in the campaign list

    Import creators from NanoInfluencer projects, CSV review flows, or manual additions without breaking the source-product identity boundary.

  2. Step 2

    Connect the mailbox timeline

    Bind a mailbox, sync real conversations, and preserve outbound-first onboarding so existing outreach does not disappear.

  3. Step 3

    Work the next best action

    Use labels, queue state, templates, and semantic recall to decide who needs a reply, a nudge, or a new campaign angle.

Built for the messy middle of creator outreach

Social24 CRM is not a generic sales database. It is shaped around creators, inbox context, campaign folders, and real follow-up pressure.

Audience

Mailbox history stays attached

Mailbox

Nano lists remain the source of truth

Template

Mailbox history stays attached

Signal

Nano lists remain the source of truth

Mailbox history stays attached

Inbound and outbound messages become part of the creator record, so every reply carries the conversation that led to it.

Nano lists remain the source of truth

Campaign folders and creator context flow into CRM without forcing old Nano users to register for a second product.

Audience

Templates learn from real work

Mailbox

Workspace boundaries are explicit

Template

Templates learn from real work

Signal

Workspace boundaries are explicit

Templates learn from real work

Previous outreach examples and approved templates are retrieved deterministically before any AI assistance enters the loop.

Workspace boundaries are explicit

Contacts, mailbox ownership, and semantic search all stay scoped by workspace so one team cannot accidentally read another team.

Where the CRM earns its place

The first screen is a workbench for repeated daily decisions, not a decorative database.

  1. Campaign managers

    See which creators are ready, waiting, interested, or stalled without switching between list exports and mailbox search.

  2. Outreach operators

    Move through a queue with profile links, prior replies, mailbox sync state, and template options already in front of you.

  3. Internal reviewers

    Audit imported contacts, resolve conflicts, and understand why a template or follow-up was suggested.

Designed around the systems we already trust

Every section maps back to real implementation boundaries: Prisma data, mailbox adapters, protected cron jobs, and Nano integration.

  1. Contacts and projects

    Projects group creators into outreach campaigns while contact links preserve profile identity across platforms.

  2. Inbox and sync jobs

    Mailbox sync is job-backed, observable, and safe to run without turning the user request into a long blocking task.

  3. Templates and recall

    Semantic search is authorized through MySQL records first, so vector results never bypass the tenant boundary.

  4. Admin visibility

    Queue and worker status stay visible to internal operators before the public product surface expands.

Social24 CRM vs.
spreadsheet-and-inbox outreach

Creator context

Mailbox work

Ownership

Follow-up memory

logo

Social24 CRM

Profiles, folders, mail, labels

Thread-aware queue

Workspace safeguards

Template and reply recall

Sheets + inbox

Links pasted into cells

Manual inbox search

Shared sheet ambiguity

Copy from old docs

Creator context

Social24 CRM

Profiles, folders, mail, labels

Sheets + inbox

Links pasted into cells

Mailbox work

Social24 CRM

Thread-aware queue

Sheets + inbox

Manual inbox search

Ownership

Social24 CRM

Workspace safeguards

Sheets + inbox

Shared sheet ambiguity

Follow-up memory

Social24 CRM

Template and reply recall

Sheets + inbox

Copy from old docs

The internal bar for the product

What this homepage should signal before public launch

Less hunting, more deciding

The CRM should make it obvious which creator needs the next action and why. The page should reflect that same operational calm.

Campaign lead

Daily outreach

Design target

The inbox is not an afterthought

Every useful creator relationship already lives in mail. Social24 keeps that timeline attached instead of making the team reconstruct it.

Mailbox operator

Sync and replies

Design target

No second identity tax

Existing Nano users should feel like CRM is a natural workspace extension, not a separate system asking them to start over.

Product owner

Nano integration

Design target

Frequently asked questions

Short answers for the product boundary this homepage is setting.

A calmer outreach workbench is taking shape

The CRM workbench is currently private while the first launch is being tested.