Help & Troubleshooting Home
Diagnose Wemblo account, channel, inbox, AI, campaign, business-tool, mobile, developer, billing, and add-on issues.
Overview
Troubleshooting, safe support requests, glossary, frequently asked questions, and workspace launch review
Chapter purpose
This chapter helps Wemblo users diagnose common user-side problems, collect safe evidence, understand important terminology, and complete a controlled launch checklist.
Chapter contents
- Help and Troubleshooting Home
- Channel Connection Troubleshooting
- Smart Inbox and Message Troubleshooting
- AI and Automation Troubleshooting
- AI Call Assistant Troubleshooting
- Campaign and Publishing Troubleshooting
- Forms, Appointments, Orders, and Payment Troubleshooting
- Mobile App Troubleshooting
- API and Webhook Troubleshooting
- Billing and Add-on Troubleshooting
- Safe Support Request Checklist
- Glossary
- Frequently Asked Questions
- Workspace Launch Checklist
TROUBLESHOOTING METHOD
- Identify the workspace, user, channel, feature, and provider.
- Record the approximate time in Pakistan Standard Time.
- Determine whether the issue affects one user, one workspace, one channel, or all activity.
- Reproduce it with fictional data.
- Check the user's role, active plan, usage, integration status, and recent changes.
- Review Wemblo and provider logs where available.
- Capture a redacted screenshot and error message.
- Open the most specific guide below or contact Support.
Never send passwords, permanent tokens, API keys, app secrets, webhook secrets, payment-card details, database credentials, or unnecessary private customer data.
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: