Useful assistant recipes

How to use these recipes#

Replace the bracketed placeholders with your company, client, people, dates, and task details before using a prompt with your assistant. Complete the first read-only task before using a recipe that changes records.

Creation, editing, and reporting depend on the actions available in your current connection and your access. Have the assistant verify availability first. If an action is unavailable, it should return a proposal for you to apply in the workspace, not claim the change succeeded.

For every proposed write, approve the exact records and values first, then verify the saved result. These recipes exclude finance, billing, accounting, general deletion, owner administration, and provider changes. They do not authorize publishing, sharing, or sending.

1. Plan the week from open tasks#

Goal: build a realistic priority list from existing operational tasks. Access: viewing access to Tasks and the relevant clients. Inputs: your company, review date, client selection, and the teammate whose work you want to review.

• Expected output: a dated priority list with references and a clear separation between facts and suggested priorities.
• Verify: compare several records in Tasks, including an overdue item and one without a due date. Check that the review is complete or its limits are stated.
• Approval: the prompt permits reading only. Approve any later reassignment, due-date change, or new task separately.

In [Company name], review open operational tasks for [Team member name] for the week starting [Week start date]. Confirm company and access, resolve the teammate unambiguously, and exclude billing work. Group overdue tasks, tasks due this week, and tasks without due dates. Include the related client, owner, due date, status, and record reference. Suggest three priorities with reasons. Read only; do not change tasks or notify anyone. Identify unavailable or incomplete information.

2. Prepare a client meeting brief#

Goal: arrive at a client meeting with current context. Access: viewing access to Clients, operational delivery records, activities, and Tasks as needed. Inputs: the client, meeting date, and review period.

• Expected output: a concise meeting brief with source records, open questions, and missing context called out.
• Verify: open the client’s activity and tasks and confirm the latest entries and unresolved blockers.
• Approval: review the brief before using it with the client. Any record change or external message needs a separate instruction and approval.

For [Client name] in [Company name], prepare a brief for our meeting on [Meeting date]. Confirm the company and client. Read the available operational client context, open tasks, and manual activity from [Review start date] onward. Exclude finance, billing, and accounting. Summarize completed work, open blockers, decisions we need, and questions to ask. Reference the records behind each factual claim. Do not infer missing work was completed. Read only; do not edit, share, or send the brief.

3. Create a reviewed follow-up task#

Goal: turn an agreed next step into one operational task. Access: viewing and editing access to Tasks and the related client or sales work; task creation must be available. Inputs: exact client, task, active teammate, due date, and details.

• Expected output: a proposal first, then a verified saved task reference only after approval.
• Verify: open Tasks and confirm one matching task, its client, assignee, due date, details, and status.
• Approval: approve the proposed task explicitly. If the client or teammate is ambiguous, resolve that choice before creation.

In [Company name], propose one task for [Client name]: [Review October creative draft], assigned to [Team member name], due [Due date], normal priority. Details: [Compare the draft with the approved brief and list changes for internal review]. Verify that task creation is available, resolve the client and teammate, and check for an existing equivalent task. Show the exact proposed record and wait for my approval. After approval, create it once and read it back. If the result is uncertain, check for the existing result before retrying. Do not create billing work, send messages, or change other records.

4. Update a completed task#

Goal: reflect a completed deliverable in an existing operational task. Access: viewing and editing access to the task’s area; the specific edit must be available. Inputs: exact task and evidence that the work is complete.

• Expected output: the current task and a one-field proposal, followed by a saved status after approval.
• Verify: reopen the exact task and check the status while confirming unrelated fields stayed correct.
• Approval: the assistant must not decide that work is complete from the task title. You supply completion evidence and approve the change.

In [Company name], find the operational task [Review October creative draft] for [Client name]. I have confirmed that [the internal review is complete and feedback is recorded]. Read its current state and propose changing only its status to completed. Show the record and proposed change, then wait for approval. After approval, reread if needed, apply the supported change, and read back the saved status. If someone changed the task meanwhile, show the new state before proceeding. Do not change its owner, due date, related records, or provider data.

5. Record an internal meeting note#

Goal: preserve a reviewed conversation summary on the right record. Access: viewing and editing access to operational activities, with manual note creation available. Inputs: client or opportunity, meeting time, and a factual summary.

• Expected output: a clearly attributed manual note with the reviewed wording and time.
• Verify: inspect the client or opportunity activity and confirm the exact note and association.
• Approval: approve the full wording before saving. Do not use this recipe to rewrite an immutable system event or decision record.

In [Company name], propose a manual activity note for [Client name] about our meeting on [Meeting date, time, and time zone]. Subject: [Creative review]. Body: [The client requested two headline options. The assigned teammate will prepare them for internal review by the agreed deadline. No scope or budget change was agreed.] Confirm the company, record, and that manual note creation is available. Show the full note and wait for approval. After approval, save it once and read it back. Label it as a manual team note; do not invent a calendar event, imported message, legal acceptance, or provider confirmation.

6. Assign a local conversation for follow-up#

Goal: give an existing local conversation record a clear owner. Access: viewing and editing access to Inbox; the relevant local assignment edit must be available. Inputs: a uniquely identified existing conversation, client, and active teammate.

• Expected output: a proposal and, after approval, a verified local owner assignment.
• Verify: open the corresponding conversation and confirm its owner. No sent-message claim should appear.
• Approval: approve the assignment only. Sending a follow-up or creating a new triage record would require its own reviewed request.

In [Company name], find the existing local conversation for [Client name] with subject [October creative questions]. Confirm it is the intended record and that local assignment editing is available. Propose assigning it to [Team member name], preserving its other details. Show the current and proposed assignment and wait for approval. After approval, save and read back the assignment. Do not send or reply, create a provider conversation, change read or delivery status, or modify consent. If no matching local record exists, stop and explain that result.

7. Prepare a performance report draft#

Goal: prepare a private draft from reviewed advertising results. Access: the report preparation and source viewing access required by the current connection; verify the reporting action is available. Inputs: client, account, exact date range, metrics, and reporting context.

• Expected output: a source review and proposed report, then either a verified private draft after approval or an unsaved outline.
• Verify: compare the account and totals with Ads manager and open the saved version in Reports. Check notes and missing metrics before delivery.
• Approval: approve saving the draft separately from sharing. Check that the report uses the intended account and includes the source data you need.

For [Client name] in [Company name], check whether report drafting from the linked advertising account is available. Use [Advertising account name] for [Report start date] through [Report end date]. First show the account, client link, dates, available metrics, time zone, and any missing data. Propose the report contents and wait for approval before saving anything. After approval, create only a private draft if supported and read back its title, client, period, and version. Separate measured results from interpretation. Do not share, publish, email, or change campaigns. If drafting is unavailable, provide a clearly labeled outline for manual review.

8. Triage a client request#

Goal: turn a client’s request into a clear internal plan without changing what the client submitted. Access: viewing access to eligible portal requests and their linked operational tasks; task editing only if a later change is approved. Inputs: client and request title or date.

• Expected output: the original request summarized accurately, its linked work, and a proposed internal next step.
• Verify: compare the request in the client record with the assistant’s summary. If you approve a task edit, reopen that task and verify the saved fields.
• Approval: reading is allowed by the prompt; every edit needs approval after the proposal. Client-authored submissions and decisions stay unchanged.

In [Company name], review the non-billing portal request [Update the autumn landing page] from [Client name], submitted around [Request date]. Confirm the company and request, read the client’s original wording and any linked operational task, and suggest the next internal action. Keep the client’s submission unchanged. If an existing task needs an update, verify editing is available and present exact proposed values for approval. Do not create an approval decision, publish feedback, share, send, or claim the client accepted anything.

9. Prepare a morning brief#

Goal: Review the day without changing records. Access: viewing access to operational tasks and sales; calendar results require a separately authorized calendar. Inputs: company, review date, time zone, and date range.

• Expected output: A dated brief with priorities, meetings, lead follow-ups, source references, and explicit coverage limits.
• Verify: Compare Tasks, Sales pipeline, and the selected calendars. Missing calendar access must be stated.
• Approval: Reading only. A recurring brief needs separate scheduling in your assistant; this prompt does not schedule future runs.

For [Company name], prepare my morning brief for [Review date and time zone]. Confirm the company. Summarize open non-finance tasks, upcoming meetings for [today through tomorrow], and sales leads needing attention. Name the sources and record references. Check all available result pages or state the limit. Separate missing access from an empty result. Read only: do not change records, send messages, or create a schedule.

10. Sales preparation for your next call#

Goal: Understand a prospect before the call. Access: viewing access to Sales, relevant activities, and Quotes. Inputs: company and prospect, with a contact name if needed.

• Expected output: A prospect brief with current stage, conversation history, outstanding questions, and proposed next steps.
• Verify: Open the same opportunity and its quotes. Confirm recipient, stage, and the most recent activity.
• Approval: Reading only; resolve ambiguous prospects before using the brief.

In [Company name], find [Client name] and summarize its current stage, notes, accessible quote history, and next steps for my call. If multiple records match, show enough context for me to choose before continuing. Distinguish saved facts from suggestions and include record references. State any unavailable history. Read only; do not change the stage, create a quote, contact the prospect, or mark the opportunity won.

11. Capture a new lead — verify availability first#

Goal: Prepare one new lead. Access: sales viewing and editing with lead creation available in the current connection. Inputs: prospect company, contact, email, notes, and desired initial stage. Ask the assistant to check whether lead creation is available before preparing the new record.

• Expected output: An exact proposal; after approval and only when supported, one saved lead with a record reference. Otherwise, an explicitly unsaved draft.
• Verify: Open Sales pipeline and check company, contact, stage, and notes. Confirm there is one lead and no client conversion.
• Approval: Approve the exact new lead before creation. Do not use real customer details for a capability test.

In [Company name], check whether creating a sales lead is available. Search for an existing opportunity for [Client name] and contact [Contact name] at [Customer email]. If one exists or multiple records match, stop and show me before adding anything. Otherwise propose a new lead with notes [Interested in a discovery call about paid search]. Show the exact fields and wait for my approval. After approval, create once and read back the saved lead. If the result is uncertain, inspect existing records before retrying. Do not mark it Won, convert it to a client, send a message, or change provider accounts. If creation is unavailable, give me an unsaved draft to enter manually.

12. Review client onboarding#

Goal: Identify what is waiting on the client. Access: viewing access to the client, onboarding items, and relevant operational tasks. Inputs: company and client.

• Expected output: A checklist in the conversation with blockers, open questions, and suggested next actions.
• Verify: Compare the client’s Delivery and Activity sections with the checklist. A chat draft should not appear as a newly saved task.
• Approval: Drafting text here is read-only. Saving work or sending a follow-up requires a separate reviewed instruction.

For [Client name] in [Company name], summarize onboarding items that are blocked or waiting on the client. Reference the source records and distinguish confirmed blockers from missing information. Draft a follow-up checklist here with proposed owners and questions. Read only: do not create tasks, edit onboarding, send the checklist, or record an approval decision.

13. Prepare a reply for review#

Goal: Get context before responding. Access: viewing access to relevant conversations and an authorized mailbox or messaging connection. Inputs: client and conversation subject/date.

• Expected output: A summary and an unsent reply draft in the conversation.
• Verify: Compare the original thread and latest message with the draft. Confirm it addresses the actual request and has not been sent.
• Approval: Check whether sending is available in your connection, then review and approve any later sending separately.

In [Company name], find the connected conversations for [Client name] about [October creative questions]. Resolve the intended client and conversation before reading. Summarize the latest accessible messages and draft a reply here for review. Name the sources and identify missing messages or incomplete coverage. Do not send, change read status, assign ownership, create a new conversation, or alter consent.