# Neotask Support Overview ## Start At The Product Screen Open the screen where the problem appears before contacting support. Gateway, Apps, Usage, and Approvals each expose the status and history support needs. ![Troubleshoot settings with the system check and repair controls](https://neotask-marketing-assets-417007889150.s3.us-east-1.amazonaws.com/docs/product/2026-08-13-r4/troubleshoot-system-check-1280.webp) This guide explains what the support phone system is designed to help with and how support access works. --- ## What Support Covers Neotask support is built to help with: - desktop app setup - app startup problems - MCP app connections - OAuth setup and reconnects - API key and manual credential setup - billing and subscription questions - login and account-access issues - teams, channels, automation, and enterprise admin questions - live troubleshooting based on recent failures, sessions, runtime errors, and workflow context The support system is not a sales line. It is optimized for troubleshooting and getting members unblocked. --- ## Member Support vs Guest Support The support number has two support modes: ### Guest Support Guest support is for callers who are not yet recognized as members. Guest support can help with: - how to sign up - where to log in - public setup guidance - payment or sign-up friction before the account is active - where to find official docs ### Member Support Member support is for recognized callers whose phone number already matches a saved support route or employee record. Member support can help with: - tenant-specific troubleshooting - deeper app and OAuth setup - billing and account context - workspace, automation, and company-admin questions - recent failures, logs, session history, and runtime context - escalations and support follow-up That means the support line can often investigate the issue directly instead of only telling the user what the docs say. --- ## Main Support Categories For app authentication, open **Apps** and check whether the requested service is connected before troubleshooting its tools. ![Connected and available apps](https://neotask-marketing-assets-417007889150.s3.us-east-1.amazonaws.com/landing/agents/2026-08-12-r1/apps-main-1280.webp) Recognized member callers are routed into these main categories: 1. **Setup and Troubleshooting** 2. **MCP and OAuth Integrations** 3. **Billing, Login, and Account Access** 4. **Workspace, Teams, Automation, and Enterprise Admin** Guest callers stay in the limited guest-support lane unless a saved member route is recognized. --- ## Recommended Routing Sequence When support answers a call, the fastest sequence is: 1. Decide whether the caller should stay in general support or move into recognized member support. 2. Identify the primary issue class: setup, MCP/OAuth, billing/access, or workspace/automation. 3. Keep the caller in one lane unless the problem clearly changes categories. 4. If the issue needs follow-up, create a support case before the call ends. Use these routing cues: - "I cannot finish setup" usually starts in setup support. - "OAuth", "callback URL", "client ID", "client secret", or a provider name usually routes to MCP auth support. - "I paid but cannot access it" usually starts in billing/account support. - "Messages are going to the wrong place" or "automation is not firing" usually starts in workspace and automation support. --- ## What To Have Ready Before You Call Support is fastest when you have: - the phone number saved on your account or employee profile - the name of the app or provider you are trying to connect - the exact status shown in the Apps tab - the error text, if there is one - the callback URL or environment variables you already configured For OAuth issues, support may ask: - which provider you are connecting - whether it uses managed OAuth, manual OAuth, API keys, or manual credentials - whether the app shows `pending`, `connected`, `error`, or another state --- ## Best Support Entry Points Use the support line when: - you are blocked from setup - reconnecting an app did not fix the problem - you need step-by-step OAuth setup guidance - you need help understanding auth status or reconnect paths - you want the system to inspect what failed recently and explain the likely cause Use the docs first when: - you only need the public setup steps - you are browsing supported apps - you need the callback URL or environment-variable naming pattern --- ## Related Docs - [Neotask Support Call Agent](./neotask-support-call-agent.md) - [Neotask Authenticated Support Access](./neotask-support-authenticated-account-support.md) - [Neotask Support Agent Capability Reference](./neotask-support-agent-capability-reference.md) - [Support App Setup And Troubleshooting](./support-app-setup.md) - [Support MCP Auth And OAuth](./support-mcp-auth.md) - [Support Billing, Login, And Account Access](./support-account-and-billing.md) - [Support Workspaces, Teams, And Automation](./support-workspaces-and-automation.md)