From three sources to one client brief
For agency and consultancy owners, account managers, and lean delivery teams, the weekly client check-in often starts in three places: Gmail for the latest conversation, a Sheets tracker for delivery status, and Drive for the agreement, brief, or meeting notes. Geniusly can read authorized context from these supported apps and prepare the brief in your Slack conversation.
This is an account review workflow. The output is a brief for your team or next client call. If you only need the wording for an email reply, use the client follow-up workflow.
| Source | What to name | What it contributes |
|---|---|---|
| Gmail | The client, relevant thread, and reporting dates. | New requests, approvals, commitments, and unanswered questions. |
| Google Sheets | The exact tracker, tab, range, and status definitions. | Recorded owners, due dates, progress, and blockers. |
| Google Drive | The current agreement, project brief, and meeting notes. | Agreed scope, recorded decisions, and context behind the work. |
Give Geniusly this task in Slack
Prepare the Acme weekly client brief for October 8–15, 2026. Read the Acme launch email conversation in Gmail, rows 2–25 of the Launch tab in the Acme Delivery Tracker in Google Sheets, and the current launch brief and October 9 meeting notes in Drive.
Return recent developments, outstanding commitments, recorded owners and dates, disagreements between sources, and questions for our next call. Link each factual item to its source. Mark missing owners or dates as unknown. Return the brief in this Slack conversation and prepare a Markdown file.
Use your own client, reporting period, and accessible documents. This example is an instruction, not a completed customer task.
One client and one reporting window keep the task focused. Name the intended files rather than asking the agent to search every account. If a source is unavailable or its format cannot be read, ask Geniusly to identify the gap and continue only with accessible material. Provide a supported text or CSV export when needed.
What the finished brief can look like
Reporting period: October 8–15, 2026. All names, sources, and facts below are sample content. Source labels show how evidence would be organized; they are not live document links.
Recent developments
- The client approved homepage copy in the October 14 email. The tracker still labels copy approval as pending. [G1, S1]
- The launch brief includes a homepage refresh and onboarding email copy. [D1]
Outstanding commitments
- Final product images: requested in the email thread; no delivery date is recorded. The tracker names Alex as the client owner. [G1, S1]
- Delivery handoff: depends on the final images. No internal owner is recorded in the supplied sources. [S1, D2]
Discrepancies to resolve
Copy approval has different statuses in Gmail and the tracker. Confirm the tracker status with its owner; this brief does not update it. [G1, S1]
Questions for the next call
- When can Alex share the final images?
- Who owns the internal delivery handoff?
- Can we confirm a launch date once the remaining inputs are ready?
Source references
- G1: Acme launch Gmail thread, October 14.
- S1: Acme Delivery Tracker, Launch tab, rows 2–25, reviewed October 15.
- D1: Current Acme launch brief in Drive.
- D2: October 9 kickoff meeting notes in Drive.
For your own task, ask for links to the actual messages, rows, and documents. Check important dates and commitments against those sources. Missing evidence belongs in an open question, rather than a confident conclusion.
Start with one client in three steps
- Sign up and add Geniusly to Slack. Choose the workspace where you manage client work. Workspace policy may require an administrator’s approval.
- Connect the three sources in a private DM. Say
Connect my Gmail, then connect the Google Sheets and Drive accounts containing the client’s material. Each app and account is authorized separately. The Gmail connection guide explains the first connection. - Request and review the brief. Specify the client, dates, tracker, and documents. Review the returned brief and file in Slack, check the source references, and ask a follow-up for any gap.
You can reuse the request next week with an updated reporting window. This guide describes an on-request brief. It does not configure a recurring schedule or claim that source records will change.
Use the brief to prepare the conversation
Ask for the brief in the format your team needs: concise bullets in Slack or a Markdown document for the meeting. Keep client-facing wording separate from internal questions, and review it before sharing.
Geniusly’s current connected-app workflow reads authorized material and prepares results. It does not send this brief by Gmail, save a Gmail draft, edit the tracker, update a CRM, or create project tasks. If the information is missing or ambiguous, the useful result is a clearly flagged gap.
Explore the Slack AI assistant, the narrower client follow-up workflow, or RevOps and operations use cases for other jobs using connected context.
Questions & answers
What is a weekly client brief?
A short account review that brings together recent developments, outstanding commitments, recorded owners and dates, source discrepancies, and questions for the next client conversation. It is broader than a follow-up email draft.
Do I need Gmail, Sheets, and Drive connected?
Connect each source you want Geniusly to use. If you only have two sources, request a brief from those and ask it to flag the missing context. Authorizing Gmail does not automatically authorize Sheets or Drive.
What if the email and tracker disagree?
Ask Geniusly to cite both sources, show the discrepancy, and mark the question for review. Do not silently treat one source as authoritative unless your instructions establish that rule.
Will it invent an owner or a due date?
Ask for recorded owners and dates only, with unknown values explicitly marked. Review the result against the sources. If you request suggestions, keep them clearly separate from agreed commitments.
Will it update my tracker or email the client?
No. This workflow produces a brief in Slack and can prepare a file. Gmail sends, saved Gmail drafts, tracker edits, and CRM or project-record updates are not enabled in this release.
Does this run automatically every week?
The workflow shown here runs when you request it. Reuse the task prompt with a new date range. This page does not configure a schedule.
Is the Acme brief a real customer result?
No. It is an illustrative example with sample sources and facts. It explains the output format, not measured customer performance or a live connected-account result.