Customer Support

Contact GovScout Pro

Use this page for customer support, billing questions, subscription help, partnership questions, or help understanding how Marcus supports your federal contracting workflow.

Email support stevenh@govscout.pro
Best information to include Your company name, account email, plan, what you were trying to do, and any error message you saw.

GovScout Pro uses this information only for support, consult follow-up, and product/revenue review. A request does not guarantee an award, eligibility, compliance result, or government affiliation.

Login help

Include the account email you used, the plan you selected, and whether the issue happened before or after checkout.

Billing help

Ask for invoice, receipt, cancellation, or payment method help. Stripe handles payment details securely.

Marcus help

Tell us what Marcus was supposed to do, what happened, and which workspace you were using.

For account access

Send the email on the account, your expected plan, the browser you used, and the exact screen where you got stuck. Do not send passwords or session tokens.

For contract workflow help

Share the non-sensitive opportunity title, agency, due date, NAICS or PSC, and what you wanted Marcus or the workspace to help you decide.

For product feedback

Explain the job you were trying to complete, what felt confusing, and whether the issue slowed down search, document review, alerts, billing, or pipeline work.

Before contacting support

Try the FAQ, the Start Here guide, or the free tools hub if you need a quick explanation.

Before asking about pricing

Review pricing and decide whether you are still learning, actively searching, or managing serious pursuit work.

Before asking about Marcus

Read How to Use Marcus and gather the business and opportunity facts that make his answers more useful.

Do not send secrets

Never send passwords, API keys, session tokens, Social Security numbers, payment card numbers, or private customer data through the contact form. Support can help without those details.

For faster triage

Use one message per issue. A login issue, billing question, Marcus answer concern, and alert-delivery question should be separated so each can be routed and verified cleanly.

For launch feedback

If you are reviewing GovScout before a marketing handoff, include the page URL, device size, browser, and whether the issue affects trust, conversion, SEO, or paid-user workflow.

What happens next

Support will first identify whether the issue is account access, billing, Marcus behavior, public website content, alerts, or release readiness. Engineering issues should be turned into tracked work instead of handled only in email.

Billing and cancellation

Payment method, invoice, and cancellation questions should route through Stripe wherever possible. GovScout support should not ask for card numbers or private payment credentials.

Federal contracting questions

If your question is about a solicitation, include the public link or non-sensitive summary. Marcus and support work best when the agency, deadline, set-aside, NAICS, scope, and evaluation clues are clear.