>_

SpendSignoff documentation

The always-on operator for your ad accounts. Read and draft from your AI client — approve before anything goes live.

Knowledge base

Getting support

There are three support channels depending on what you need: Discord for community questions, GitHub for bugs and feature requests, and direct email for enterprise and billing issues.

Support channels

  • Discord — the fastest path for how-to questions, setup help, and discussion with other users. The #spendsignoff channel is monitored by the team. Join link is in the app sidebar.
  • GitHub Issues — use this for confirmed bugs, reproducible errors, and feature requests. Include the error message, the AI client and version, the MCP server response if available, and whether the issue is consistent or intermittent.
  • Email — support@spendsignoff.com — for billing questions, account access issues, and anything that involves private account data. Do not post account IDs or token details in Discord or GitHub.
  • Enterprise — Agency-tier accounts and self-hosted deployments can reach the team at enterprise@spendsignoff.com for onboarding help and SLA discussions.

Writing a useful bug report

1

Describe what you expected

One sentence: what were you trying to do and what did you expect to happen? This gives the reader immediate context before the details.

2

Describe what actually happened

Include the exact error message from the AI client, the SpendSignoff app, or the MCP server response. Copy-paste is better than paraphrasing.

3

Include your environment

AI client name and version, operating system, browser if the issue is in the SpendSignoff app, and the plan you are on (Free / Solo / Pro / Agency).

4

State whether it is reproducible

Can you reproduce it consistently with the same steps? Or did it happen once and stop? Intermittent failures take longer to diagnose but are still worth reporting.

Response time expectations

Discord responses typically come within a few hours on weekdays. GitHub issues are triaged weekly, with critical bugs addressed faster. Enterprise email has a 1-business-day response target.

SpendSignoff is an early-stage product. The team is small. If something is not answered immediately, it is not ignored — triage is running.

Never share tokens or credentials in support channels

Support staff will never ask for your OAuth tokens, API keys, or Clerk session credentials. If you see a connection issue, share the error message only — not the token that produced it.

Self-hosted deployments

The MCP connector core is open-source. Self-hosted issues are tracked in the same GitHub repository. Include the version tag or commit hash you deployed, the deployment environment (Cloud Run, Fly.io, bare VM), and the error from the server logs.

Next

Troubleshooting

Connection errors, stale drafts, locked approve controls, and missing data.

    Getting support — SpendSignoff Docs