Skip to content

Marketing

Plan the program, capture the lead, and keep publishing a person's decision.

Programs hold the campaigns beneath them. Forms capture leads and credit the campaign that earned them. A blog post, an email or an event moves through draft, review and approval — and a person still carries out the step that leaves the workspace.

What Marketing is

A program groups related campaigns under one objective; open a campaign to see its own sequences and steps.

A form captures leads and can be linked to a campaign, so a submission's channel is credited to the effort that earned it.

Publishing, sending and streaming stay a person's own action: a blog post, email or event moves through draft, review and approval, and a person performs the step that actually leaves the workspace.

An event of kind webinar links to a Studio webinar production: Studio delivers that event's own sealed, approved sessions to its registrants, rather than a second, separate registration list.

Work it supports today

Each of these starts on a real page in the product. Nothing here is planned or promised.

  • Start a program and its first campaign

    A program with an objective, and a campaign beneath it ready for sequences and steps.

    1. Open Programs and choose New program.
    2. Name it and describe the objective.
    3. Open the program and choose New campaign.
    4. Give the campaign its own name.
  • Capture leads with a form and credit the campaign

    A published form linked to a campaign, with submissions visible on the form's own page.

    1. Open Forms and open the one you want, or start a new one.
    2. Link it to a campaign.
    3. Publish it.
    4. Watch submissions arrive on the form's own page.
  • Move a blog post from draft to approved

    A post that has passed review, with its SEO checklist visible the whole way.

    1. Open Blog and open a post, or start one.
    2. Request review when it's ready.
    3. An approver holding marketing.approve decides it.
    4. Once approved, publish it yourself.
  • Plan an event's run-of-show

    An event with its agenda set, moving between draft, scheduled and rehearsal as it comes together.

    1. Open Events and open one, or start it.
    2. Set the agenda across its sections.
    3. Move it between draft, scheduled and rehearsal as it's ready.

By hand: capture a lead from a form and follow up

Devon Okafor at Larkspur Analytics fills in the contact form on a campaign landing page; Priya Anand works the reply.

  1. Priya opens Marketing, then Forms, and opens the contact form's page.
  2. She sees Devon's new submission listed with his answers.
  3. She opens CRM, then Leads, and creates a lead for Devon with source: form.
  4. Back on the campaign page, she records the form touch by hand, crediting this campaign.

Fictional names. Start here: /marketing/forms

Or let Noc do it

Noc plans the steps, previews every effect, asks before anything irreversible, and hands back one receipt. Autopilot is off by default.

“Noc, this submission is from a lead I've already created: credit the campaign, record the signal, route it, mark it working, and set my follow-up.”

  1. Read the form's submission evidence — its state, campaign link and how many replies it has had. Nothing is written.
  2. Identify the lead this submission belongs to. Noc never creates one: you name it, or it's the record this goal was raised on.
  3. Credit the campaign with this form touch, and record the intent signal so the lead's score reflects it. Neither is undone, so Noc asks first.
  4. Route the lead by the workspace's current rules, and mark it as being worked.
  5. If you already wrote a reply, confirm the draft is ready. Sending it stays with a person, since no sending provider exists in this build.
  6. Create the follow-up task on the lead's company.
Before anything irreversible
Before crediting the campaign, recording the signal, or moving the lead's status, Noc previews the exact change and asks for your confirmation first.
What you get back
One receipt per step that ran, written in the same transaction as the change it describes, and one terminal receipt for the whole request.

Capabilities this plan can use: 8. Each is registered, permission-bound and previewed.

What stays in your hands

  • Your permissions decide, every time

    Reading needs marketing.read; changing needs marketing.write; approving needs marketing.approve. Campaigns and leads carry their own read/write permissions. Noc carries your permissions and never more.

  • Publishing and sending are asked for, never assumed

    A post, email or event is prepared and confirmed by a person; nothing here sends a message or publishes a page by itself.

  • A live event is a state, not a stream

    Marking an event live records that a host is running it; it is not a claim that anything is being streamed, because no streaming provider exists.

The honest states

What the product really shows when there is nothing yet, when it refuses, and where this build stops.

  • What you see first

    A new workspace has no programs yet

    Programs shows nothing until the first one is created; there is no sample program or campaign.

  • When something is refused

    Noc never creates the lead for you

    If a submission has no lead named, Noc reports the refusal plainly — creating a brand-new record stays a person's decision — rather than inventing one.

  • Not available in this build

    No invitation, reminder or campaign email sends itself

    Sending is blocked_no_provider: the message is prepared and confirmed, and a person sends it with their own tools.

  • Not available in this build

    No event is actually streamed

    "Live" is a state a host sets on the event record, not a claim about a streaming provider — none exists in this build.

Next

To see Marketing you need a membership in a workspace. Acting needs the permissions your administrator grants.