Skip to main content
Customer Follow-ups is a private workspace-owner automation pack for new native Form enquiries. Contact Button keeps the Contact, enquiry message, thread ownership, and follow-up state. Gmail holds an optional unsent acknowledgement, and Google Sheets can receive an optional copy. Gemini and Google Workspace are separate connections. A verified Gemini API model supplies text generation; Google authorization grants access to specific services. Connecting a Gemini model or public Agent grants no mailbox access.

Set up the pack

  1. As the workspace owner, open the Form’s Notifications → Automations. Enable response storage in the Form settings so the enquiry has a native Contact and Inbox timeline.
  2. Find Customer Follow-ups and choose the follow-up deadline, from 1 to 720 hours after submission. The default is 24 hours. The pack uses the existing Contact follow-up service and creates a one-time reminder owned by you.
  3. Map the customer email and optional name fields.
  4. To prepare acknowledgements, connect your own Google account with Gmail draft permission, select a verified, billed Gemini API connection, and explicitly approve sending this Form’s plain-text answers to that model.
  5. Optionally grant Sheets access and select the spreadsheet ID and tab. The Sheet is an output; it does not replace the Contact timeline.
  6. Enable and save the pack. Submit a synthetic enquiry first, review the native receipt and Google action result, then open Gmail to review and send the draft yourself.
The pack requires GOOGLE_WORKSPACE_ENABLED, native response storage, and Contact follow-ups. Existing workspaces are opted out. Enabling the pack does not grant Google permissions or change existing notification, webhook, Google Contact, or email-campaign settings. If you only want native follow-ups, turn off the Gmail draft and Sheets options. This mode does not require Google authorization or a Gemini connection.

What happens on a new enquiry

The existing Form submission flow creates the Contact, response, and Inbox message. The pack links a follow-up to that same thread and message. It does not create a second customer database or infer a new owner. If someone has assigned the thread to another operator, the receipt asks for an ownership review and skips the pack’s Google outputs rather than taking over their thread. When you enable drafts, Gemini receives only the approved Form’s bounded plain-text answers. Uploaded files, request metadata, credentials, mailbox history, meeting content, and Google-imported knowledge are excluded. The model proposes a short acknowledgement; Laravel chooses the mapped recipient and subject and creates the draft through the fixed Gmail drafts endpoint. The model cannot choose a tool, URL, recipient, or send operation. Google’s gmail.compose permission permits sending as well as draft management. This pack enforces draft-only behavior in the backend: its Gmail action only creates a draft. It provides no customer-send or draft-update operation. Existing Google OAuth verification requirements still apply to the scopes your application requests.

Receipts and edits

Native Follow-up Receipts records whether a reminder was created or existing thread ownership needs review. Recent Actions records Gmail and Sheets outcomes independently. A completed Gmail action means Google confirmed draft creation; it does not mean a customer was emailed. One native response creates at most one pack follow-up. External actions reuse the existing per-submission/action delivery ledger and queue locks. Reprocessing a completed action does not recreate or update its draft, preserving your edits in Gmail. A stable message ID helps manual reconciliation when an external result is uncertain. Ambiguous external failures stop in Needs review. Check Google for an existing result before any manual recovery; the pack never blindly repeats an uncertain write. A lock-contention retry is safe because the external action has not started. Saving a changed or disabled pack cancels its queued actions and replaces the server-held activation revision. Running jobs recheck owner identity, the connected Google account, granted capability, current configuration, and the original native response. An in-flight request may finish after settings change. Existing drafts and reminders are retained for you to manage. Copied Forms require fresh owner activation. An old settings payload cannot restore a revoked activation. Owner transfer, disabled response storage, revoked capabilities, or deleted source responses prevent further pack execution as applicable. Pack settings are omitted from Form serialization and the general Forms API.

Private data boundary

This first release handles new native Form enquiries only. It does not read selected Gmail threads, import meetings, inspect Calendar contents, or process Google-derived Knowledge through a model or MCP. Those capabilities require a separately approved data path. The pack is independent of public website Agents, public MCP questions, and visitor action proposals. There is no public MCP tool to enable it or run it. Results follow the workspace’s normal Contact, Inbox, and task visibility rules; only the workspace owner can manage the pack. AI monitoring reuses the existing form-delivery trace and opaque submission ID. Prompt and model-output capture remain disabled.