Business software troubleshooting

Business software problems, explained clearly.

Find the exact issue, understand what is causing it, and get to the setting or fix that matters.

Exact intentStart from the symptom
Useful orderLikely checks come first
Real payoffFinish by verifying the fix
Software index

Go straight to the product involved.

Each software hub narrows the problem by feature, workflow, setting, or failure state. No logo wall and no generic product summaries.

Browse all software
01
HubSpotWorkflows · Contacts · Forms · Email · Integrations · Permissions · Imports · Reporting · Billing & Plans
View fixes
Troubleshooting desk

Specific problems. A useful next check.

Curated guides that begin with the failure itself rather than a generic introduction to the software.

Diagnosis

Broken—or simply limited?

A missing option or stopped workflow can look like a bug when the real cause is a permission, usage ceiling, account type, or plan boundary.

01 / Configuration path

Usually worth checking as configuration

  • It worked before.
  • Only one user or workspace is affected.
  • An integration was reconnected or permissions changed.
  • A trigger or condition no longer matches.
OR
02 / Product boundary

Possibly a plan or product limitation

  • The feature is completely missing.
  • A usage or automation limit has been reached.
  • The option only exists on a higher plan.
  • The account type does not support the feature.
Coverage index

Browse by the work you are trying to get done.

A compact route into the software library, not a generic category feed.

Editorial method

Useful troubleshooting should reduce uncertainty.

A BusinessTally troubleshooting guide should identify the actual failure state, show the most likely checks first, separate configuration problems from software limitations, and explain how to confirm the issue is resolved.

01Name the failure precisely

No broad “software not working” advice.

02Prioritize the likely check

Settings, permissions, data flow, limits, then edge cases.

03Verify the behavior changed

The article should tell you how to confirm the fix actually worked.