Glossary
Understand Wemblo terms for workspaces, Smart Inbox, WABA, Phone Number ID, API keys, webhooks, AI actions, social publications, and handover.
Overview
Workspace: Separated business environment.
Smart Inbox: Unified conversation workspace. All is the default combined view.
WABA: WhatsApp Business Account.
Phone Number ID: Meta API identifier for a WhatsApp Business number.
Access Token: Secret authorizing provider API calls.
Verify Token: Value used during a webhook verification handshake.
Webhook: HTTPS event notification.
API Key: Secret used by an external system to call the Wemblo API.
AI Action: Metered AI operation.
Social Publication: One successful post to one selected destination.
Segment: Saved contact audience.
Custom Field: Business-specific structured contact value.
Human Handover: Transfer from automation or AI to an authorized person.
Idempotency: Prevents duplicate processing of a request or event.
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. |
Step-by-step instructions
- Open Wemblo -> Help or the affected module.
- Identify the affected area.
- Record the time in PKT and exact error.
- Check account, workspace, permission, connection and limits.
- Reproduce with fictional data.
- Review the relevant detailed guide.
- Contact Support with redacted evidence if unresolved.
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: