How to set up toll-free verification for SkioSMS

Before you start

Have your legal business name, address, and business registration number (for US businesses, this is your Employer Identification Number (EIN)) on hand before you start.
Use the contact details of the person responsible for this verification request. This is who Twilio and Skio's support team will reach out to if there's an issue with the submission.
UK merchants: toll-free number provisioning requires manual setup and isn't completed through this survey. Contact help@skio.com to enable bundles or local numbers for your UK customer base.

Your business name, corporate website, and email domain must match, or your submission may be rejected. Learn more about verification rejection reasons on Twilio’s website here.

How to set up toll-free verification with Twilio

Step 1: Start the verification request

In the left-hand menu of your Skio Dashboard, go to Retain > SkioSMS. If SkioSMS is already enabled and you need to complete or redo verification, go to the Settings tab on the SkioSMS page and click on Toll-free verification survey.

Access the toll-free verification survey anytime from your SkioSMS settings.

Step 2: Enter your business contact information

On the Business Contact Information screen, enter the details for the person responsible for this verification:

First name and Last name.
Email.
Phone number, entered with the country code (for example, 13125918300 for a US number).
Business website, entered as a full URL (for example, https://yourstore.com).

Select Next to continue.

Step 3: Enter your business information

On the Business Information screen, enter your business's legal name and address:

Business name.
Street address, and optionally a Street address 2 line.
City and Postal code.
Country.

Select Next to continue.

Step 4: Enter your business registration details

On the Business Registration screen, enter your business's registration information:

Business registration country.
Business type: choose from Private for-profit, Public for-profit, Non-profit, Sole proprietor, or Government.
Registration authority (for example, EIN - Employer Identification Number (US)).
Business registration number. This is required, and for US businesses is your EIN (formatted like 12-3456789).
Doing business as (optional), if your business operates under a different name than your legal name.

Select Next to continue.

Step 5: Add SMS Terms language to your Terms of Service

You'll be asked to add SMS-specific language to your store's Terms of Service:

Enter your Terms of Service URL and Privacy Policy URL.
Skio generates SMS Terms language for you to copy and paste into your existing Terms of Service. Use Copy to clipboard to grab the text.
Select the checkbox acknowledging that Skio isn't providing legal advice by generating this language, and that you should consult your own legal counsel to confirm compliance with applicable laws for your SMS activities.

You must select the checkbox before you can continue.

Step 6: Review and submit your request

On the Review Information screen, check your business contact information, business information, and business registration details. Select Previous if you need to make changes, or Continue once everything looks correct.

On the Confirm Submission screen, review the summary one more time and select Submit Request. This sends your information to Twilio for processing.

Note: Skio's support team will reach out if there are any issues with your submission, or if additional information is needed.

What happens after you submit

Your Twilio number can't send messages to customers until verification is complete.

Verification timing depends on Twilio's review process. You can check your verification status in the Settings tab on the SkioSMS page. This can take anywhere from a few minutes to one week.
If Skio's support team needs more information to complete your submission, they'll contact the business contact you entered in Step 2.

If your verification is rejected

Find your error code

Twilio's rejection notice includes a specific error code. Search for that exact code rather than a similar-sounding one — a related code doesn't cover the same requirements, and correcting for the wrong one won't resolve your rejection. The table below summarizes common codes; each linked code has the full correction requirements.

See a full list of rejection reasons in Twilio’s guide here.

Note: Cancellation and account/profile-related rejections follow a different process than content or opt-in rejections. Always check the specific row and status tied to your request rather than assuming a general fix applies.

Common toll-free verification rejection reasons

Error code	Rejection reason	What to fix
30482	Business email isn't on an official company domain	Resubmit using an email address at your business's own domain, not a generic or personal one.
30484	Business name doesn't match official records	Enter your business name exactly as it appears on your registration documents.
30527	Business registration number missing or invalid	Confirm your EIN (or equivalent) is entered correctly and matches your registration country.
30489	Website isn't established or active	Make sure your business website URL loads, is live to the public, and reflects an active business.
30491	Website requires a login or is password-protected	Submit a URL that's publicly accessible without credentials.
30493	Privacy policy or Terms of Service URL missing, broken, or lacking SMS terms	Confirm the link loads for anyone without logging in, and that it includes SMS-specific disclosures (message frequency, rates, opt-out).
30498	Opt-in workflow doesn't match your submission	Make sure your written description of how customers opt in matches the actual example or screenshot you provide.
30509	Opt-in example URL isn't accessible	Provide a public URL to your opt-in flow, or submit screenshots if it's behind a login.
30496	Use case and use case summary are inconsistent	Make sure your description of how you'll use SMS matches the messaging examples you submit.
30499	Message content doesn't align with use case	Confirm your sample messages match the use case category you selected.

Warning: Some rejections — including fraud, gambling, cannabis/CBD, cryptocurrency, and similar restricted categories — aren't eligible for resubmission. These require a different use case or channel rather than a corrected form.