Workspace Launch Checklist
Verify profile, roles, channels, Smart Inbox, contacts, AI, calls, automation, campaigns, mobile, APIs, billing, security, and support before launch.
CHECKLIST
- Business profile, Pakistan timezone, and public contact details are correct.
- Workspace owner, teams, users, and least-privilege permissions are tested.
- One connected channel passes inbound and outbound tests.
- Smart Inbox All and channel tabs work.
- Contacts, tags, fields, pipeline, tasks, and follow-up are ready.
- AI provider, knowledge, boundaries, multilingual tests, and handover are approved.
- AI Call Assistant disclosure, incoming or outgoing test, actions, recording, transcript, and transfer are reviewed where used.
- Automation triggers, branches, fields, fallback, logs, and handover are tested.
- Campaign consent, templates, audiences, opt-out, social allowances, and reply ownership are ready.
- Forms, appointments, Google, catalogs, orders, and customer payments are tested where used.
- Mobile access and notifications are tested.
- API keys and webhooks use HTTPS, least privilege, verification, retries, and idempotency.
- Plan, add-ons, provider costs, billing, export, preferences, and deletion routes are understood.
- Support ownership and escalation are defined.
- A small controlled pilot is approved before full launch.
Who should use it
All Wemblo users and authorized support contacts.
Where to find it in Wemblo
Wemblo -> Help or the affected module
Before you begin
- Record the workspace, user, module and time in PKT.
- Reproduce the issue with fictional data where possible.
- Collect a redacted error message or screenshot.
- Never include passwords, API keys, tokens or private customer data.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Issue Scope | One user, workspace, channel or service-wide. |
| Reproduction | Steps that consistently cause the problem. |
| Error Code | Provider or Wemblo reference. |
| Redaction | Removal of secrets and private data. |
| Support Evidence | Safe screenshot, timestamp and expected result. |
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Issue cannot be reproduced | Confirm workspace, user, time, environment and exact steps. |
| No useful error is available | Review logs, provider dashboard and status. |
| Support cannot investigate | Provide redacted evidence, expected result and affected record. |
| Sensitive data was attached | Remove it, rotate exposed credentials and resubmit safely. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: