Export a case list for an account review or operational handoff

An export gives you a point-in-time copy of an operational list for an account review, a management discussion or a controlled handoff. In B2B support, the important work is choosing the right customer scope and useful columns before creating the file. Supportbench exports the rows matching the authorized current view and filters across pages; checking a few case boxes does not restrict the export to those cases.

Export the list you actually intend to share  ·  Understand what the export includes  ·  Choose PDF or spreadsheet for the next task  ·  Check saved-view export preferences  ·  Worked example: prepare a weekly customer account review  ·  Verify the result before relying on it  ·  Troubleshoot export problems

Export the list you actually intend to share

1. Open Cases and choose the intended agent, queue or saved view. Confirm the account/company scope and current filters.
2. Review the resulting rows, sorting, grouping and column choices. If you need one company’s open requests, filter to that company and the intended states before exporting. Selecting checkboxes is not an export filter.
3. Open Export in the Case list toolbar. Choose Export to PDF for a document-style copy or Export to Spreadsheet for an XLSX workbook.
4. Wait for the download and open the actual file. Confirm its title/context, columns, representative case IDs and customer scope. A file being downloaded is not proof that its filter means what you intended.
5. Store or share the file through your organization’s approved process, with a clear explanation of when it was produced and what the filters include.

You need permission to export the list. If the control or operation is unavailable, ask an administrator to check your export capability and access to the underlying records. The guide does not promise password protection, a secure-sharing link or automatic expiry for a downloaded file.

Understand what the export includes

Choose PDF or spreadsheet for the next task

The current spreadsheet export is XLSX; older instructions describing only an XLS download are outdated. Spreadsheet export supports the relevant Cases, Activities, Surveys and Assets list types. Use the correct list’s meaning and authorization when exporting a different type.

Check saved-view export preferences

For a live grid, hidden columns and columns marked non-exportable are filtered from the requested export columns. For a saved view, its persisted visible-column and ID-exclusion export preferences can control the server’s projection instead. This is why a quick on-screen column change may not produce the column set you expected.

• Review the saved view’s export preferences through the view configuration owner.
• Open a small representative export and check whether the expected identifiers and customer context are present.
• Keep the columns needed for the recipient’s decision. A weekly account review may need case ID, subject, state, owner and commitment context; it rarely needs every available field.
• If the export differs from the screen, compare the saved preferences before treating the download as stale or retrying repeatedly.

Use the view-building guide for list design and the relevant configuration reference for export preferences. Do not assume every user can edit a shared view simply because they can export it.

Worked example: prepare a weekly customer account review

An account owner is meeting a customer with several contacts and a recurring equipment issue. The useful report should help the meeting decide what needs attention, who owns it and what update is due. It should not mix unrelated customer records or imply that a snapshot is a live dashboard.

1. Start from the approved account-review view or create the appropriate view through the supported workflow. Filter to the intended company and explicitly decide whether the meeting includes open work, recently closed work or both.
2. Review several representative cases in Supportbench. Confirm that the company relationship and state criteria match the meeting’s purpose.
3. Choose readable columns and an ordering that puts the required decisions together. Do not infer the number of distinct incidents solely from rows if related cases exist.
4. Export to Spreadsheet when you need meeting annotations, or PDF when a document is more suitable. Inspect the actual output before distribution.
5. Describe the scope and creation time in the meeting material. Record decisions, ownership changes and customer commitments back in Supportbench through their normal actions; spreadsheet annotations alone do not update the case.

For a recurring delivery, use scheduled views and verify its recipients, schedule and scope separately. A one-time export does not create or test a scheduled report.

Verify the result before relying on it

• Check a known included case and a known excluded case against the chosen filters.
• Confirm that the customer/company scope is correct and the file contains the columns the recipient needs.
• Inspect grouped output, totals and long text for readability. Do not treat a group header as a case row when counting manually.
• Check whether new case changes occurred after the export. Refresh the report when current information matters, and keep the snapshot date clear.
• Follow your organization’s rules for storing, sharing and deleting customer-data exports.

Troubleshoot export problems

Continue learning

• Build views for operational decisions
• Schedule recurring data-view reports
• Use bulk actions on selected cases
• Interpret KPI scorecards and trends