Troubleshooting
Last updated February 28, 2026
Common setup and operational issues with practical fixes.
Support page loads but ticket cannot be submitted
Check:
- Website API key is correct
- At least one template exists for the website
- Template required questions are properly answered
File upload issues
Check:
- Client-side file constraints in your support UI
- Organization storage usage versus plan quota
- Correct multipart request forwarding in your app
Workflow menu is disabled
Check:
- Your organization role is
owneroradmin - Your plan is
growthorenterprise
Cannot open organization settings
Organization settings are owner-only.
Confirm the current member role in the active organization.
Article not visible publicly
Only PUBLISHED articles are visible in public support experiences.
Customer ticket link expired
Ticket links are time-bound for security.
If expired, request a fresh ticket access link through your support flow.
Emails not being delivered
Check:
- Open your Website settings and verify the email delivery mode is enabled
- Confirm that the sender email address and domain are correctly configured
- Check spam folders — initial emails from a new domain may be flagged by recipient mail providers
- If using a custom domain, ensure DNS records (SPF, DKIM) are properly set up
Workflow not executing
Check:
- Your plan supports workflows — only
growthandenterpriseplans have access. See Billing and Plans - The workflow is in an active state, not paused or in draft
- Trigger conditions match the ticket event — review the trigger type and filters in Workflows
- The workflow was created after the ticket — workflows do not retroactively apply to existing tickets
Team member cannot see tickets
Check:
- The member is assigned to a Team that has access to the relevant website
- The member's role allows ticket visibility —
memberrole users can only see tickets assigned to their team - The ticket is not assigned to a different team exclusively
- The member has accepted the organization invitation and completed onboarding
API key returns 401
Check:
- The API key belongs to the correct website — each website has its own key
- The key may have been rotated — regenerating a key invalidates the previous one immediately
- Ensure the key is passed in the correct header format as described in API Endpoints
- Check that the website has not been deleted or deactivated
Storage quota exceeded
Check:
- Your organization has reached the file storage limit for its current plan. See Billing and Plans
- Review storage usage in the organization settings dashboard
- Delete unused file attachments from resolved tickets to free space
- Upgrade your plan if you consistently need more storage capacity