approve_contact_change
ChatGPTApplies a pending contact delivery-field change after the person confirms the review summary or preview page.
approve_ecard
ChatGPTPuts an approved draft on the calendar. Before draft_ecard, show the person the subject and message as they will appear on the card (use line breaks in chat so the formatted layout is visible), say they can change wording before you proceed, and call draft_ecard only after they clearly approve that text. After draft_ecard, the card preview panel shows the still or looping video when the host supports it; share previewUrl and animationPreviewUrl as links. Do not use markdown image syntax for imageUrl on hosts that block Scheduled Smiles media URLs (broken gray tiles in ChatGPT). call approve_ecard only after they explicitly confirm putting the card on the calendar—a soft yes is not approval.
approve_order
ChatGPTPlaces a drafted flower or mailed-card order after an explicit yes to the server-built summary. Explicit yes only. When chatApprovalAllowed is false on the draft, send the review link instead; approve_order returns page_approval_required with the same link.
cancel_ecard
ChatGPTCancels a pending e-card that was scheduled through the agent.
cancel_flower_order
ChatGPTCancels a pending flower pre-order that was placed on the calendar after approve_order. Use scheduledItemId from read_scheduled_items. reject_order only applies before approval.
cancel_gift_order
ChatGPTCancels a gift order on the calendar, including placed gifts when Goody still allows cancel. Use scheduledItemId from read_scheduled_items.
cancel_mailed_card_order
ChatGPTCancels a pending mailed-card pre-order that was placed on the calendar after approve_order. Use scheduledItemId from read_scheduled_items.
check_flower_delivery_availability
ChatGPTFlower delivery only. Use when the user asks if they can still order or schedule flowers for a holiday or date. Do not use get_order_deadlines for flower bookability or a 'last day to order'. Requires a delivery postal code: use postalCode from the user, or contactRef/contactId when signed in (contacts.read). If ZIP is not known, read_contacts or resolve_contact first when connected, otherwise ask for the recipient ZIP. Do not guess a ZIP. Pass occasionName (e.g. Mother's Day (US)), occasionSlug (EVT-NNN), or deliveryDate.
check_payment_readiness
ChatGPTReturns whether a card is on file. When it is not, returns the signed-in Scheduled Smiles path to add one. Never asks for or returns a card number.
create_contact
ChatGPTCreates a contact with name, relationship, preferred tone, and optional email, phone, preferences, notes, birthday (yyyy-MM-dd calendar date), and mailing address. preferredTone is required: use get_contact_field_options for allowed values. If the person did not choose tone (or did not confirm an inferred relationship), you may assume a reasonable value to call this tool, but you must disclose the assumed value and ask them in the same turn to confirm or pick another; use update_contact if they want a change. When Azure Maps corrects an address, call again with addressVerificationChoice Suggested or AsEntered. Read reviewSummary verbatim for voice confirmation. Use missingOptionalFields to interview for remaining optional fields in batch.
describe_capabilities
ChatGPTLists tool names, which of e-cards, mailed cards, and flowers are available, and the rate limit. Use when no other published tool fits. Price and account-access questions belong to get_pricing_and_access. For unavailable chat capabilities, point to the Scheduled Smiles website without promising a date or review timeline.
draft_ecard
ChatGPTCreates a pending e-card draft, or replaces the contents of an existing unapproved draft for the same contact and occasion, after the person accepted the subject and formatted message in chat. Pass catalogItemId from search_catalog or suggest_ecard_templates (template slug). Format draft_ecard message like a greeting card body (not one run-on sentence): greeting with the recipient's name, then a newline, then the main wish on the next line(s); when the person gives a sign-off (e.g. Dad, Love Mom), put a blank line before it on its own last line. Use newline characters in the message string; preserve the person's words—only add line breaks for layout. Before draft_ecard, show the person the subject and message as they will appear on the card (use line breaks in chat so the formatted layout is visible), say they can change wording before you proceed, and call draft_ecard only after they clearly approve that text. After draft_ecard, the card preview panel shows the still or looping video when the host supports it; share previewUrl and animationPreviewUrl as links. Do not use markdown image syntax for imageUrl on hosts that block Scheduled Smiles media URLs (broken gray tiles in ChatGPT). call approve_ecard only after they explicitly confirm putting the card on the calendar—a soft yes is not approval. Returns previewUrl, animationPreviewUrl, imageUrl (a still picture to embed inline), and optional shareableMediaUrl; scheduling still requires approve_ecard or the preview page.
draft_flower_order
ChatGPTDrafts a flower order and returns the review link and the summary to read aloud. Pass catalogItemId from search_catalog results[].id (flower public id). occasionSlug is EVT-NNN from get_order_deadlines or search occasions. Update the same draft sequentially with intentId and draftVersion, not in parallel. Nothing is placed until approve_order or the review page. Explicit yes only; 'sounds good' is not a yes. maxTotalUsd can only lower the limit for this draft.
draft_mailed_card_order
ChatGPTDrafts a mailed-card order and returns the review link and the summary to read aloud. Pass catalogItemId from search_catalog results[].id (mailed-card slug). occasionSlug is EVT-NNN from get_order_deadlines or search occasions. Update the same draft sequentially with intentId and draftVersion, not in parallel. Nothing is placed until approve_order or the review page. Explicit yes only. maxTotalUsd can only lower the limit for this draft.
get_contact_field_options
ChatGPTLists allowed relationship, tone, media, and visual-style values and the order to offer optional fields in batch. Use preferredTones when asking the person to confirm or change an assumed tone on create_contact.
get_ecard_writing_context
ChatGPTReturns user-provided writing context plus tone, length limits, and example phrases to avoid. The assistant writes the card; this tool does not call Scheduled Smiles AI. Use tone, subjectMinChars/subjectMaxChars, messageMinChars/messageMaxChars, and phrasesToAvoidExamples from get_ecard_writing_context when drafting subject and message in chat. phrasesToAvoidExamples are non-exhaustive occasion hints, not a complete filter. When relationshipGuidance is present it is an admin-written default hint for this kind of relationship; follow it unless the person's own aiInstructions, occasionGuidance, or notes say otherwise. Format draft_ecard message like a greeting card body (not one run-on sentence): greeting with the recipient's name, then a newline, then the main wish on the next line(s); when the person gives a sign-off (e.g. Dad, Love Mom), put a blank line before it on its own last line. Use newline characters in the message string; preserve the person's words—only add line breaks for layout. Before draft_ecard, show the person the subject and message as they will appear on the card (use line breaks in chat so the formatted layout is visible), say they can change wording before you proceed, and call draft_ecard only after they clearly approve that text. After draft_ecard, the card preview panel shows the still or looping video when the host supports it; share previewUrl and animationPreviewUrl as links. Do not use markdown image syntax for imageUrl on hosts that block Scheduled Smiles media URLs (broken gray tiles in ChatGPT). call approve_ecard only after they explicitly confirm putting the card on the calendar—a soft yes is not approval.
get_order_deadlines
ChatGPTLists shop occasions with next occurrence dates and mailed-card order-by deadlines. For whether flower delivery on a holiday is still bookable for a ZIP, use check_flower_delivery_availability instead. occasionSlug is an EVT-NNN id for filters and drafts, not a holiday name alone.
get_pricing_and_access
ChatGPTExplains what ordering requires and, when the caller is signed in, which features their own account has. Example: whether a subscription is required to send flowers (it is not). Prices are the prices this caller pays today, from the payload. When a feature is not available on this account, say so plainly and point to informationUrl. Do not list subscription options, compare them, or suggest a change. Do not state assistant spend-cap amounts.
read_contacts
ChatGPTScenario 67 (relationship match, e.g. get me flowers for my mom): reads contacts on the signed-in account. Returns full contact fields for the assistant (names, contactRef, tone, email, phone, address, preferences, custom dates, missingOptionalFields, contactDetailUrl)—you need not read every field aloud to the user. Includes a locked-contact field when the subscription lapsed (not the free-plan add limit). Map the person's words to the stored Persona relationship name (Mother, not mom). Brother-in-law is not Brother. Contacts with no relationship stored do not match a filter. One relationship match returns that contact. Several matches return all matches; ask which one by display name and do not guess. Two matches with the same display name: ask using whatever else the result allows and do not invent a difference. None means no contact on this account has that relationship recorded. Ordering and payment are unavailable; send no checkout link.
read_personal_occasions
ChatGPTScenario 68 (when is my mom's birthday): reads upcoming personal occasion dates on the signed-in account. Each row includes display name, stored relationship, occasion name, and next calendar date. Use the relationship argument for birthday-by-relationship questions: map the person's words to the stored Persona name (Mother, not mom). Brother-in-law is not Brother. A contact with no relationship stored does not match. One Mother with a birthday returns that Birthday row. Two Brothers with birthdays return both rows; ask which one by display name and do not guess. When a relationship filter returns no rows, or returns rows but none with occasionName Birthday, say there is no birthday recorded for that relationship on this account. Includes dates without a scheduled smile and dates beyond 30 days. A successful read does not schedule anything and must not claim a smile was scheduled. A locked contact's row carries the same subscription-lapse sentence as the contact tool (not the free-plan add limit). Ordering and payment are unavailable; send no checkout link.
read_scheduled_items
ChatGPTScenarios 69 and 70 (what is scheduled, what is scheduled for my mom, how many in December): reads smiles already on the signed-in account's calendar: e-cards, flowers, mailed cards, and any other service. This reports smiles that already exist; it does not schedule anything, and a successful read must not be described as this chat scheduling a smile. Answer how-many questions from totalCount, not by counting items. When moreOnWebsite is true, say the full list is on the Scheduled page in the Scheduled Smiles app. scheduledDate is the date the customer picked (e-card send date, flower delivery date, mailed-card requested arrival). A mailed-card date schedules printing and dispatch; postal delivery is not promised. Use vendorPlacementDate only when asked when the order was placed with the florist or printer. Quote status as returned. A flower or mailed card whose status says it was charged is already with the vendor; do not offer to cancel it here. For relationship questions map the person's words to the stored Persona name (Mother, not mom); Brother-in-law is not Brother. When noContactWithRelationship is true, say there is no contact with that relationship. When matchedDisplayNames has one name and items is empty, say nothing is scheduled for that person. Several names: ask which one by display name and do not guess or pick the first; two identical names: ask using whatever else the result allows and do not invent a difference. A locked contact's row carries the same subscription-lapse sentence as the contact tool (not the free-plan add limit). Each row includes scheduledItemId for follow-up agent writes on that smile (for example update_scheduled_ecard, cancel_ecard, send_scheduled_ecard, cancel_flower_order, update_scheduled_flower_order, cancel_mailed_card_order, or update_scheduled_mailed_card_order). Agent-scheduled e-card rows may include previewUrl (read-only after approval; share when the person asks to see the card). Ordering, cancelling, and payment are unavailable here except via the dedicated write tools; send no checkout link.
refresh_ecard_preview
ChatGPTIssues a fresh preview link for the same open draft when the previous link expired. Returns the same preview fields as draft_ecard, including animationPreviewUrl and imageUrl.
reject_ecard
ChatGPTRejects an open e-card draft.
reject_order
ChatGPTRejects an open flower or mailed-card draft. Nothing is placed.
resend_ecard
ChatGPTResends a sent or failed e-card immediately using the same card view link as the original delivery.
resolve_contact
ChatGPTFinds contacts on the signed-in account by display name and/or stored relationship. Never guesses when several match. Returns the same full contact row as read_contacts (including address and email for the assistant; not every field must be spoken aloud). contactRef tokens are for write tools, never raw ids.
search_catalog
ChatGPTSearches e-cards, mailed cards, and flowers with optional occasion, price, text, and e-card tone filters. Tone and visual style are not text-search filters—use suggest_ecard_templates when recommending e-cards for a contact. Each result id is the catalogItemId for draft and update tools (template slug, mailed-card slug, or flower public id). occasionSlug filter uses EVT-NNN from get_order_deadlines, not a holiday name. Required when the person wants to see or choose catalog items; pictures appear in the card preview panel automatically when results are non-empty. Tell the person to use that panel rather than pasting result image or link values into chat. Set service (for example ecard) and pageSize when they ask for a specific count. Example: service=flowers, maxPriceUsd=60.
send_scheduled_ecard
ChatGPTScenario 73 (send Julian's scheduled birthday e-card now): delivers an existing pending or failed e-card by scheduledItemId using the same rules as portal Send now. Call only after an explicit send-now request. Use read_scheduled_items first (relationship and optional dates; no display-name filter) to obtain scheduledItemId; when multiple rows match one person, ask which by display name and occasion—do not guess. Not for already-sent cards (use resend_ecard). On success describe the outcome as sent or delivered, not as scheduling a new smile. Failed cards may be retried after SMTP failure.
set_auto_send
ChatGPTEnables recurring Auto Send for e-cards on a contact and occasion. A future scheduler may deliver the e-card to the external recipient automatically each year; this invocation changes enrollment but does not send immediately.
show_catalog_preview
ChatGPTShows catalog pictures in the card preview panel for specific catalogItemId values. Use when you need to refresh the panel for ids without running search_catalog again. search_catalog and suggest_ecard_templates already show the preview panel when they return results. Pass at most 12 catalogItemId values. Ids that are not in the public catalog are skipped.
suggest_ecard_templates
ChatGPTReturns ranked e-card templates for a contact and occasion using the same scoring as Auto Send. Use this—not search_catalog text queries—when the person asks for style-matched e-card picks. Optional toneHint overrides the contact stored preferred tone for this call only (never saved). When the approved message used a tone from get_ecard_writing_context, pass the same toneHint. Unsupported toneHint returns allowedValues from get_contact_field_options; pick the closest tone and retry. Optional limit defaults to 3 (max 5). Each template includes catalogItemId for draft_ecard; pictures appear in the card preview panel when templates are returned.
update_contact
ChatGPTUpdates a contact. Supports email, phone, preferences, and a complete mailing address with Azure Maps verification. Omit birthday to leave it unchanged; null is treated as omitted; pass "" to clear (same as the website). Read reviewSummary verbatim for voice confirmation. Paid flowers, mailed cards, or paid Auto Send may return pendingContactChange with a preview URL.
update_scheduled_ecard
ChatGPTUpdates subject and/or message on a pending agent-scheduled e-card. Does not change the preview link token. Provide scheduledItemId from read_scheduled_items or approve_ecard.
update_scheduled_flower_order
ChatGPTUpdates a pending flower pre-order after approve_order. Provide scheduledItemId from read_scheduled_items and at least one of catalogItemId (search_catalog flowers id), deliveryDate, cardMessage, or deliveryNote. If the quoted total changes, use full re-approval per Scenario 72 (review link and explicit approve_order); do not rely on acceptPriceChange in chat.
update_scheduled_mailed_card_order
ChatGPTUpdates a pending mailed-card pre-order after approve_order. Provide scheduledItemId from read_scheduled_items and at least one of message, requestedArrival (yyyy-MM-dd), catalogItemId (search_catalog mailedCards id), or giftCardAmountUsd.