You advise several clients at once. Your assistant knows the option being debated for one client, the dependency blocking another, and the question a third promised to answer. The practical risk is not lack of context. It is sending the right context to the wrong person.
For independent consultants, fractional leaders, and specialist advisers, RelayLink works best as one personal account with separate client relationships and threads.
Use one consultant identity
Your RelayLink account represents you: your email, your display name, your inbox, and the correspondence you approve. Use that account across your client portfolio.
Do not create a separate account for each client. A client is not one of your identities. They are the recipient of a package, and sometimes an accepted contact. Creating or sharing credentials in their name would blur who reviewed the message and who controls the inbox.
If you use several assistants yourself, they may connect to your one account. Give each integration its own OAuth connection or named key so you can disconnect one without disturbing the others.
A client can remain on email
The client does not need an activated account to receive value. Address the briefing to their email. They receive a notification, read the package on the web, and reply from the page or by email.
This is often the best fit for occasional clients, executive sponsors, or specialists who only need to answer a scoped question. Do not turn a request for feedback into software onboarding.
If the client signs in, they activate their account-owned inbox and may connect an assistant. Starting a new thread then requires an accepted contact relationship. Send a contact request and let them accept. The request carries no pitch or project context; the actual briefing follows consent. A refusal is not proof that the address has an account. Inviting a contact covers that path.
The existing cold thread can continue after activation, unless either side blocks the other.
Separate work by conversation
Use threads to keep client work logically distinct. One thread might cover a pricing decision, another an implementation risk, and another a contract question. Packages on a thread carry that conversation forward without requiring the recipient to reconstruct it from your private assistant session.
Client separation here is not a claim of a different cryptographic key per thread. It is an application and workflow boundary: each package has a recipient and thread, and your authenticated account can work only with correspondence it participates in.
Name topics concretely. “Northwind launch date” is safer than “Quick question.” Before approving, check the displayed recipient, address, topic, and ask. Similar client names are exactly where a polished draft can create false confidence.
Let the assistant structure, not authorize
Your assistant can turn working notes into a briefing with a direct ask, concise context, assumptions, options, and open questions. It can identify which claims came from you and which it inferred.
You remain the sender. RelayLink creates a draft and returns a preview. Delivery is a separate confirmation after you review it. If the model overstates your recommendation or includes context meant for another client, correct it before confirming.
The approval step matters because consulting correspondence often changes scope, budget, or responsibility. “The assistant wrote it” is not a useful answer after the client acts.
Build a repeatable client routine
For each piece of correspondence:
- Choose the person, not merely the company.
- Choose the existing thread or start a clearly titled one.
- State the decision, review, or information you want back.
- Ask the assistant to draft for a cold reader.
- Review the preview and confirm only when it says what you mean.
Use private nicknames to find contacts quickly, but keep internal labels out of client-facing prose unless you deliberately permit the client to see that word. The nickname helps select the person; it does not become their display identity.
Where RelayLink is not enough
RelayLink fits a consultant writing a specific person with context and a real ask. It does not replace your CRM, document repository, billing system, or shared client workspace. It is also not a campaign tool for prospecting at scale.
If several agency employees need shared ownership of every client record, read RelayLink for agencies. A solo consultant's personal correspondence model is simpler: one identity, many recipients, separate threads, and approval on every send.