Beta

Use Google Drive with an AI Browser for Support Triage

Run support triage in Strawberry using Google Drive as one of the inputs. Specific surfaces, example prompt, real output, and tradeoffs vs alternatives.

If you use Google Drive and you regularly need to triage and respond to support, the bottleneck is usually the same: Google Drive holds part of the context, but support triage also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the Google Drive context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles support triage when Google Drive is one of the inputs. It names the Google Drive surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a support engineer, founder doing support, CS lead is trying to do

The goal of support triage is to categorise inbound tickets, surface the urgent ones, and draft accurate replies grounded in product source-of-truth. The success metric is concrete: first-response time under 2 hours, accurate-categorisation rate above 95%, draft-edits-before-send under 20%. That definition matters because it shapes what Google Drive needs to contribute to the workflow.

What signals support triage actually needs

For each signal below, here is whether Google Drive can contribute directly or whether Strawberry has to find it via the browser:

  • Ticket category (billing, bug, feature request, account, security) - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Sentiment (positive, neutral, frustrated, churn-risk) - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Product state (subscription tier, recent activity, feature flag) - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • History (has this user reported the same before) - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • GitHub/Linear status if it's a bug - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Team-mate replies already in the thread - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Google Drive

Strawberry can find files by query, open Docs/Sheets/Slides in-context, and read content for follow-up actions.

Google Drive surfaces Strawberry uses for this workflow: folders, shared drives, permissions, doc/sheet/slide files, search.

How Strawberry runs support triage with Google Drive

  1. Strawberry opens the Google Drive folders that contains the relevant context.
  2. The companion pulls related context from Google Drive (shared drives, history, attached files) where it exists.
  3. For the parts Google Drive does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
  4. Strawberry synthesises the output in the shape this workflow needs: A draft reply per ticket, plus a category label and priority - human reviews before send.
  5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Google Drive or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with Google Drive connected. Adjust the specifics to your actual ICP, role, or topic.

Read this Google Drive folders and any linked context.
Then run a full support triage workflow on it. Use the browser to fill any gaps not in Google Drive.
Return the output in the shape we use for support triage: A draft reply per ticket, plus a category label and priority - human reviews before send.
Do not send anything externally. Save the draft to me to review.

What a good support triage output looks like

Here is what a finished output for support triage should look like in practice. The specifics will change for your use case, but the shape should look similar:

  • Ticket #1962 - Marcus Rosenberg (marcus@clubstill.com)
  • Category: billing - plan-state mismatch
  • Priority: P1 (paying user, $118 charge vs Intern credits)
  • Verified: Stripe shows Intern, charge log shows $118 Part-Time amount, credits granted at Intern rate
  • Draft reply: confirm Intern is active, apologise for the rate mismatch, grant 22k credit balance to match Part-Time tier for current cycle, no refund promised

Why Google Drive for this, and where to use a different tool

Google Drive is strong for this workflow because Strawberry can find files by query, open Docs/Sheets/Slides in-context, and read content for follow-up actions.

Where Google Drive falls short PDFs without text layer need OCR; binary files (.psd, .zip, .ai) can't be read directly.

Consider also a structured CRM or Sheet for tracking actions.

Common mistakes when running support triage

  • Auto-replying with 'we'll look into it' without doing the work
  • Ignoring teammate replies already in the thread
  • Guessing about product behaviour instead of checking GitHub or source code
  • Automated security-report replies (always a major mistake - escalate to a human only)

Connecting Google Drive to Strawberry

Drive scope is included when you connect Google Workspace. Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.

How Google Drive + Strawberry runs support triage

1 Google Drive

Read

Open the relevant Google Drive folders; pull related context.

2 Browser

Augment

Use the browser, LinkedIn, news, and other connected apps for signals outside the CRM/tool.

3 Output

Compose

Synthesise into the support triage shape: A draft reply per ticket, plus a category label and priority - human reviews before send.

4 Human

Approve

Human reviews before any external action; approved output is saved back.

FAQ - Google Drive + AI browser for support triage

Can Strawberry do support triage entirely inside Google Drive?

No, and that is the point. support triage needs signals Google Drive does not store - public web, LinkedIn, news, other apps. Strawberry combines Google Drive with the browser, which is where the real value comes from.

Does Google Drive need to be the primary CRM or system of record?

Not necessarily. Google Drive can be one input among several. Strawberry can read it as context even if your primary system of record is somewhere else.

What permissions do I need on Google Drive?

Read access to the surfaces you want Strawberry to use (folders, shared drives, permissions). Write permissions are only needed if you want Strawberry to update Google Drive after a human approves the change. Drive scope is included when you connect Google Workspace.

What is the realistic success metric for support triage?

first-response time under 2 hours, accurate-categorisation rate above 95%, draft-edits-before-send under 20% - that is the target Strawberry helps you hit, not the only thing it measures.

What is the biggest mistake to avoid?

Auto-replying with 'we'll look into it' without doing the work.

Run support triage in 10 minutes with Strawberry and Google Drive

  1. Open Google Drive

    Connect Google Drive so Strawberry can read folders, shared drives, permissions, doc/sheet/slide files, search and combine them with the rest of the brief. Pin the specific records or views you want to start from so the agent does not drift.

  2. Tell Strawberry the brief

    Drop the prompt below. Replace the placeholder with the actual support engineer, founder doing support, CS lead target - one name, one URL, or one Google Drive reference is enough. Keep the goal explicit: categorise inbound tickets, surface the urgent ones, and draft accurate replies grounded in product source-of-truth

  3. Let it gather signals

    Strawberry pulls ticket category (billing, bug, feature request, account, security) and sentiment (positive, neutral, frustrated, churn-risk), then layers public web sources in parallel. You should see citations next to each fact - that is the audit trail. Watch the Google Drive side: PDFs without text layer need OCR; binary files (.psd, .zip, .ai) can't be read directly

  4. Review before write-back

    Output lands in the shape you asked for: A draft reply per ticket, plus a category label and priority - human reviews before send. Read it once. Fix anything off. The success metric is first-response time under 2 hours, accurate-categorisation rate above 95%, draft-edits-before-send under 20% - if the draft does not hit that bar, send it back with a one-line correction.

  5. Save it as a routine

    If you will triage and respond to support this again next week, click Save as routine. Pick a cadence (daily, weekly, on-trigger). Strawberry re-runs the whole flow on schedule and pings you when the new output is ready.

Paste-ready prompt for support triage with Google Drive

You are helping me triage and respond to support support triage. Use Google Drive as one input and the public web for the rest.

Target: [paste one support engineer, founder doing support, CS lead target here - a Google Drive reference, a name + company, or a URL]

Goal: categorise inbound tickets, surface the urgent ones, and draft accurate replies grounded in product source-of-truth

Signals to gather:
- ticket category (billing, bug, feature request, account, security)
- sentiment (positive, neutral, frustrated, churn-risk)
- product state (subscription tier, recent activity, feature flag)
- history (has this user reported the same before)
- GitHub/Linear status if it's a bug
- team-mate replies already in the thread

Output shape: A draft reply per ticket, plus a category label and priority - human reviews before send

Rules:
- Cite every fact with a link or a Google Drive reference. If you cannot find a signal, say so explicitly rather than guessing.
- Do not invent specifics. Use real, dated signals from the last 90 days where possible.
- If a fact would change the outcome and is missing, pause and ask me before writing the final output.

When the output is ready, surface it in this chat. Do not write back to Google Drive or send anything externally until I approve.

Paste this into Strawberry's chat field. Replace the target placeholder before running.

When Google Drive + Strawberry is the right combo for support triage

Google Drive is the file system where team documents, decks, and reports live. Strawberry can find files by query, open Docs/Sheets/Slides in-context, and read content for follow-up actions. For support triage specifically, that means the agent already has folders, shared drives, permissions, doc/sheet/slide files, search as starting context - you do not need to brief it from scratch.

When it is NOT a fit

  • You need a single number, not a synthesised brief. A SQL query against your warehouse is faster.
  • The decision is happening in the next 60 seconds. The agent is fast but it is not instant; for hard real-time use, do it manually.
  • The Google Drive data you would feed in is stale or wrong. Garbage in, confident garbage out.

Three mistakes to avoid

  1. auto-replying with 'we'll look into it' without doing the work
  2. ignoring teammate replies already in the thread
  3. guessing about product behaviour instead of checking GitHub or source code

Honest tradeoff

PDFs without text layer need OCR; binary files (.psd, .zip, .ai) can't be read directly. If you are running this at scale (10+ briefs per day), batch the inputs and let Strawberry process them as a routine instead of one-by-one prompts - cheaper per brief and the output stays consistent.

What a real output looks like

Ticket #1962 - Marcus Rosenberg (marcus@clubstill.com),Category: billing - plan-state mismatch,Priority: P1 (paying user, $118 charge vs Intern credits),Verified: Stripe shows Intern, charge log shows $118 Part-Time amount, credits granted at Intern rate,Draft reply: confirm Intern is active, apologise for the rate mismatch, grant 22k credit balance to match Part-Time tier for current cycle, no refund promised
Download