Most SuiteDash problems we are asked to fix come from the same handful of setup decisions. None of them are unusual, and none of them need a rebuild. Here is what they look like and how to fix each one.
Too many custom fields
It is tempting to create a field for everything. The result is records so long that nobody fills them in, and reports nobody trusts.
Fix: list the fields you actually use to make decisions or send messages. Retire the rest, or merge them. A short record that is always complete beats a long one that is half empty.
Tags that mean the same thing
“Client”, “Active client” and “Current” all describe the same contacts. Over time, automations start depending on one tag while your team applies another.
Fix: agree a short tag list with a one-line definition for each tag. Merge duplicates, then update every automation that referenced the old tags.
Automations built before the process was settled
Automations depend on forms, stages and templates. When those change after the automation is built, it keeps waiting for something that no longer happens.
Fix: list each automation, what triggers it and what it does. Fix the ones pointing at old forms or stages, and remove any that overlap. Then build new automations only after the pieces they connect are stable.
A portal that shows everything
When every module is switched on, clients can’t tell what you need from them, so they reply by email instead.
Fix: rebuild the dashboard around three things: what the client needs to do, what you have shared, and how to reach you. Switch off everything else until a client needs it.
No custom domain or branded emails
Clients hesitate when a portal invitation arrives from an address they don’t recognize, and some of those emails land in spam.
Fix: set up your custom domain with a CNAME record, brand your login page and send system emails in your brand. It is one of the quickest wins in SuiteDash.
No documentation
A year later, nobody knows why a setting exists or what an automation was for, so nobody dares change it.
Fix: keep a short document with your field list, tag definitions, pipeline stages and automation list. Update it whenever you change the setup.
If your account shows several of these symptoms, a SuiteDash audit and clean-up is usually faster than starting again.
Questions
Do I need to rebuild SuiteDash to fix setup mistakes?
Rarely. Most setup mistakes can be fixed with a structured clean-up: merging duplicate records, trimming fields and tags, restructuring pipelines and untangling automations. A rebuild makes sense only when the account was designed for a different business model or nobody can predict what the automations do.