Software Help HQ Guides

Troubleshoot software, verify results, and choose with care.

Read a CSV Header Before Importing Contacts

Inspect the first line of a CSV safely, identify mismatched columns and document the mapping before any real import.

When to Stop Troubleshooting and Ask the Vendor for Help

Set a stopping rule when troubleshooting exceeds your authority, recovery capability or provider-side visibility.

The Fix Worked Once. Check the Neighboring Steps Before Closing the Issue

Use a narrow regression record to verify the fixed step and its nearest relevant dependencies.

An Incident Crossed Midnight: Put Its Timestamps on One Timeline

Preserve original timestamps, normalize explicit offsets and keep unknown timezones visibly unresolved.

Check Which Account and Workspace You’re In Before Troubleshooting

Check account, workspace, object and role before importing data or changing a configuration.

Read an Error Message in Five Parts Before Searching

Read an error in five parts and remove private values before searching official troubleshooting information.

Write a Support Ticket Without Sending Passwords or Customer Records

Prepare a useful support ticket with precise reproduction steps and inspected, redacted evidence.

How to Keep Track of a Software Test Without Sharing Private Data

Document a safe software test with seven useful fields, redact private details and prepare a support-ready summary.

Your Automation Ran Without Errors — So Why Did Nothing Happen?

Investigate successful automation runs that produce no intended result by checking destination records and missing outcomes.

Connecting a Form to a CRM? Preserve This Information First

Preserve identity, answers, source context, permission records and the original submission when connecting a form to a CRM.