Welcome to Specteron Support
Search setup guides, workflow help, billing answers, and troubleshooting steps. Use the library for fast self-serve support, open a ticket when your issue needs account context, or join Discord for quick back-and-forth with the community.
Start with the help library for the fastest path to an answer. If your case depends on workspace data, billing details, or a bug that needs investigation, switch to tickets so the team can review it properly.
Search guides, troubleshooting steps, setup walkthroughs, and common operational questions in one place.
Create a tracked request with replies, attachments, and status history when your issue needs investigation.
Use the docs for widget snippets, SDK controls, gateway API, webhooks, signatures, and limits.
Join for quick back-and-forth on setup, best practices, and lightweight feedback before opening a formal support request.
Browse support by area
Choose the path that matches your issue, then move into the article or support channel that fits best.
Getting started
Start here if you are setting up Specteron for the first time or bringing teammates into the workspace.
Knowledge and automation
Use these if you are tuning the source material, answer behavior, routing, and review flow behind the assistant.
Channels and integrations
Use these for inbox setup, communication channels, gateway API, and webhook delivery.
Account, security, and fixes
Use these for workspace governance, billing, and the most common production troubleshooting paths.
Popular support journeys
Use these paths for the tasks that usually matter most during setup, operations, billing, and launch review.
Start here if you are launching Specteron for the first time and want the fastest path to a usable support workflow.
- Create the first agent or workflow.
- Publish the widget on the production domain.
- Connect the right support inbox.
- Invite teammates with the right level of access.
Use this before expanding automation so answers are grounded in clean and approved source material.
- Add files, URLs, notes, and collections.
- Remove outdated or conflicting content.
- Run sample questions before going live.
Use this when the basics are already running and you want cleaner queues, better ownership, and fewer manual steps.
- Refine ticket routing rules.
- Review automated responses carefully.
- Use troubleshooting guides for operational issues.
Use this path when you are reviewing plans, account changes, or support questions that may need a tracked follow-up.
- Check billing and usage guidance first.
- Review workspace security before account changes.
- Open a ticket for account-specific investigation.
- Use Discord for non-sensitive general questions.
Help library
Find setup, automation, integration, billing, security, and troubleshooting guidance for Specteron operations.
Choose a topic
Filter the library by the part of setup, automation, billing, or troubleshooting you are working on.
Open a guide
Use the matching article for practical steps, checks, and launch-ready guidance.
No matching articles
Try a different keyword, switch categories, or open a ticket if your issue needs account-specific review.
Frequently asked questions
Short answers for the questions that usually come up first during setup, operations, and support handoff.
How long does setup usually take?
Most teams can get the first workflow running quickly when they start narrow. The cleanest first rollout usually means one inbox, one workflow, and a review step before expanding automation.
Do we need technical help to get started?
Not for the basic flow in most cases. Technical help becomes more relevant when you want advanced integration patterns or a more customized operational setup.
When should we use tickets instead of the help library?
Use the library for general questions and how-to help. Use tickets when the answer depends on your account, workspace configuration, billing state, or a bug that needs investigation.
What is Discord best for?
Discord is best for fast back-and-forth around onboarding, setup direction, and best practices. It is not a replacement for tickets when the issue needs a tracked support thread.
Can we refine how workflows respond?
Yes. Most teams improve results by tightening source material, clarifying workflow rules, and reviewing uncertain cases before broadening automation.
What must be checked before publishing the widget?
Check the production script, bot key, allowed origin, launcher placement, first reply, and fallback or ticket path from the real domain.
Where should security or API key questions go?
Use the security and API articles for general guidance. Open a ticket for workspace-specific keys, origins, SSO, retention, or compliance-sensitive setup.
When should we use roadmap, changelog, or status?
Use roadmap for planned product work, changelog for shipped updates, and status for incidents or maintenance. Keep account-specific details inside tickets.
What should we check when support feels slow?
Start with the troubleshooting guidance. Review inbox connection, workflow configuration, ownership rules, and whether the issue belongs in a tracked ticket for deeper investigation.
Still need help?
If the library does not cover your case, move to the right support channel. Open a ticket for anything that needs a tracked answer or workspace-specific review. Use Discord for lighter questions and faster discussion.