Skip to content

CRM

Know every company you work with, and what happens next.

One record per company, the people inside it, the leads and opportunities attached to it, and the next action on top. Nothing is hidden in a spreadsheet, and nothing changes without a person or a permission you gave.

What CRM is

A company is the anchor. Contacts, leads, opportunities, lists, relationships and tasks all hang off a company record, so the answer to “where do we stand with them?” is one page.

Every record belongs to your workspace only. Access is checked on the server for each request, and row-level security in the database refuses anything else.

The next action is a first-class thing: a task on a company, with a due date and an owner, that shows up where the work is.

Work it supports today

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

  • Add a company and the people in it

    A company record with its contacts, ready for leads and next actions.

    1. Open Companies and choose New company.
    2. Enter the name and what you know.
    3. Add a person from the company page.
    4. Set the next action so it is never forgotten.
  • Work a lead into an opportunity

    A lead with a status, an owner chosen by your routing rules, and an opportunity in your pipeline when it is real.

    1. Open Leads and pick the lead.
    2. Route it or assign an owner.
    3. Move its status as the conversation moves.
    4. Create the opportunity when there is one.
  • Bring in records you already have

    Your existing companies and contacts inside Noctessia, with every row you imported traceable to the file it came from.

    1. Open Import.
    2. Choose the CSV file.
    3. Match the columns.
    4. Review, then import.
  • Keep lists and geography in view

    Saved lists for the companies you are working, and a map of where they are.

    1. Open Lists and build one from your companies.
    2. Open Geography to see them placed.

By hand: a new company and its first next action

Priya Anand met Halden Rowe Joinery at a trade fair and wants to follow up next Tuesday.

  1. Priya opens CRM, then Companies, and chooses New company.
  2. She types “Halden Rowe Joinery” and saves. The company page opens.
  3. She adds a next action: “Call about the workshop extension”, due Tuesday.
  4. The task shows on the company page and in her work, until she marks it done.

Fictional names. Start here: /crm/companies/new

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, follow up on the new form lead from Halden Rowe Joinery: credit the campaign, route it, mark it working, and set the follow-up.”

  1. Read the form submission and the lead it belongs to. Nothing is written.
  2. Credit the campaign with the form touch and record the intent signal. These are not undone, so Noc asks first.
  3. Route the lead by your current rules; undo assigns the previous owner back.
  4. Mark the lead as being worked, and create the follow-up task on the company.
Before anything irreversible
Before any step that cannot be undone, Noc asks first: it shows the exact effect and waits for your confirmation. The confirmation is bound to that preview: if anything about the record changes in between, the plan is re-previewed instead of run.
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 goal. Skipped or refused steps earn nothing and claim nothing.

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

What stays in your hands

  • Your permissions decide, every time

    Reading needs companies.read; changing needs companies.write, people.write, leads.write or opportunities.write. Noc carries your permissions and never more: a step you could not do yourself is refused for Noc too.

  • Irreversible steps ask first

    A status move, an attribution credit or a new opportunity asks for your confirmation, and the confirmation expires. Creating a task is undoable, so Noc can do it and you can cancel it afterwards.

  • Pause and stop are yours

    You can pause a running goal between steps; a paused goal never continues on its own, and an emergency stop for the whole workspace refuses every new step.

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 shows an empty Companies list

    There is no sample data and no demo tenant. The first company is the one you add or import.

  • When something is refused

    A refusal says why

    If a record moved or was deleted while Noc was planning, the step is refused with the reason, nothing is written, and you can re-plan. If you lack a permission, the page says which one.

  • Not available in this build

    No outside discovery provider is connected

    Decision-maker discovery through external data providers is not available in this build; the record shows what you and your team entered.

Next

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