Status updates and support channels
2 min read
Updated Apr 10, 2026
Good operations depend on knowing where to look when something feels wrong. Signelio keeps public service status separate from product and support conversations, and both matter during an integration or rollout.
Before you begin
A question or operational issue
A sense of whether the problem is service-wide or document-specific
Relevant package identifiers if the issue is workflow-specific
Use the Status Page for broad health questions
If something feels like a wider service issue, the public Status Page is the first place to check.
That helps you avoid opening a narrowly framed ticket for a platform-wide incident.
Use support for workflow-specific help
When the issue is tied to a specific workspace, document, or rollout plan, use Support or Contact Us.
Include the minimum context needed for the team to help quickly.
Keep the channels distinct
Status tells you what the platform is doing broadly, while support helps with your specific implementation or workflow question.
Using the right channel reduces back-and-forth.
Pro Tips
Check status first when several users report the same issue.
Include workspace and document context when the issue is not platform-wide.
Record where your team should look first during urgent signing periods.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.