Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nedzo.ai/llms.txt

Use this file to discover all available pages before exploring further.

When you connect a calendar action to an agent, we add a default block of booking instructions to your agent’s prompt. The agent uses these to ask for a timezone, present a couple of slots at a time, and collect the contact’s name and email only after they’ve picked a time. You can edit these instructions directly in the prompt editor. They are part of your agent’s prompt — they are not hidden from you and they are not enforced by the platform. Tune them, replace them, or remove them entirely.

​
The default block

Copy this into your agent’s prompt if you ever need to restore the defaults. 
OPERATIONAL RULES:
1) Conversation Memory (CRITICAL): If the user's timezone, name, or email has already been provided earlier in this conversation, remember and reuse that information. NEVER re-ask for information already collected.
2) Timezones (REQUIRED FIRST): Before checking availability, ask the user for their timezone only if it has not been provided yet in this conversation. Always convert tool outputs to the user's local time when speaking.
3) Identity Verification (ONLY WHEN BOOKING): Only ask for Full Name and Email when the user has selected a slot and is ready to book. If name and email were already collected earlier in the conversation, skip this step and proceed directly to booking. Do NOT ask for name/email before showing availability.
4) Presenting Availability: Offer a maximum of two slots at a time. Use relative dates (e.g., "Tomorrow," "This Thursday"). Speak naturally, no bullet lists.

BOOKING WORKFLOW:
1) Get Timezone only if not already known from this conversation
2) Check Availability with fetch_slots
3) Offer Slots (max 2 at a time)
4) Collect Contact Info only AFTER slot selection — if already known, confirm: "I'll book this under [name], [email] — shall I go ahead?"
5) Finalize with book

​
Why each rule exists

  • Conversation Memory — Without this, agents re-ask for timezone or email after every tool call, which feels broken to the contact.
  • Timezones first — Booking against the wrong timezone produces calendar invites the contact never sees. Asking up front is cheaper than apologizing later.
  • Identity only at booking — Asking for name/email before showing availability comes across as gating. Asking after a slot is selected feels like a normal confirmation step.
  • Two slots at a time — Voice channels can’t read a list of ten options. Even on chat, two options at a time keeps the back-and-forth fast.
  • Booking workflow ordering — Codifies the sequence so the agent doesn’t try to book before checking availability.

​
Customizing

You can edit any of these freely. Common tweaks:
  • Offer more or fewer slots — change “two slots” to “three slots” if you want a wider menu, or “one slot” for a more directive feel.
  • Change the language — these instructions affect tone. If your brand is formal, rewrite them as full sentences in that voice; the model will mirror it.
  • Add booking-window rules — e.g. “never offer slots within the next 4 hours” or “only weekday afternoons”.
  • Remove identity verification — if you already authenticated the contact (e.g. logged-in web chat), skip the name/email confirmation by deleting rule 3.

​
Calendar timezone

Each calendar action has an optional Timezone field (IANA, e.g. America/New_York). When set, the agent will not ask the contact for a timezone — it will book against the calendar’s timezone instead. Leave it blank if your contacts span multiple timezones and the agent should always ask.

​
Tool wiring (handled automatically)

You don’t need to add the tool names (fetch_slots, book, cancel, reschedule) or the calendar provider/ID to your prompt. Those are still injected automatically when you attach a calendar action — only the operational rules above live in your editable prompt.