How to Set Up HelpBuilder: Step-by-Step Onboarding Guide

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

  1. Sign up at HelpBuilder’s signup page with your admin email.
  2. Verify your email and complete basic company details (name, timezone, language).
  3. Add and verify your support domain or help center URL (DNS TXT or CNAME as required).

3. Configure company settings

  1. Upload logo and set brand colors under Appearance.
  2. Set default timezone, business hours, and holiday schedule.
  3. Configure support email address ([email protected]) and reply-to settings.
  4. Set security options: enforce SSO (if available), password policy, and 2FA for admins.

4. Set up teams, roles, and permissions

  1. Create teams (e.g., Tier 1, Tier 2, Billing, Product).
  2. Define roles: Admin, Manager, Agent, and Contributor.
  3. Assign permissions at team and role level (ticket visibility, KB editing, analytics access).
  4. Add users by email and assign them to teams and roles. Send invites.

5. Connect channels and integrations

  1. Email: configure inbound routing so support@ emails create tickets.
  2. Live chat: install chat widget snippet on your site and customize greetings.
  3. Social and messaging: connect Facebook, Twitter, WhatsApp if needed.
  4. Integrations: link Slack for notifications, CRM for contact sync, and analytics tools.

6. Build your knowledge base

  1. Import existing content via CSV, Markdown, or direct copy-paste.
  2. Create categories (Getting Started, Billing, Troubleshooting).
  3. Write or refine top 10 articles first: concise titles, clear steps, screenshots.
  4. Create reusable macros/canned replies for common ticket types.
  5. Set article visibility (internal vs public) and SEO metadata for public articles.

7. Configure ticket workflows and automation

  1. Create ticket pipelines: New → Triaged → In Progress → Resolved → Closed.
  2. Set SLA rules for response and resolution times by priority.
  3. Add automations:
    • Auto-assign by keyword or team workload.
    • Auto-acknowledgement emails on ticket creation.
    • Escalation rules for missed SLAs.
  4. Create tags and custom fields for reporting (product, severity, region).

8. Onboard agents

  1. Provide a short onboarding checklist: login, set status, handle a test ticket.
  2. Run a 30–60 minute training session covering:
    • Ticket triage and response standards.
    • Using KB articles and attaching macros.
    • Escalation and SLA expectations.
  3. Assign each new agent a mentor for the first week.
  4. Monitor initial tickets and give feedback.

9. Test everything before going live

  1. Submit test tickets via email, chat, and web form.
  2. Verify automations, assignments, notifications, and SLA tracking.
  3. Preview public help center pages and try article search.
  4. Check integrations (CRM sync, Slack alerts).

10. Launch and iterate

  1. Announce launch to customers and update contact info on your site.
  2. Monitor key metrics daily for the first two weeks: response time, resolution rate, ticket volume.
  3. Collect agent feedback and adjust workflows, macros, and KB content.
  4. 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.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *