Business Tools Overview
Use Wemblo forms, appointments, catalogs, orders, widgets, QR links, business events, external systems, and payment workflows.
Overview
Forms, appointments, calendars, catalogs, orders, widgets, business events, external systems, and customer payment integrations
Chapter purpose
This chapter explains the user-side business tools that convert conversations into structured forms, bookings, products, orders, events, and verified customer payments.
Chapter contents
- Business Tools Overview
- Create and Publish Forms
- Configure Appointment Booking
- Manage Availability, Reminders, Rescheduling, and Cancellation
- Connect Appointments with Google Calendar and Meet
- Configure Appointment Payments
- Connect and Manage Product Catalogs
- Manage Orders and Status Notifications
- Use the Website Chat Widget
- Generate Direct Chat Links and QR Codes
- Send Business Events to Wemblo
- Connect External Business Systems
- Customer Payment Integration Overview
- Connect a Supported Payment Gateway
- Obtain Provider Keys and Webhook Secrets
- Configure Payment Webhooks
- Use Payments with Appointments and Orders
- Review Payment Transactions
- Test Payments Safely
- Troubleshoot Payment Status and Webhooks
Wemblo business tools connect customer conversations with structured data and operational actions. Use only the modules required for a real business workflow and confirm final price, stock, availability, payment, refund, delivery, or approval through an authorized person or connected source.
Who should use it
Workspace owners, operations teams, sales users and authorized technical users.
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 |
|---|---|
| Business Tool | Module connecting conversations to operations. |
| Owner | User responsible for the workflow. |
| Integration | Connected external system. |
| Verification | Test proving the workflow works. |
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: