Use Case 01

Call Notes Ingestion — AI meeting notes → client record of truth

Every call lands in the client record within minutes — decisions, owners, deadlines, no re-reading transcripts.

On-trigger
01The Pain

What was getting in the way.

Every client call generated an AI notes doc that lived and died in someone's Drive. Decisions, owed items, and deadlines from calls never made it into the client's standing record, so the next person touching the account worked from memory or re-read a 100KB transcript. Duplicate ingestion and missed follow-ups were routine.

Context

Used across the marketing team’s active client roster (local service businesses: trades, health & wellness, professional services).

02The Workflow

How the work runs.

  1. 01

    Trigger

    a team member drops a meeting-notes doc link in chat ("ingest our last call").

  2. 02

    Agent checks the doc ID

    Agent checks the doc ID against existing records — already-ingested calls are detected and skipped (no duplicates).

  3. 03

    Fetches the doc through authorized

    Fetches the doc through authorized internal access (team docs sit behind a login wall; the agent uses its own service identity).

  4. 04

    Reads the structured notes (summary

    Reads the structured notes (summary, decisions, next steps) rather than the raw transcript.

  5. 05

    Files the transcript, updates the

    Files the transcript, updates the client project's canonical status record with a dated call section (outcomes, decisions, checkbox next-steps split by owner), and cross-links the client memory file.

  6. 06

    Outcome

    replies with headline outcomes and flags any owed item whose deadline has already passed.

03In the Environment

Evidence from the workflow.

Slack exchange where a founder asks the agent for a kickoff-call rundown and receives a structured summary (names and account details anonymized)
04Connected Systems

Each system has a role.

  • Intake

    AI meeting notes (docs)

  • Record of truth

    Client project records

  • Intake / signal

    Team chat

05Capability Level

Why this is Copilot.

Helps a person work faster. You ask, it answers. All actions belong to a human.

Read-and-file only; the agent never messages clients from call content. Canonical record edits are additive (new dated sections), never destructive.

Effects / Outcomes

Call outcomes are queryable in the client record instead of buried in transcripts; anyone picking up the account sees decisions and owed items at a glance.

Overdue commitments surface at ingest time — the agent flags items whose deadline already passed.

Duplicate ingestion eliminated by design (doc-ID dedupe check before any work).

← All use cases

Find where a workflow like this fits.

Start with the systems, work, constraints, and authority already present in your operation.