November 13, 2026
What to Ask About Where Drafts and Notes Are Stored Before You Connect Your Inbox
Most of the worry about connecting an assistant to email centers on what it can send. The more useful questions are about what it keeps. Every draft, meeting summary and account brief it produces has to live somewhere, and a firm that cannot say where is taking on a risk it has not measured. A short set of questions, asked before the connection is switched on, settles most of it.
Access is one decision, storage is another
Granting an assistant read access to an inbox feels like the big decision, and the permission screen makes it look that way. But access is only the start. Once connected, the tool reads messages, writes drafts, summarizes threads and often stores notes about contacts and conversations. Each of those outputs is a new copy of client information, and copies are where exposure tends to happen.
A team should treat the two questions separately. Who can read the inbox is one answer. Where the things the assistant creates are kept, and for how long, is a different answer, and it is the one vendors explain least clearly.
Where do drafts actually live
The simplest arrangement is that drafts are written straight into the firm's own mail system, in the drafts folder, and nowhere else. A person reviews them there and sends them or deletes them. Nothing about the draft sits on an outside server once it is saved.
Some tools work differently. They compose drafts in their own interface, store them in their own database, and push a copy to the inbox only when someone approves. That is not wrong, but it means there are two copies, and deleting one does not delete the other. A firm should ask plainly: when a draft is created, how many places does it exist, and what happens to each copy when it is sent or discarded?
Call notes and summaries need the same answer
Meeting notes are often more sensitive than email. A call summary can contain pricing, staffing concerns, a client's internal politics and things nobody would put in writing to the client. If an assistant writes those summaries, the firm needs to know whether they are saved to its own document storage or CRM, or kept inside the vendor's system.
The safer pattern is that notes land in a place the firm already controls and already backs up, under the same permissions as the rest of its client files. If notes stay inside a separate tool, the team should check who at the firm can see them, whether that matches who can see the matching client folder, and whether they are included when someone searches for records later.
Questions to ask the vendor, in writing
A short written list keeps the conversation specific. Five questions are worth putting to any tool before it touches the inbox. Where are drafts, notes and summaries stored, and in which country? Is any of the firm's content used to train or improve the vendor's models, and can that be switched off by contract rather than by a setting? How long is content kept after it is sent, deleted or the account is closed? Who at the vendor can view stored content, and under what circumstances? And can the firm export everything the tool has stored, then get confirmation of deletion when it leaves?
Answers given on a sales call should be checked against the actual terms of service and data processing agreement. Where the two disagree, the written document is the one that counts.
Match storage to the firm's existing rules
Most firms already have rules about client files, even informal ones: what goes in the shared drive, who can open which folders, how long records are kept. The easiest way to judge a new tool is to ask whether its storage follows those rules or creates a parallel system with its own.
A parallel system is not automatically a problem, but it has to be managed. Someone needs to own it, check its permissions when people join or leave, and include it in any request to locate or delete a client's information. If nobody is willing to own it, that is a sign the tool should write to existing storage instead.
Start narrow and widen later
A team does not have to connect everything at once. A sensible first step is to connect a single inbox, with drafts written only to that inbox's drafts folder and notes saved to one agreed location. Run it for a few weeks. Check where things actually ended up, not where the setup screen said they would go.
Once the team is confident the outputs land where expected and nothing is kept elsewhere longer than agreed, adding more inboxes or more types of output is a small, informed decision rather than a leap.
A routine to try before the next connection
Before switching on any assistant that touches email, write a one-page storage map. List each thing the tool will produce: drafts, call notes, summaries, contact records. Next to each, write where it will be stored, who can read it, how long it is kept and how it is deleted. Fill in any blank by asking the vendor in writing.
Review the map with whoever is responsible for client data at the firm. If every line has an answer the team is comfortable with, connect one inbox and check the map against reality after two weeks.
Key takeaways
- Inbox access and output storage are separate decisions, and storage is the one that is usually explained least.
- Drafts written directly into the firm's own drafts folder are simpler to control than drafts kept in a second system.
- Ask vendors in writing where content is stored, how long it is kept, whether it trains their models and how it is deleted.
- Write a one-page storage map before connecting, then check it against what actually happens after the first few weeks.
Questions, answered
What is the short answer on What to Ask About Where Drafts and Notes Are Stored Before You Connect Your Inbox?
Connecting an assistant to a firm's inbox is mostly a question of where things end up. Before granting access, a team should know where drafts, call notes and summaries are kept, who can read them, and how they are removed.
What are the key takeaways?
Inbox access and output storage are separate decisions, and storage is the one that is usually explained least. Drafts written directly into the firm's own drafts folder are simpler to control than drafts kept in a second system. Ask vendors in writing where content is stored, how long it is kept, whether it trains their models and how it is deleted. Write a one-page storage map before connecting, then check it against what actually happens after the first few weeks.
How does VIPMarketing approach security?
VIPMarketing is a hosted, private workspace. Your documents and records stay yours and never train a model, and every draft is approved by a person before it is sent.