Oops! Facing network problem. Unable to load this page. Refresh
SPRL

Just a moment...

Hello Guest

logo

FAQs

Help Center

Enterprise

Enterprise Onboarding Guide

Learn how to set up and launch your SPRL Enterprise environment, including organization planning, custom domains, platform services, API integrations, security requirements, testing, and production deployment.

Overview

The SPRL Enterprise Onboarding Guide helps organizations prepare, configure, and launch their SPRL environment in a structured manner.

A well-planned onboarding process helps ensure that your organization has the required users, domains, platform capabilities, integrations, security settings, and operational processes ready before beginning production use.

Good to Know:
SPRL provides unlimited user login access. Enterprise onboarding should therefore focus on your organization's structure, domains, products, integrations, usage requirements, and operational workflows rather than user-seat planning.

Before You Begin

Before starting your Enterprise onboarding, identify the main requirements your organization expects to implement on SPRL.

  • Organization and administrative requirements.
  • Users who require platform access.
  • Custom domains and subdomains.
  • Expected link and traffic volume.
  • Marketing and communication solutions.
  • API and integration requirements.
  • Security and privacy requirements.
  • Existing workflows that need to be migrated or connected.

Enterprise Onboarding Process

StageWhat to Do
1. PlanIdentify your organization's requirements, domains, products, integrations, and expected usage.
2. ConfigureSet up your organization, platform resources, custom domains, and required services.
3. IntegrateConnect SPRL with your websites, applications, APIs, and business workflows.
4. TestVerify domains, links, APIs, campaigns, forms, and other required functionality.
5. LaunchMove approved workflows and campaigns into production use.
6. MonitorReview usage, analytics, platform activity, and operational performance.

Step 1: Plan Your Organization

Start by documenting how your organization intends to use SPRL. This provides a clear foundation for the rest of the onboarding process.

  • Identify the primary administrator or administrators.
  • Identify the departments or business functions using SPRL.
  • Determine which users require access.
  • Define responsibilities for domains, campaigns, APIs, and platform resources.
  • Identify the SPRL products required by each business function.
Important:
Since SPRL provides unlimited user login access, you do not need to plan your onboarding around purchasing individual user seats.

Step 2: Configure Custom Domains

If your organization uses branded links, configure your custom domains before launching production campaigns.

  1. Add your custom domain in SPRL.
  2. Configure the required DNS records.
  3. Complete domain verification.
  4. Wait for SSL activation.
  5. Test the domain using a sample branded link.

If you manage multiple brands or business units, repeat the process for each required domain.

Recommendation:
Keep a record of your domain configuration and DNS settings. This can simplify future troubleshooting and additional domain setup.

Step 3: Configure Your Platform Services

Identify and configure the SPRL products and services your organization plans to use.

ServiceOnboarding Consideration
URL ShortenerDefine branded link requirements and campaign workflows.
AnalyticsIdentify the metrics and reporting requirements for your organization.
SMS MarketingConfigure campaigns, contacts, and required messaging workflows.
Email MarketingPrepare subscriber lists, campaigns, and communication workflows.
Email VerifierDefine the email verification workflow for your contact data.
WhatsApp Business APIConfigure the required WhatsApp account, campaigns, contacts, and messaging workflows.
Custom Form MakerPrepare forms, fields, destinations, and data collection workflows.

Step 4: Configure API Integrations

If your organization plans to automate SPRL operations or connect SPRL with internal applications, configure the required API integrations before production launch.

  • Identify the applications that need to connect with SPRL.
  • Determine which API capabilities are required.
  • Create and securely store API credentials.
  • Configure the integration in your application.
  • Test API requests in a controlled environment.
  • Verify error handling and authentication.
Security Reminder:
API keys and other authentication credentials should be treated as confidential information. Do not publish them in client-side code, public repositories, or other publicly accessible locations.

Step 5: Configure Security & Privacy Requirements

Review your organization's security and privacy requirements before moving production workflows to SPRL.

  • Review the SPRL Security Policy.
  • Review the Privacy Policy.
  • Review the Data Processing Agreement where applicable.
  • Review the Acceptable Use Policy.
  • Review the API Terms of Use.
  • Define internal responsibilities for account and platform access.
Security Resources:
Visit the SPRL Trust Center for information about platform security, privacy, data protection, responsible disclosure, and related trust resources.

Step 6: Test Before Launch

Testing is an important part of Enterprise onboarding. Complete your testing before moving important campaigns or workflows into production.

AreaWhat to Test
Custom DomainsVerify DNS, SSL, branded links, root redirection, and 404 handling.
Short LinksConfirm links redirect to the correct destinations.
AnalyticsVerify that expected traffic and activity are recorded correctly.
FormsSubmit test responses and verify the expected workflow.
MarketingTest campaigns and messaging workflows before production use.
APIVerify authentication, requests, responses, and error handling.

Step 7: Launch

After completing configuration and testing, your organization can begin using SPRL for production workflows and campaigns.

Before launching a major campaign, perform a final review of the destination URLs, branded domains, campaign settings, tracking configuration, and required integrations.

  • Confirm all production domains are active.
  • Verify important short links.
  • Confirm campaign destinations.
  • Verify analytics and tracking requirements.
  • Confirm API integrations are functioning correctly.
  • Review any scheduled campaigns before activation.

Post-Onboarding Management

Enterprise onboarding does not end when the initial configuration is complete. As your organization grows, review your SPRL environment periodically and update it according to your changing requirements.

  • Add new custom domains when required.
  • Review existing platform resources.
  • Monitor link and traffic usage.
  • Review campaign performance.
  • Maintain API integrations.
  • Review security and privacy requirements.
  • Update internal documentation when workflows change.

Enterprise Onboarding Checklist

RequirementStatus
Organization requirements documentedRequired
Administrators and responsibilities identifiedRequired
Required custom domains identifiedRequired
DNS and SSL configuration completedRequired
Required SPRL products configuredRequired
API integrations configuredRequired
Security and privacy requirements reviewedRequired
Production workflows testedRequired
Production launch completedRequired

Frequently Asked Questions

How long does Enterprise onboarding take?

The time required depends on the organization's requirements, number of domains, integrations, products, and workflows being configured.

Do I need to create a separate account for every employee?

No. SPRL provides unlimited user login access. Authorized users can access the organization's SPRL environment according to the applicable account and access configuration.

Can I configure multiple custom domains during onboarding?

Yes. Multiple custom domains can be configured according to your organization's requirements and applicable account limits.

Can I integrate SPRL with my existing application?

Yes. SPRL provides API capabilities for supported integrations and automated workflows.

Should I migrate everything at once?

Not necessarily. Organizations may prefer to begin with a controlled set of links, domains, campaigns, or workflows, validate the configuration, and then expand the migration.

Can I add new services after onboarding?

Yes. Your SPRL environment can be expanded as your organization's requirements evolve and additional platform capabilities are needed.


Quick Reference

StageSummary
PlanIdentify organization, domain, product, integration, and usage requirements.
ConfigureSet up domains, products, and required platform resources.
IntegrateConnect SPRL with applications and business workflows.
TestValidate domains, links, campaigns, APIs, and other workflows.
LaunchMove approved workflows into production use.
MonitorReview usage, analytics, and operational performance.

Learn More:
Explore the SPRL Help Center for detailed guides on Enterprise Overview, Managing Large Organizations, Enterprise Security, API Integration, Migration, Enterprise Support, and Enterprise Best Practices.
Tip: Start with a structured onboarding plan and test your most important workflows before moving large campaigns or production processes to SPRL. This makes it easier to identify configuration issues early and establish a reliable operating process for your organization.

Need more help?

Our support team is always happy to assist you.

×

We use cookies to improve your experience, analyse traffic, and personalise content. By clicking “Accept”, you consent to the use of cookies as described in our Cookie Policy .

Accept cookies Read our Cookie Policy