Support loop

Send the site, the action and what happened. Keep secrets out of support.

Support is triaged through a governed Gmail loop: messages can be labeled, summarized and drafted for review, but beta replies and product actions stay human-approved.

Email singularityseo@gmail.com

What to include

Site context

Site URL
Customer/site ID if visible
Approximate time of the issue

Action context

The exact ChatGPT prompt or action
Whether it involved setup, reports, proposal, apply, rollback, Search Console or rankings

Visual context

Screenshot of the WordPress dashboard if the issue is visual
Any clear error message shown by ChatGPT or WordPress

Do not send

Support does not need WordPress passwords, bridge credentials, OAuth tokens, Render keys, SerpApi keys, Google OAuth secrets or payment data.

A safe support message: Site: https://example.com/ Customer/site ID: visible-site-id Action: I asked ChatGPT to generate a baseline report. Issue: The report did not load. Time: Around 2:15 PM Pacific. Screenshot: attached.

Priority levels

P0 Security

Wrong customer data visible, secrets exposed or public SEO changed without approval.

P1 Connection

Controller unavailable, ChatGPT cannot authenticate or WordPress cannot verify hosted connection.

P2 Workflow

Setup, proposal, reporting, Search Console or rollback workflow is blocked.

Support boundaries

The support loop can draft replies and prepare escalation packets, but it does not apply SEO changes, run paid rank refreshes, roll back changes, delete account data or send customer replies without approval during beta.