Complete your first launch checklist
Use a practical prelaunch checklist for Agent content, product data, support, deployment, permissions, and customer testing.
Coordinate the final checks for a first Humind launch. The checklist connects configuration areas so a working preview is not mistaken for a complete customer experience.
Humind separates preparation from customer-facing delivery. Work in the B2B workspace can change an Agent, Knowledge, catalog, Inbox, or Helpdesk without immediately changing every live surface. Understanding that separation helps you test deliberately, involve the right teammate, and avoid treating a saved draft as a completed launch.
Before you begin
Access: An administrator should coordinate the launch. Area owners can validate their own permissions and settings.
- Choose the Agent and target sales channel.
- Name an owner for Knowledge, catalog, support, and deployment.
- Prepare representative customer questions and products.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Validate sources and Agent behavior
Review guidance, published Knowledge, catalog readiness, and optional tools. Run Playground and product tests against common, difficult, and unsupported questions.
- Confirm answers use current business information.
- Record unsupported cases and the intended safe response.
Prepare the human support path
Confirm escalation behavior, Inbox access, operator availability, tickets, and saved replies. A customer should never be sent to a team that cannot see or own the conversation.
- Run one escalation from customer request to operator takeover.
- Verify the operator can resolve or return the conversation to AI.
Review channel and security settings
Check allowed domains, interface presentation, teammates, roles, and personal access. Remove no one during this review unless the company owner has approved the access change.
- Verify each launch operator can sign in.
- Confirm the production domain is explicitly allowed.
Deploy and observe the real experience
Install one embed on the target channel and test desktop and mobile. After launch, review conversations and analytics to prioritize corrections based on evidence.
- Use a private window to avoid administrator session effects.
- Save the tested URL, time, and scenario in the launch record.
Important limits and operating notes
- Do not use customer personal data in prelaunch tests.
- A Helpdesk and an Agent are separate public surfaces with separate publication or deployment steps.
- Some analytics views need live activity before they become useful.
- Unavailable integrations should remain outside the launch promise.
Verify the result
- Core questions, products, and escalation pass in the workspace.
- The real domain loads exactly one working entry point.
- A teammate with the intended role can complete their task.
- The launch owner has a short issue list with owners and priorities.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
The workspace test passes but the website fails
Inspect deployment, allowed domains, duplicate embeds, and the exact Agent used by the sales channel. Retest in a private window after correcting only the failing layer.
The team cannot agree that launch is ready
Classify each open item as blocking, monitored, or later. Require a blocking issue to name the affected customer journey and failed verification rather than relying on a general concern.