01Who this is for
- Agency owners who manage multiple client locations need clear accounting for each Twilio subaccount.
- Founders of marketing firms that resell phone services can separate billing per client by using agency managed Twilio.
- Businesses that have migrated to HighLevel’s native LC Phone can still use Twilio for legacy locations.
02Agency managed Twilio and phone rebilling, explained
The feature maps a HighLevel location to a specific Twilio subaccount by storing the Twilio Account SID in the Phone Integration settings. This mapping ensures that numbers, call logs, and SMS usage are linked to the correct client location.
Once the mapping is correct, agencies can turn on Phone Rebilling. The rebilling settings let the agency add a markup or usage fee that HighLevel will charge the client for each call or message sent through the Twilio connection.
If multiple locations share the same Twilio SID, the platform provides a troubleshooting workflow to reassign each location to its proper subaccount, move numbers if needed, and test the connection before billing.
03How businesses use agency managed Twilio and phone rebilling
- Digital marketing agency. The agency checks each client location’s Subaccount Settings, matches the displayed SID with the Twilio console, and then configures a markup in Phone Rebilling so the client is billed for their own call usage.
- Consulting firm with separate phone lines per office. The firm verifies that each office location points to its dedicated Twilio subaccount, then enables Phone Rebilling to apply office specific charges in the client’s SaaS billing profile.
- Call center outsourcing provider. The provider ensures every call queue location uses a distinct Twilio SID, updates any mismatches, and sets up Phone Rebilling to reflect the precise usage per queue before activating client invoices.
04Before you start
- Confirm the agency is using its own connected Twilio account.
- Identify the HighLevel location that will be configured.
- Determine the correct Twilio subaccount for that location.
- Make sure the required phone numbers exist under that Twilio subaccount.
- Check that the location’s Twilio Account SID is recorded in HighLevel.
- Fix any shared or mismatched Twilio SID before enabling rebilling.
05How to set up and use agency managed Twilio and phone rebilling in HighLevel
Verify the Twilio subaccount for a HighLevel location
- Sign in to HighLevel and switch to Agency View.
- Navigate to Settings > Phone Integration.
- Open the Subaccount Settings tab.
- Locate the target HighLevel location.
- Confirm the location is managed by Twilio.
- Record the Account SID shown for the location.
- Log in to the agency’s connected Twilio account.
- Find the Twilio subaccount whose SID matches the recorded value.
Configure phone rebilling
- Verify the correct HighLevel location is selected.
- Ensure the phone provider is the agency managed Twilio account.
- Confirm the Twilio Account SID matches the location’s subaccount.
- Check that the client’s billing or payment setup aligns with your SaaS configuration.
- Set the desired Phone Rebilling markup or usage billing parameters.
- Review the client facing billing configuration prior to activation.
Troubleshoot multiple locations using the same Twilio Account SID
- Go to Agency View > Settings > Phone Integration > Subaccount Settings.
- Locate the affected locations in the list.
- Compare the Account SID displayed for each location.
- Identify any locations that share the same Twilio Account SID unexpectedly.
- In the agency’s Twilio console, review all existing subaccounts.
- Determine which subaccount should belong to each affected HighLevel location.
- If a needed subaccount does not exist, create it following Twilio’s procedure.
- Note the correct Account SID for the intended subaccount.
- Return to Agency View > Settings > Phone Integration > Subaccount Settings, select the location, and update its connection with the correct subaccount information.
- Save the change and verify that the displayed Account SID now matches the intended subaccount.
06Settings that matter
- Subaccount Settings. Shows the Twilio Account SID linked to each HighLevel location and lets you edit the connection to a different Twilio subaccount.
07Things to know before you rely on it
- Phone rebilling does not replace an incorrect Twilio location mapping; the mapping must be fixed first.
- Moving a phone number between subaccounts does not automatically move contacts, call history, or compliance settings.
- The Move Numbers tool only supports eligible US and Canada numbers within the same agency and master Twilio account.
- Reusing another client’s Twilio subaccount to avoid creating a new one is not recommended.
- The guidance applies only to locations using an agency managed Twilio account; LC Phone locations follow a different setup.
08If something goes wrong
- Multiple locations share the same Twilio Account SID. Identify the correct Twilio subaccount for each location, update each location’s Subaccount Settings with the proper SID, and verify the change before enabling Phone Rebilling.
09How it connects to the rest of HighLevel
- Activate phone rebilling in SaaS mode Phone rebilling activation
- Manage SaaS wallet credits for client billing SaaS wallet credits
- Review HighLevel pricing and plan options Pricing and plans
Michael's take

Wondering if you really need to map each location to its own Twilio subaccount before you start rebilling? The short answer is yes. It keeps your numbers, usage and invoices tidy and avoids a lot of head scratching later. I’d first verify the Account SID for each location in Settings > Phone Integration > subaccount Settings, then match that SID to the right subaccount in your Twilio dashboard.
Once the mapping is solid, set up your phone rebilling markup or usage billing. Double check the client facing billing details before you flip the switch. If something looks off, fix the subaccount link first. Rebilling won’t clean up a mismatched SID.