How to use SWS Agent Help
SWS Agent Help is written for tenant users operating the CRM—not for engineers. Topics follow a repeatable structure so you can execute, verify, and fix issues without guessing.
Video
Who can do this
All readers.
What you'll accomplish
- Know where to start by situation
- Understand sections inside task articles
- Use See also links for related workflows
Step-by-step procedure
Start here if you are…
| Situation | Start with |
|---|---|
| Brand-new workspace | Set up your workspace |
| Looking for Settings | All Settings |
| Configuring AI | Knowledge Hub |
| Daily CRM | Contacts overview · Inbox overview |
| Something broke | FAQ + topic Troubleshooting |
Task article anatomy
- Overview — what and why
- Video placeholder (
VideoSlot) - Who can do this — roles
- Before you begin — prerequisites
- What you'll accomplish — success criteria
- Step-by-step procedure — bold UI labels
- Verify your work — expected outcomes
- Tips / Important admonitions
- Troubleshooting table
- See also links
Paths and permissions
Routes like /email-campaigns are intentional—bookmark them. Missing menus usually mean role or module gates.
Depth rollout
Core onboarding and Settings topics lead in depth; Marketing, Automation, Reports, and Reference are enriched to the same standard. Short pages link onward via See also.
Extended guidance
Use Verify your work sections as QA scripts when training new admins—have them demonstrate each bullet. Video placeholders will become walkthroughs; until then, rely on bold UI labels matching the live product.
Practice scenarios
Pick a random task article, identify all ten structural sections, complete Verify your work bullets in product. Teach a colleague to find Troubleshooting tables in under two minutes using sidebar search.
Sandbox validation
Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.
Team rollout checklist
Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.
Keep learning
Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.
Verify your work
- Found answer using Troubleshooting table
- Video placeholder noted for future walkthrough
Tips
Use workspace search if sidebar item hidden—some modules are role-gated.