Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Gmail intake and scoped support tickets. Read a dedicated Gmail inbox and convert reviewed messages into tickets for approved paid company users. Current availability: Implemented; verification required. Before you start. An authorized administrator in the correct company or the TLS owner console, with mandatory verification completed. Use an approved synthetic account for acceptance. Keep credentials, personal data and recovery codes out of recordings. Step 1. Authorize the intended Gmail mailbox. Personal Gmail uses OAuth offline consent. Google Workspace can instead use a service account with domain-wide delegation approved by its administrator. Grant Gmail read access to the dedicated support mailbox. Step 2. Open Connected services > Gmail and Google Workspace intake. Enter all three OAuth fields or the delegated service account email and complete PEM key, plus the exact mailbox. Save protected credentials, verify mailbox identity and enable the connection. Step 3. Run the first complete inbox scan. Subsequent runs use Gmail history checkpoints. When Google reports an expired checkpoint, Connect starts a new inbox pass. Use the recorded page state until that pass completes. Step 4. Review a message header and choose Create scoped support ticket. The sender must match exactly one active approved company user with an active subscription. Unknown, ambiguous or automated messages need review in Gmail. Step 5. A company Workspace connection creates a company helpdesk ticket. TLS platform intake and Managed IT connections create TLS support tickets for the matched company. A message ID and mailbox claim prevent repeat conversion. Step 6. Read the resulting ticket. Body text is imported; attachments remain in the source mailbox and are listed by name only. This action does not grant sign-in access, forward attachments or send an acknowledgment. Step 7. Pause or recycle the connection during offboarding. Reconnection does not invalidate the retained duplicate-prevention evidence. Accept a real approved mailbox and one harmless message before using intake operationally. Now verify the result. Read checkpoints remain scoped to the authorized mailbox. Another company’s sender cannot be accepted by a company-scoped inbox. Disabling the company or user during import prevents a new ticket. If you get stuck. Automatic conversion of every incoming message, reply threading and Gmail attachment import are not enabled. Current conversion is a reviewed action. Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.