Workflow

Monitor Investor Follow-Up With a dot

Monitor Investor Follow-Up With a dot: give an always-on agent a recurring private-capital responsibility using permitted apps and reviewed Finta context.

By Finta Editorial TeamReviewed by Finta Editorial TeamPublished September 29, 2026Verified September 29, 2026Last reviewed September 29, 2026

A monitored follow-up queue shown beside reviewed Finta relationship context and the official dots mark.
Audience
Founders and investor-relations teams
Products
CRM, Networks, Documents, Share Pages
Prerequisites
An eligible ChatGPT plan with dots access, A Finta workspace or reviewed Finta artifact, Permission to use the selected records and documents
Expected outcome
a monitored follow-up queue
Approval boundary
A person reviews sources, relationship context, record changes, and every consequential external communication.

Direct answer: Give a dot an ongoing fundraising responsibility, the smallest useful set of connected context, and clear rules for what it may do. OpenAI's dots are always-on agents in ChatGPT, powered by GPT-6 Astra, with their own cloud computer and the ability to keep making progress between conversations. Pair that continuity with reviewed Finta relationship and deal context to produce a monitored follow-up queue. Keep every consequential relationship decision, record change, file share, and external message under human review.

Your dot keeps open commitments, unanswered questions, and due follow-ups visible while the relationship owner controls what is sent.

The job to give your dot

Keep investor follow-up current without turning a relationship into an automatic sequence. The useful shift is from asking an occasional question to assigning a continuing responsibility with a recognizable output, cadence, and approval boundary.

LayerWhat it contributesWhat remains controlled
FintaRelationship records, pipeline state, approved documents, meeting context, and recorded commitmentsFinta remains the source of truth for the fundraising workflow
Your dotOngoing research, synthesis, drafting, scheduled review, and progress between conversationsIt can use only the apps, accounts, and permissions you choose to connect
YouJudgment, corrections, consent, approval, and the final decisionYou set Custom Rules and review consequential work before it affects people or systems

Choose how your dot receives Finta context

Dots use ChatGPT's plugin ecosystem and connected apps. In ChatGPT, open Settings > Plugins, review the apps available to your account, and grant only the permissions this job requires. If Finta appears as an available plugin or approved connection, confirm the intended Finta organization and begin with retrieval. If it does not appear, use a reviewed Finta brief, approved Share Page, selected document, or export as a deliberate handoff. Do not treat a general ChatGPT or MCP connection as proof that every dot can access Finta.

  • Plugin path: Use only when Finta is visible in the dot's available tools and the requested permission matches the job.
  • Reviewed handoff: Provide the smallest useful Finta artifact when a direct connection is not available.
  • Browser or computer access: Enable only when needed. Local-computer access starts off and requires a separate user decision.

Set up the responsibility

  1. Create your first dot on desktop. Open dots in ChatGPT from the desktop app or desktop web. Initial creation is not available on mobile.
  2. Connect only the required apps. Confirm the exact accounts and permissions in ChatGPT's Plugins settings.
  3. Describe the job. Name the responsibility, audience, cadence, expected artifact, and decisions that must come back to you.
  4. Write Custom Rules. Require sources, block unsupported outreach, and specify when the dot must ask first or hand work back.
  5. Start with a read-only run. Ask the dot to show the information it can access before it interprets or drafts.
  6. Add a schedule only after review. Once the first result is useful, set the recurring cadence and define the stop condition.
  7. Follow the work in Activity View. Inspect progress, add context, redirect the task, pause it, or stop it.

Copy this responsibility brief

Review my permitted investor relationship context for follow-up that is due or blocked. For each candidate, show the last substantive interaction, any promise or requested material, the responsible owner, and why follow-up may be appropriate now. Draft a personal message only when the evidence supports it. Do not send anything. Treat silence as unknown, not rejection, and keep connector consent and recipient context visible.

What the dot should bring back

#OutputExpected behavior
1Recipient and relationship ownerBring back proactively
2Last substantive interactionBring back proactively
3Open promise or requested materialKeep visible for review
4Reason to follow up nowKeep visible for review
5Draft status and approval stateKeep visible for review

Worked example

An investor asked for a customer-reference summary after a second meeting. The dot finds the request, the approved source material, and the relationship owner's note. It prepares a concise draft, flags one unsupported metric, and waits for the founder to correct and approve it. This is an illustrative workflow, not a claim of a measured customer result.

Use the underlying Finta method

This page owns the dots working experience. The durable operating method remains in the related Finta Workflow. Use that method for review criteria and failure states, then bring the reviewed context into the dot only through a connection or handoff available to your account.

Controls that make the workflow trustworthy

  • Proactive research is read-only. OpenAI says background research cannot send messages, change plugin content, or control a browser or computer. Any follow-up action goes through the normal rules and checks.
  • Custom Rules set your preferences. You can allow supported actions, require approval, block actions, or require a handoff within OpenAI's built-in safeguards.
  • Auto-review checks consequential actions. A separate system reviews planned actions against instructions, Custom Rules, and safety requirements.
  • Activity View keeps the work visible. You can follow, correct, redirect, pause, or stop ongoing work.
  • Dots can still make mistakes. Reopen the source and review consequential work before it affects a relationship, record, file, or account.

Workflow boundary: A dot does not receive a standalone email address at launch. Sending or sharing requires appropriately scoped authorization, and approving one message does not create permanent permission.

Availability and limits

As of 2026-09-29, dots are rolling out to ChatGPT Pro and Business Premium users in eligible markets. Enterprise, Edu, and Healthcare workspaces can access a beta when an admin enables it, and it is off by default. Access, plugins, plan limits, regions, and interfaces can change. OpenAI says the first dot is included with eligible Pro and Business Premium plans, but launch-period usage terms should not be treated as permanent pricing.

  • Finta is not a proprietary investor, LP, company, or property database.
  • A relationship path, reply gap, or engagement signal does not establish interest, consent, or permission to contact someone.
  • Connected data can be incomplete or stale. Require sources and observation dates.
  • Do not paste passwords, access tokens, unrestricted exports, or confidential material outside the approved task boundary.
  • Plugin access varies by plan, region, workspace policy, and the permissions granted to the selected account.

Start with one responsibility

Create your dot in ChatGPT, choose one recurring job, and run the responsibility brief with the smallest useful set of permitted context. If you use a reviewed handoff, start with Finta Networks, Finta Documents, or an approved Finta Share Page.

Sources and editorial note

Research updated 2026-09-29. Written and reviewed by the Finta Editorial Team. OpenAI owns the dots name and product. Finta is not claiming sponsorship, endorsement, or a native dots integration. Verify the availability, connections, and controls presented to your own account before relying on this workflow.