Use the Website Chat Widget
Configure a website conversation button with the correct destination, greeting, appearance, and prefilled message.
STEPS
- Select the connected destination channel and number.
- Configure button position, color, logo, heading, body, and call to action.
- Add an approved prefilled message.
- Generate the script.
- Add it to the website through the approved implementation method.
- Test desktop, mobile, accessibility, and page performance.
Who should use it
Workspace owners, operations teams, sales users and authorized technical users.
Where to find it in Wemblo
Wemblo -> Tools
Before you begin
- Use the correct workspace and authorized role.
- Prepare fictional Pakistan test data.
- Confirm connected provider accounts where required.
- Define who approves price, stock, booking, payment or final status.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Destination | Connected channel or number. |
| Greeting / Prefilled Text | Optional opening context. |
| Placement | Website or printed location. |
| Source Tracking | Identifies where the conversation started. |
| Test | Verification on a separate device. |
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 |
|---|---|
| Configuration does not save | Required fields, validation, permission and active workspace. |
| External action fails | Credential, provider status, endpoint or field mapping. |
| Duplicate record or action | Event ID, idempotency, retries and existing record. |
| Customer notification is missing | Template, channel connection, status transition and contact details. |
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: