Work with Bridget over email

Essentials#

Read before sending the first email.

What Bridget is#

Bridget is an AI research agent in Teamroom, the platform that hosts your projects. It runs internal and external primary research, drafts and revises interview guides, synthesizes findings with supporting evidence, and produces documents, data tables and slide decks.

Bridget always works inside one project and uses only that project’s files, sources and tools. Each project has a compliance template. Bridget takes only the actions that the template, your project permissions and the enabled tools allow.

Projects#

A project is a shared workspace in Teamroom for one engagement or research question. It holds the files you upload, interview studies and their transcripts, notes, data tables, decks, the people who are members, and the compliance template. Bridget saves everything it produces to the project, so members can open it in Teamroom.

You must be a member of the project. Send from the email address of your Teamroom account. If you aren’t a member of the project you name, Bridget won’t do the work. Its reply lists the projects you do have access to.

Choosing a project. Bridget matches each new thread to a project. Plain language works, in the same email as your task or on its own. The quoted lines below are just examples.

• Say which project. Name it anywhere in the email, for example “Project: [your project name]”. Bridget also recognizes a project from a clear description of its work, such as the company or market it covers, or from interviews it is running.
• Ask about your projects. Ask Bridget about the projects you have access to, for example “Which projects do I have?” or “What am I working on?”. It replies with every project your account can use.
• Create a project. Ask for a new one and give it a name, for example “Set up a new project called [name] and summarize the attached deck.” Bridget creates the project, then runs the task in it. If you don’t give a name, Bridget proposes one and waits for you to confirm. Your task runs once the project exists, so you don’t need to send it again.

If Bridget can’t tell which project you mean, it asks you and offers the likely matches. Reply with your choice.

Bridget remembers your project for two weeks. When you choose a project, Bridget remembers it as your current project for two weeks. If a new email doesn’t clearly point to a project, Bridget uses the remembered one rather than asking again, as long as you still have access to it. Each new choice restarts the two weeks. To work somewhere else, name that project.

Sending an email#

Email Bridget at:

bridget@m.teamroom.ai

Include:

• the project (see Projects)
• your objective
• the sources or attachments to use
• the output you want

Bridget may ask clarifying questions, send interim updates, and return results or files in the thread. Every reply links to the work in Teamroom.

Questions can have a time limit. A question from Bridget may say how long it will wait for your answer. If no answer arrives in that time, Bridget goes ahead with its defaults. The time limit varies, so read each question and reply in time if the choice matters to you.

While a task is running, Bridget may not reply until it finishes. Wait for it; don’t resend the request.

Copying colleagues. You can cc colleagues. Bridget copies its replies only to people who are members of the project. Anyone cc’d who isn’t a member is removed from the reply, and Bridget says so. To include them, add them to the project in Teamroom first.

Threads#

Use one email thread per task. Each thread belongs to one project, and every reply in it runs there. Bridget sees the earlier messages in the thread, the files sent in it and the work it has already done, so you don’t need to repeat yourself.

To continue a task, reply to Bridget’s latest email in that thread. This includes answers to its questions, approvals, revisions and follow-up analysis. In a mail client, use Reply or Reply all. A new email with the same subject starts a new conversation, and Bridget won’t see the earlier context. Start a new thread only for a separate task.

Connecting an agent#

You can have your own AI agent email Bridget for you. No Bridget SDK or API key is needed. The agent needs:

• A mailbox Bridget accepts. The agent sends from the email address of a Teamroom account that is a member of the project.
• Send and receive. The agent can send email with attachments and set reply headers (In-Reply-To, References).
• Inbox monitoring. The agent watches for Bridget’s replies, questions and interim updates, and checks at the times given in each workflow (rules in Timing and status checks).
• This guide as instructions. Give the agent the plain-text version of this guide. Download the agent text.

Project context#

Do once per project, then keep current.

Save project context#

Bridget knows only what is in the project. Before the first task, send it the background it needs, and ask it to save that background to the project. Later tasks can then use it. For a task that is already running, send files in that task’s thread.

1. 1
   Email Bridget with the project name. Attach relevant briefs, background documents, prior research or other context, and ask Bridget to save them to the project for future work.
2. 2
   For each file, say what it is (source evidence, background, an approved question guide or a design reference), how to use it, any restrictions, and its date or version. Say if it replaces or conflicts with an earlier file.
3. 3
   Read Bridget’s reply and open the Teamroom link to check what was saved. Reply in the same thread if anything needs correcting.
4. 4
   Start a separate thread for each task in Task workflows. Refer to the saved context instead of sending it again.

Best practices#

Write a context brief

Bridget can’t see your local files or other Teamroom projects. Write a short brief, such as project-context.md or a Word document. Cover the objective, the decision it supports, background, definitions, known findings, open questions and constraints. Separate confirmed facts from assumptions and include sources.

Mark examples as references

Attach slides or reports from similar work that you are allowed to share. Point to the useful sections or slide numbers, and say what each one shows: narrative, depth, layout or tone. Say they are references, so their figures aren’t treated as evidence for this project.

Keep the context current

When a decision or assumption changes, send a short update and ask Bridget to update the saved context. Name the file and version so that later tasks use the right material.

Be specific when asking for changes

Open the Teamroom link in Bridget’s reply to check sources and content. Reply in the same thread with the question numbers, table fields or slide numbers to change, and what to change.

A good starting package is one context brief, the relevant source files and, optionally, an example deliverable. Keep the email short:

Project: [name]. Please save the attached context brief and sources for future work. The reference deck shows the storyline and layout we want; its figures are not evidence for this project. Confirm what was saved and flag missing or conflicting context. I’ll send each task in a separate thread.

Task workflows#

Read only the workflow for the current task. Use one thread per task.

Internal primary research#

1. 1
   Email your research goals and the internal audience you want to interview. Attach your question guide, or ask Bridget to write one from your goals. Say that you will provide the participants.
2. 2
   Before going further, Bridget sends back the guide as an editable Word file, with any questions about the study setup.
3. 3
   Reply with edits, or attach a revised guide. Bridget applies the changes and sends the updated materials for review.
4. 4
   When you’re happy, ask Bridget to launch. Give the participant details or ask for a shareable interview link. Answer any open setup or compliance questions.
5. 5
   Bridget confirms the launch and sends the interview link. If you asked for a shareable link, share it with your participants.
6. 6
   When responses come in, ask Bridget to synthesize the interviews. It sends findings, supporting quotes and evidence gaps, with a Teamroom link to the underlying material. Reply in the thread for more analysis.

External primary research#

1. 1
   Email your goals, target respondent profiles, geography, number of interviews, deadline and recruiting exclusions. Attach a guide and screener if you have them, or ask Bridget to write them.
2. 2
   Bridget sends back the screener and guide as editable Word files, and asks for any missing audience or study details.
3. 3
   Reply with changes or send back edited files. Before launch, review the revised materials, the respondent criteria and the credit estimate.
4. 4
   Ask Bridget to launch recruitment. Answer any remaining compliance or credit approvals in the thread.
5. 5
   Bridget confirms that recruitment has started. Use the Teamroom links to see the study and any responses. Ask Bridget in the thread for a status update whenever you need one.
6. 6
   When responses are in, ask for a synthesis and name the comparisons or questions to cover. Bridget sends evidence-backed findings. Reply for deeper analysis or follow-up questions.

These flows are for AI-moderated interviews. For now, you set up human-led live interviews in Teamroom.

Deep research#

Deep research produces a cited report from Bridgetown’s library and the web.

1. 1
   Email the research objective, key questions, geography, timeframe and report format you want. Name any library material or web sources to prioritize or exclude, and attach extra context if it helps.
2. 2
   Bridget sends back a research plan. The plan covers the questions, the scope, the source rules, and which project and library content it will use.
3. 3
   Reply with changes, or approve the plan and ask Bridget to launch. Bridget starts the research only after you approve the plan.
4. 4
   Bridget sends the finished report with citations and a Teamroom link to the report and its sources.
5. 5
   Reply with questions or corrections, or ask Bridget to investigate a specific gap. If that needs another research run, review the new scope before it starts.

Data tables#

1. 1
   Email a source spreadsheet or document, name an existing project table, or describe the list of companies you want researched. Give the rows, columns, geography, units and size, or ask Bridget to propose them. If you want to review the table structure before Bridget fills it in, say so.
2. 2
   Bridget asks for any missing details.
3. 3
   Reply with the agreed scope and any credit approval Bridget asked for. Bridget pulls rows from your material or finds matching companies, then researches each field.
4. 4
   Bridget sends the result with a Teamroom link to the table, its sources and any missing values.
5. 5
   Reply to add rows or columns, refresh fields, filter the table or ask for analysis. Bridget sends the updated result. More research may use more credits.

Slides from synthesis#

1. 1
   Send the synthesis, or say which project findings to use. Give the audience, the aim of the presentation, the key questions and roughly how many slides you want.
2. 2
   Optionally, attach your own slides and say whether they are layout references or content to revise. Without references, Bridget picks layouts from its library. Reference slides never count as evidence for new claims.
3. 3
   Ask Bridget to send the storyline before it builds the deck. Bridget replies with a slide-by-slide outline showing each slide’s message, its evidence and any gaps.
4. 4
   Reply with changes to the storyline, then ask Bridget to build the slides.
5. 5
   Bridget sends a download link for the editable PowerPoint and a Teamroom link. Reply with slide numbers and the changes you want, and Bridget sends a revised deck.

Meetings#

Bridget can join a call as a notetaker bot, then write up the meeting in the project.

1. 1
   Forward the meeting invitation to Bridget, or add bridget@m.teamroom.ai as a guest on the calendar event. Name the project, and say what you want from the meeting, such as notes, a summary or answers to specific questions.
2. 2
   Bridget reads the invite and offers to join. It books the bot only after you confirm. If it needs the meeting link or anything else, it asks in the thread.
3. 3
   Confirm in the same thread. The bot joins the call at the scheduled time.
4. 4
   After the meeting, Bridget saves the transcript to the project and writes up the meeting. Reply in the thread for follow-up analysis.

Bridget can’t join a meeting that has already happened. If you send an invite for a past meeting, Bridget replies to say so.

Reference#

Look up as needed.

Timing and status checks#

Each workflow gives a check time. Times count from your last message with the inputs or approval Bridget needs. They are typical, not promises. If Bridget gives an ETA, use that instead.

If nothing has arrived by the check time:

1. 1
   Look for an interim update or question from Bridget, and open the Teamroom link.
2. 2
   If it’s still unclear, ask for status in the same task thread.
3. 3
   No reply doesn’t mean the task failed. While a task runs, Bridget often can’t reply until it finishes.
4. 4
   Never resend the request or start a duplicate task.

Troubleshooting#

When Bridget can’t take on an email, it replies to say why. Find the reply below.

For anything else, email support@teamroom.ai (see Sending an email).