Point holds a line between the businesses you run. Each one keeps its own mail, its own people and its own record, and what’s in one stays there. The line follows a business rather than a client, and that difference is what decides whether this is the control you came looking for.
- Two different requests arrive in the same words. Only one is about the boundary. The other is about what you’d rather not look at this morning.
- The line holds on what crosses between them. Both businesses can be in front of you at once and still be apart.
- The mistake this prevents is an identity slip: the reply that went out under the wrong firm’s name because two windows were open.
- Every other control in this collection is set on one side of the line, so a second business starts with its own set of answers.
Two requests inside one question
Ask for two businesses kept separate and you could mean one of two things. They have different answers.
The first is about attention. You do the accounts on a Tuesday, and you’d rather the property company’s suppliers sat somewhere else while you work. Nothing is at risk here. You just don’t want to be looking at it yet.
The second is about crossing. What belongs to one business stays in that business: its mail, what your assistant learned there, the people who work in it. This one is a line. It holds or it doesn’t.
Point answers them separately, so it’s worth knowing which one you’re asking. The expensive way to solve an attention problem is to build a boundary you didn’t need. If what you want is work and home landing in different piles, that’s sorted inside a single business. Each message goes to the part of your life it belongs to, and one business covers it. Set up a second business for that job and you’ve bought two of every control on this page to solve something a filter already solved.
What the line is drawn around
The unit is a business you operate. Something with mail arriving in its name, people who work in it, obligations that belong to it, and a name at the foot of a reply. The practice and the property company. The consultancy you own, and the second firm where you took on a role and now help run the place. Two things that would each have to exist if the other closed tomorrow.
A client isn’t that unit, and this is the one place worth being exact about rather than comfortable about. The line runs between the businesses you operate, not between one of your clients and another. There’s no arrangement in which each client’s mail is sealed off inside your own firm. Anyone telling you otherwise about any tool is describing something else, usually storage, and calling it isolation.
That’s the right unit, for a reason you already know from your own week. A firm’s work divides by client badly. One thread names two of them. A question about a deadline belongs to the practice, whoever asked it. The thing that has a mailbox, a team and a letterhead is a business, so a business is what a boundary can honestly be drawn around. Draw it around a client and half your correspondence sits across the line.
What you have inside one business is narrower and more useful. Nobody outside that business’s own people is in it. What your assistant did there is recorded there. What you must tell clients about a tool that reads their correspondence is a professional question rather than a setting, and it lives in what confidentiality means when AI reads client mail.
Both in front of you, and still apart
The intuitive version of separation is hiding. Hiding is the weaker half of it.
Without a boundary you get two windows. One business per browser tab, or one per app, and you move between them all day. It hides very well. It also produces the one failure people arrive here with. The thing you missed was in the window you weren’t looking at, and you found out on Thursday.
So Point shows every business you belong to in one feed, and every card says which business it belongs to. That single piece of labeling is what makes one surface safe to use. The risk of a merged view was never seeing the other business. It was being briefly unsure which one you were reading.
When you want the narrower view, one switch lists the businesses you belong to, and one click takes the whole surface down to a single one. Filter to the other and the thread is simply not there. That’s the same isolation the two windows gave you, held for as long as you want it and no longer.
Then there’s the half that matters more, because it runs outward. Reply from the combined feed and the reply goes out inside the business the thread belongs to. You don’t pick an identity, so you can’t pick the wrong one. That’s the real cross-business accident, and it has always been a human one. Somebody with two addresses open, moving at speed, thinking about the sentence rather than the sender. Taking the choice away is what removes it.
The same holds when Point is working without you. Setting how much your inbox does on its own decides how far Point goes on a kind of work, and at the top of a setting Point goes ahead unasked. That setting says how far. Where the work happens comes from the thread. Work done on its own is still done inside the business whose thread it belongs to.
Two businesses means two of everything here
Each control in this collection is set on one side of the line. People meet this in week three and read it as a fault, so it’s worth stating plainly.
How far Point goes on a kind of work is answered within a business. A yes you gave belongs to the business you gave it in, which is the boundary in approving anything new before it acts. The record of what happened is kept per business, so the activity log behind every action is two records rather than one merged feed. Even the connection sits on one side, since the mailbox a business receives on is that business’s, and the keys live in the credentials that connect your mailbox.
So filing running on its own in the practice stays in the practice. The second business answers that question for itself. Nothing was inherited, and nothing should have been. A setting that spread across the line would itself be a thing crossing it. A permission that leaked from your busiest business into the one you look at on Fridays would be the exact failure this whole arrangement exists to prevent.
What it does mean is that the second business needs the same attention the first one got, and usually it doesn’t receive it. The pattern is easy to describe and easy to fall into. You watch the main business closely and raise settings there as you get comfortable. The smaller one runs on whatever it started with, which is review. That’s a safe place for it to sit, so nothing goes wrong, and nothing is handed over either. A year later you’re still clearing a queue in the business you barely think about. The other order is worse and rarer: raising a setting in the business whose record you never open. Raise where you’re watching, and watch where you’ve raised.
Where the separation stops
One mailbox is one business. If both businesses have been running through one address for years, that address is one business as far as any software can tell. The boundary follows the mail, not your sense of which hat you were wearing. Two businesses sharing an address is a bookkeeping arrangement you already live with, and separating them is a job that starts with a second mailbox rather than with a setting.
You can reach both. You belong to both, so both are open to you, and that’s the design working. The line governs what crosses between the businesses and who else stands on each side. Your own company stays yours to look at.
A person you put on both sides is on both sides. Invite the same colleague into two businesses and they’re in two businesses. That’s the answer to the question rather than a hole in it, and it means the guest list is the control here. Deciding who is in a business is the same act as deciding what they can see of it.
Where data is held is a separate question. Separation inside a product and separation inside a supplier’s systems are two different sentences, and only one of them is answered by anything on your screen. Storage, retention, who at a vendor could reach a record, and what happens to it when you leave are things to put to a company in as many words. The list to put is questions to ask any AI tool about your data.
This page describes a boundary for a reader who wants to know its shape. Handing work over is a separate decision, and it stays yours. If two businesses are on your mind because trusting one of them to a tool still feels early, running more than one business through it takes the same ground from the other end. The benefits page is the inventory of what there is to hand over in the first place.
Common questions
Can I keep each client’s email in its own separate space?
No, and it’s better to know now than to find out later. The line Point holds runs between the businesses you operate. A client sits inside a business rather than beside it, somebody your business corresponds with. What you get instead is a business that’s closed: closed to the other businesses you run, and closed to anyone you haven’t put in it. If the question underneath is what you’re obliged to tell clients about a tool with access to their correspondence, that’s a professional question with a professional answer, and it lives in AI and client data for accountants.
If both businesses show up in one feed, in what sense are they separate?
In the sense that matters, which is what crosses rather than what you can see. Every card names the business it came from. One switch narrows the whole surface to a single business. A reply leaves inside the business its thread belongs to. Keeping them in two windows would hide more and protect less. Hiding gives you a smaller view, and the thing you missed was usually in the half you had closed.
Could a reply go out from the wrong business?
The thread already belongs to a business, and the reply is sent inside it. You never select an account, which is what takes the mistake away. That holds at every position of the dial for replies. Where the setting is at review, you’re releasing words that were already addressed to the right side of the line. Where you’ve raised it and Point acts without asking, the acting still happens inside the thread’s business. The setting changes how far, never where.
Do the people in one business see the other one?
Only if you put them in both. Membership belongs to a business. Someone invited into one is in one. Someone in two is in two by a decision you made, rather than by drift. Treat each business’s invite list as part of this control rather than as administration. It’s the single place where the boundary is decided by a person instead of by the software.
Do I have to set the controls up twice?
Yes, and that’s the boundary being real rather than a step somebody forgot to build. Settings that copied themselves across would be information moving between two businesses that are supposed to be closed to each other. The practical version is that a second business begins where the first one began, on review, and reaches wherever you take it. It’s the same two weeks of watching and raising you did the first time. Assume it arrived already configured like the other one and a queue builds quietly in the business you think about least.
The short version
The boundary runs between businesses you operate, and it holds on crossings rather than on visibility. Both can be in one feed, each card saying whose it is. A switch narrows to one when you want the narrower view. A reply leaves inside the business its thread came from, and you don’t choose. Where the line stops: a client sits inside a business, one shared address is one business, and both companies stay open to the person who runs them. Everything else here is set on one side of it, which is why a second business is a second set of decisions. Point is where the switch lives.