Viewing and Exporting Serial Numbers by Blueprint/Provisioning Template Before Device Onboarding

Android

Title: Serial numbers missing or unverified before device provisioning — view and export by Blueprint

When devices are pre-registered in Esper but not yet provisioned, serial numbers and their Blueprint assignments are only visible if your list view is configured correctly and filtered to show the Registered device state.

Why this happens

Esper separates devices into distinct states. A device that has had its serial number imported under Provisioning Methods but has not yet been provisioned sits in the Registered state. The default Devices & Groups list view does not show this state or the Serial Number column unless you explicitly configure both, which means pre-registered devices can appear absent even when the import succeeded.

Before you start

Serial numbers must already be added to your Esper account under Provisioning Methods — either entered manually or imported via CSV. If you have not done this yet, complete that step first before following the instructions below.

View serial numbers and their Blueprint assignments

1. Navigate to Devices & Groups in the Esper Console.
2. Click Views → Customize List View and add the Serial Number column to your visible columns, then save the view. This column is hidden by default and must be enabled manually.
3. Apply the filter Device State → Registered to limit the list to devices that have been pre-registered but not yet provisioned.
4. Review the list, which now displays Device IDs, serial numbers, and the Blueprint or provisioning template assigned to each entry.
5. Use the on-screen search or apply an additional Blueprint filter to confirm which blueprint a specific serial number is assigned to.

Export serial numbers for bulk auditing

1. Navigate to Devices & Groups in the Esper Console.
2. Apply the filter Device State → Registered. Optionally, also filter by a specific Blueprint to scope the export to a single provisioning template.
3. Click the Download icon located next to the Filter button.
4. Select Download as CSV (recommended for large deployments) or Download as Excel.
5. Open the exported file and confirm that serial numbers and Blueprint assignments are present as expected. For deployments with hundreds or thousands of devices, the CSV export is the only practical way to audit at scale.

Verify: The exported file should contain one row per pre-registered device, with Serial Number and Blueprint columns populated. If you filtered by Blueprint before downloading, only devices assigned to that blueprint should appear in the file.

Troubleshooting

• Serial numbers do not appear in the Registered state list: Confirm that the CSV import or manual entry under Provisioning Methods was completed and saved. A partially completed import will not surface any records.
• Serial Number column is missing from Customize List View: Verify that your user account has a role with sufficient permissions in the Esper Console. Read-only or restricted roles may not have access to column customization.
• Exported file does not include Blueprint assignment data: Apply the Blueprint filter before downloading, then re-export. Blueprint data is only included when that filter is active at the time of export.

If this doesn't resolve it

If serial numbers confirmed as successfully imported via CSV are still not appearing in the Registered device list, this may indicate a data ingestion issue on the platform side. Collect the following before contacting Esper Support:

• The original CSV file used for import
• A screenshot of the import confirmation screen
• Your Esper account (enterprise) name and the date of the import attempt

Still need help?

If you're unable to view or export serial numbers by blueprint or provisioning template, please submit a support ticket and include the specific blueprint or template name, the number of devices affected, and whether you're experiencing this issue before or after device onboarding.