Overview
SPRL Enterprise Support is designed to help organizations manage their platform requirements, troubleshoot issues, and maintain reliable business workflows across SPRL services.
Enterprise customers may require assistance with account configuration, custom domains, link management, integrations, APIs, campaigns, security-related questions, and other platform functionality.
Good to Know:
Before contacting support, collect the relevant account, domain, link, campaign, or integration details. Providing clear information helps the SPRL team understand the issue and respond more efficiently.
When to Contact Enterprise Support
Contact SPRL Support when you need assistance with a platform issue, configuration problem, or question that cannot be resolved through the Help Center.
- Custom domain configuration issues.
- DNS or SSL-related problems.
- Short-link or redirect issues.
- API integration problems.
- Campaign or platform configuration questions.
- Account-related issues.
- Security-related concerns.
- Unexpected platform behavior.
Before Contacting Support
Checking the relevant Help Center documentation before opening a support request can often help resolve common configuration and setup issues quickly.
- Search the SPRL Help Center for the relevant topic.
- Review the applicable troubleshooting guide.
- Confirm that your configuration matches the documented requirements.
- Check whether the issue affects one resource or multiple resources.
- Collect the information required to explain the problem.
Recommendation:
Include the exact error message, affected URL or resource, relevant screenshots, and the steps that led to the issue whenever applicable.
How to Contact SPRL Support
You can contact the SPRL team through the available support channels for assistance with your account and platform requirements.
For general questions, platform assistance, or account-related support, use the SPRL Contact page.
Contact Support:
Visit the SPRL Contact Us page to submit your request and provide the relevant details.
What to Include in a Support Request
Providing complete information helps the support team understand the issue without requiring multiple follow-up questions.
| Information | What to Provide |
|---|
| Account | Relevant account or organization information. |
| URL | The affected short link, destination URL, or page where applicable. |
| Domain | The affected custom domain or subdomain when reporting domain issues. |
| Error | The exact error message or unexpected behavior. |
| Steps | The steps that caused or reproduced the issue. |
| Screenshot | A screenshot showing the issue when it helps explain the problem. |
| Time | The approximate date and time when the issue occurred, where relevant. |
Custom Domain Support
Custom domain issues are commonly related to DNS configuration, propagation, domain verification, or SSL activation.
When contacting support about a custom domain, provide the affected domain and describe the current status shown in SPRL.
- Provide the affected domain or subdomain.
- Confirm when the DNS records were configured.
- Provide the relevant DNS configuration details where required.
- Describe the current verification or SSL status.
- Include any error message displayed by SPRL.
Learn More:
Review the SPRL Help Center guides for Custom Domains, DNS Configuration, SSL Activation, Domain Verification, and Domain Troubleshooting before contacting support.
API & Integration Support
When reporting an API or integration issue, provide enough technical information for the support team to understand the request and the resulting behavior.
- Identify the affected API operation or integration.
- Provide the endpoint or relevant API functionality.
- Include the HTTP status or error response where applicable.
- Describe the expected result.
- Describe the actual result.
- Include relevant request information without exposing private credentials.
Security Reminder:
Never send passwords, API keys, access tokens, or other private credentials in a support request. Remove or mask sensitive information before sharing logs or screenshots.
Security & Abuse Reports
Security vulnerabilities and abuse reports should be handled through the appropriate SPRL reporting process rather than being posted publicly.
If you believe you have discovered a security vulnerability affecting SPRL, follow the responsible disclosure process described in the SPRL Security Policy.
For suspicious or abusive SPRL links, use the SPRL Abuse Reporting process and provide the relevant URL and supporting information.
Important:
Do not include unnecessary personal information, passwords, API credentials, or other sensitive data when submitting a security or abuse report.
Support Request Best Practices
- Use a clear and specific subject.
- Describe the issue briefly at the beginning of the request.
- Provide the affected URL, domain, or resource.
- Include the exact error message where applicable.
- Explain the expected and actual behavior.
- Include relevant screenshots or technical information.
- Remove passwords and private credentials before submitting information.
- Avoid submitting duplicate requests for the same issue unless additional information is available.
Support & Troubleshooting Workflow
| Step | Recommended Action |
|---|
| 1. Identify | Clearly identify the affected account, domain, link, integration, or feature. |
| 2. Review | Search the Help Center and review the applicable documentation. |
| 3. Reproduce | Determine whether the issue can be consistently reproduced. |
| 4. Document | Collect error messages, URLs, screenshots, timestamps, and relevant details. |
| 5. Contact | Submit the support request through the appropriate SPRL support channel. |
| 6. Follow Up | Provide additional information if requested by the support team. |
Enterprise Support Checklist
| Requirement | Status |
|---|
| Issue clearly identified | Required |
| Relevant Help Center article reviewed | Recommended |
| Affected URL, domain, or resource identified | Required |
| Error message documented | Required if applicable |
| Steps to reproduce documented | Recommended |
| Screenshot or supporting information collected | Recommended |
| Sensitive credentials removed | Required |
| Support request submitted | Required |
Frequently Asked Questions
How do I contact SPRL Support?
For general support and account-related questions, use the SPRL Contact Us page to submit your request.
What information should I provide?
Provide the affected resource, a clear description of the issue, relevant error messages, steps to reproduce the problem, and supporting screenshots or technical information where applicable.
Should I send my API key to support?
No. Never send API keys, passwords, access tokens, or other private credentials in a support request.
Can support help with custom domain issues?
Yes. When reporting a custom domain issue, provide the affected domain and relevant DNS, verification, SSL, or error information.
Can support help with API integration issues?
Yes. Provide the relevant API operation, error response, expected behavior, actual behavior, and other non-sensitive technical information that can help explain the issue.
Where should I report a security vulnerability?
Security vulnerabilities should be reported through the responsible disclosure process described in the SPRL Security Policy rather than through a public channel.
Where should I report an abusive SPRL link?
Use the SPRL Abuse Reporting process to submit suspicious or abusive links for review.
Quick Reference
| Support Area | Recommended Channel or Action |
|---|
| General Support | Contact the SPRL Support team through the Contact Us page. |
| Help & Troubleshooting | Search the SPRL Help Center for the relevant guide. |
| Custom Domains | Review DNS, SSL, verification, and domain troubleshooting documentation. |
| API Integration | Provide relevant non-sensitive technical details and error information. |
| Security Vulnerability | Follow the SPRL responsible disclosure process. |
| Abuse Report | Use the SPRL Abuse Reporting process. |
Learn More:
Explore the SPRL Help Center for detailed guides on Enterprise Security, API Integration, Migration, Custom Domains, Troubleshooting, and other platform features.
Tip: A clear and complete support request usually makes troubleshooting easier. Include the affected resource, exact error, expected behavior, actual behavior, and relevant supporting information while keeping passwords and private credentials confidential.