Two weeks ago
Pricing form: wants to run two brands out of one workspace, and asked what happens to the second brand's people.
Written by the platform when the form arrived on your site
Contacts
People, stages you name yourself, and a history that writes itself when something real reaches somebody. A newsletter that truly landed appears on that person's timeline without anyone remembering to log it, and every message that reaches a human left because a human sent it.
Contacts, close up
Where people come from
What happens to it
Where you work with it
What is travelling those lines
This is the same map as the one on the front of Solutions, zoomed into one surface. People arrive through a brand's own forms, work moves along stages you named, and everything pointed at a real human stops in the middle and waits for you.
What it does
A newsletter that truly reached somebody writes a line on their timeline by itself, carrying the subject and the moment it landed. A skipped, suppressed or capped delivery writes nothing. That is the whole point: what you read back is what reached them, not what you queued.
A funnel is a name and an ordered list of labels you type. A brand can run several at once, and a person can sit on more than one of them at a time, in a different place on each.
Putting somebody in a stage is refused unless the stage exists in that funnel and the funnel belongs to that person's brand. Refused with the stages that would have worked, so a person or an agent can correct it on the spot instead of guessing.
Identity is the email address inside one brand. The same address in two of your brands is two people with two separate histories, and nothing joins them. Two brands that share a customer do not share what was said to them.
Phone calls, meetings, emails, demos, onboarding sessions, notes and proposals arrive with every brand. Add a Site Visit or a Contract Review with its own name, icon and colour and it shows up in that brand's picker only.
Try to remove one that entries are still filed under and you are told how many, then offered the safer move: switch it off so it leaves the picker while everything already logged keeps its name and its icon.
An instruction you wrote can read what you know about somebody and the brand's own positioning, judge how well they fit, and draft the message, using your own AI key. It ends at a saved draft you can edit. You read it before anything reaches anybody, and you send it from your own account.
Every delivery is checked against the suppression list, against the same template having already gone to the same address inside the window, and against the brand's own cap. A blocked one is skipped and recorded rather than retried into the ground, and a list past the cap waits for the next drain instead of blasting.
One person, close up
This is one person\'s timeline, in the order it fills in. The locked lines were written by the platform because something really happened: a form arrived, an email was delivered. The rest are yours, logged by hand and yours to change. Nothing had to be imported, and nothing had to be remembered at the end of a long day.
Two weeks ago
Pricing form: wants to run two brands out of one workspace, and asked what happens to the second brand's people.
Written by the platform when the form arrived on your site
12 days ago
Walked the board and the history. They want the stage names to match the words they already use, so we renamed them on the call.
Logged by you, completed
6 days ago
Sent: the August product note
Written by the platform when the newsletter actually reached them
4 days ago
Asked for a second board for onboarding, kept separate from the sales one.
Logged by you, completed
Next Thursday
Set their two brands up together, an hour.
Logged by you, assigned to you
The two locked lines are the record of something that actually reached this person, so nobody gets to tidy them up afterwards. Their wording cannot be rewritten and the lines cannot be removed: not by you, not by anybody else in your workspace, not by a connected agent. The person\'s record refuses the edit and refuses the delete, and the studio does not even offer the buttons.
It is the wording and the line itself that are closed, and we are not going to tell you it is more than that. The same line carries a date, a status and an assignee, and those can still be changed from the calendar, which does not ask where a line came from. So a real send is something you can move, reassign or close off, and never reword. Deleting the person takes their history with them.
Your stages
There is no standard pipeline in here to bend your work around. A funnel is a name and an ordered list of labels, stored as a list, and every part of it stays editable. A brand can run several at once, and the same person can sit on two of them in a different place on each.
Seeded once, so the board is not a blank page on the first morning. Every label is yours to rename, reorder or throw away, and the starting set never comes back to overwrite you.
It opens as one empty line with the starter set one click away. An onboarding board that arrives full of sales words just means deleting them, so it does not arrive that way. It will not save without at least one stage on it.
Moving somebody is refused unless the stage exists in that funnel and the funnel belongs to that person\'s brand, and the refusal names the stages that would have worked. Your readouts then count people under these labels, not under somebody else\'s.
Where this sits
A person record is only worth having because of what points at it. Each of these has a page of its own you can read.
The newsletter you broadcast is one of your own templates, and a delivery that truly landed is what writes the line on somebody's history. Read that page for how the templates themselves are drafted and approved.
Read EmailsThe instruction that judges how well somebody fits, and the one that drafts the message, are records you can open and rewrite per brand. Nothing about how your outreach reads is buried out of reach.
Read PromptsA task, a note or a decision can point straight at the person it is about, so it is findable from either end and the reasoning does not end up in a document nobody can name.
Read ArtifactsWhat a connected agent may do with all of it, and the shorter list of what it may not: no send, no subscribe, no suppression.
Read Your agentYours to keep
Every one of these we would choose again.
Stage names and activity types are yours to write. Nothing here asks you to describe your own work in somebody else's nouns before it will hold it.
A drafted message has no send path at all. A newsletter goes when a person with that permission sends it. Nothing goes out because a date passed or because something was recorded elsewhere in the workspace.
A line the platform wrote cannot be reworded or removed, by you, by anybody in your workspace, or by an agent. History that can be edited into a better story is not history.
A person joins a brand's audience by their own click on that brand's form. There is no import, no paste and no add button, and that is a decision rather than a gap.
An unsubscribe is kept against the address, so deleting somebody does not quietly make them contactable again.
Stages, activity types and people are all held per brand. The same address in two of your brands is two people, and neither one can see the other's history.
Questions
Keep reading
The templates a broadcast picks from, drafted and approved before anything goes out.
The instructions behind the fit judgement and the draft, as records you can rewrite.
Where the work that belongs to a person you are dealing with actually lives.
The full boundary: what an agent may touch here, and what stayed with people.
Open the workspace, do one real piece of work in it, and the joins will show you the rest.