How to Set Up HelpBuilder: Step-by-Step Onboarding Guide
Getting HelpBuilder up and running quickly ensures your support team starts delivering faster, more consistent answers. This guide assumes a standard HelpBuilder account and covers account setup, workspace configuration, agent onboarding, knowledge base creation, and live deployment.
1. Before you start (prep checklist)
- Admin account: Ensure you have an admin login.
- Team list: Names, roles, and email addresses for agents.
- Brand assets: Logo, colors, and help center URL.
- Content inventory: Existing FAQs, canned replies, and documentation.
- Integrations: List of tools to connect (e.g., Zendesk, Slack, CRM).
2. Create your account and verify domain
- Sign up at HelpBuilder’s signup page with your admin email.
- Verify your email and complete basic company details (name, timezone, language).
- Add and verify your support domain or help center URL (DNS TXT or CNAME as required).
3. Configure company settings
- Upload logo and set brand colors under Appearance.
- Set default timezone, business hours, and holiday schedule.
- Configure support email address ([email protected]) and reply-to settings.
- Set security options: enforce SSO (if available), password policy, and 2FA for admins.
4. Set up teams, roles, and permissions
- Create teams (e.g., Tier 1, Tier 2, Billing, Product).
- Define roles: Admin, Manager, Agent, and Contributor.
- Assign permissions at team and role level (ticket visibility, KB editing, analytics access).
- Add users by email and assign them to teams and roles. Send invites.
5. Connect channels and integrations
- Email: configure inbound routing so support@ emails create tickets.
- Live chat: install chat widget snippet on your site and customize greetings.
- Social and messaging: connect Facebook, Twitter, WhatsApp if needed.
- Integrations: link Slack for notifications, CRM for contact sync, and analytics tools.
6. Build your knowledge base
- Import existing content via CSV, Markdown, or direct copy-paste.
- Create categories (Getting Started, Billing, Troubleshooting).
- Write or refine top 10 articles first: concise titles, clear steps, screenshots.
- Create reusable macros/canned replies for common ticket types.
- Set article visibility (internal vs public) and SEO metadata for public articles.
7. Configure ticket workflows and automation
- Create ticket pipelines: New → Triaged → In Progress → Resolved → Closed.
- Set SLA rules for response and resolution times by priority.
- Add automations:
- Auto-assign by keyword or team workload.
- Auto-acknowledgement emails on ticket creation.
- Escalation rules for missed SLAs.
- Create tags and custom fields for reporting (product, severity, region).
8. Onboard agents
- Provide a short onboarding checklist: login, set status, handle a test ticket.
- Run a 30–60 minute training session covering:
- Ticket triage and response standards.
- Using KB articles and attaching macros.
- Escalation and SLA expectations.
- Assign each new agent a mentor for the first week.
- Monitor initial tickets and give feedback.
9. Test everything before going live
- Submit test tickets via email, chat, and web form.
- Verify automations, assignments, notifications, and SLA tracking.
- Preview public help center pages and try article search.
- Check integrations (CRM sync, Slack alerts).
10. Launch and iterate
- Announce launch to customers and update contact info on your site.
- Monitor key metrics daily for the first two weeks: response time, resolution rate, ticket volume.
- Collect agent feedback and adjust workflows, macros, and KB content.
- Plan recurring reviews: weekly for month one, then monthly.
Quick checklist (summary table)
| Item | Done |
|---|---|
| Admin account & domain verification | ☐ |
| Branding and business hours | ☐ |
| Teams, roles, and users added | ☐ |
| Channels & integrations connected | ☐ |
| Top KB articles published | ☐ |
| Workflows, SLAs, and automations set | ☐ |
| Agent training completed | ☐ |
| End-to-end testing completed | ☐ |
| Public launch announced | ☐ |
Follow these steps and you’ll have a structured, scalable HelpBuilder setup that keeps tickets moving and knowledge organized.
Leave a Reply