Integrate Google Calendar with a WhatsApp agent

Google Calendar + WhatsApp integration matters when the agent must offer real slots (demos, visits, consults) without “does Tuesday work?” ping-pong. In practice: the agent proposes slots, confirms, and creates the event (or leaves a hold for a human). This page covers the config pattern and timezone/opt-in caveats. In 42agents you deploy it white-label on Cloud API + coexistence; signup is available in the dashboard, with a 7-day trial.

When it makes sense

• The ad CTA is “book a call/visit,” not only “ask for info.”
• There is a shared sales team calendar (not the owner’s personal calendar mixed in).
• Slots are predictable (15/30/60 min blocks) with buffers between meetings.
• Humans can move meetings in Calendar without the agent double-booking.

Configuration and prompts

1) Dedicated Calendar: sales@[client] or shared team calendar.
2) Single documented timezone (e.g. America/Mexico_City).
3) Business hours + exceptions (holidays).
4) Default duration + buffer (e.g. 30 min + 10 min).
5) Event fields: name, WhatsApp phone, source (ad/web).
6) WhatsApp confirmation + optional reminder (Meta template if outside the window).
7) Cancel/reschedule policy in the prompt.

When the lead wants to book:
1) Ask city/zone only if it affects TZ.
2) Offer 2–3 real calendar slots (do not invent).
3) On confirm, create the event and reply with clear date/time.
4) If no capacity in 7 days, offer waitlist or handoff.
5) If the lead switches to complex pricing, pause booking and escalate.

- Wrong TZ → meetings shifted 1–3 hours.
- Founder’s personal Calendar → conflicts and privacy issues.
- Confirm without creating the event → phantom bookings.
- Reminders without template/opt-in outside the 24h window.

Deploy in 42agents

Sign up at https://dashboard.42agents.app/sign-up, connect Cloud API with coexistence, link the client’s Calendar, and test end-to-end (lead → slot → event). Plans from USD 39/account/mo. 7-day trial.