Configure Appointment Booking
Create appointment services with PKT availability, duration, questions, reminders, payments, Google Calendar, and Meet.
MAIN CONCEPTS
| Service | Bookable offering. |
|---|---|
| Timezone | Use Pakistan Standard Time for Pakistan operations. |
| Duration | Length of the booking. |
| Availability | Working days and slots. |
| Buffer | Reserved time around bookings. |
| Questionnaire | Information collected before confirmation. |
STEPS
- Create the appointment configuration.
- Add name, description, location, PKT timezone, and duration.
- Set daily limit, advance booking, overlap, and buffer rules.
- Configure availability and multiple intervals.
- Add customer questions.
- Choose confirmation, reminder, reschedule, and cancellation messages.
- Connect Google and payments where required.
- Test booking, update, reschedule, cancellation, and no-availability cases.
Who should use it
Workspace owners, operations teams, sales users and authorized technical users.
Where to find it in Wemblo
Wemblo -> Automations -> Appointment Booking
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.
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: