bTaskee

Third and final step of the deep cleaning ("tổng vệ sinh") flow. Creates a REAL, paid booking against bTaskee's backend using the exact date/area/address already quoted by quote_deep_cleaning — a real side effect (not idempotent: two calls make two bookings). INSTRUCTIONS: REQUIRED STEP 3/3 for deep cleaning bookings. Flow: verify_address -> quote_deep_cleaning -> book_deep_cleaning. Call this tool as your literal next tool call the moment the customer confirms the quoted price ("đặt", "đặt đi", "ok", "chốt") — before doing anything else. Required arguments: reuse EXACTLY what quote_deep_cleaning already used — date, area, address. Do not re-derive or re-ask any of them, and do not pass a price: the confirmation card's price is calculated by this server. If the customer changes one after quoting, call quote_deep_cleaning again first, then book_deep_cleaning with the new quote. Protocol: 1. Call this tool immediately after the customer's explicit price confirmation. 2. When the client renders the confirmation card, do not repeat service/time/address/price as text — just confirm the booking is set and mention a Tasker will take it on soon, phrased around the Tasker themselves accepting the job (e.g. "Tasker sẽ nhận việc của bạn") — never as bTaskee creating the booking or a Tasker being "assigned" in a passive, institutional voice. 3. When the client does not support the card, state the outcome yourself: confirm the booking and repeat service/time/address/price so the customer has a record. 4. `status: "verify"` means no booking was created: the customer's bTaskee account isn't phone-linked yet. Follow its `message` exactly. This is temporary, not a dead end — once they say they're done linking, call this tool again with the same arguments. 5. When the result has `success: false`, no card is shown. Follow its `assistant_instruction` exactly. If that instruction contains a markdown link (for example the bTaskee account-link link), put that link in your reply unchanged — the customer cannot continue without it. RESTRICTIONS: - Never tell the customer booking failed or isn't possible unless this tool actually returned `success: false` — then relay that `error` verbatim. - Never drop, shorten, or paraphrase a link given in `assistant_instruction`. - Never claim a booking exists without having called this tool. - Do not ask for payment method — bTaskee handles payment outside this chat. - Never expose internal field names or codes to the customer; use plain language.

book_deep_cleaning

Third and final step of the home cleaning flow. Creates a REAL, paid booking against bTaskee's backend using the exact date/duration/address/extras already quoted by quote_home_cleaning — a real side effect (not idempotent: two calls make two bookings). INSTRUCTIONS: REQUIRED STEP 3/3 for home cleaning bookings. Flow: verify_address -> quote_home_cleaning -> book_home_cleaning. Call this tool as your literal next tool call the moment the customer confirms the quoted price ("đặt", "đặt đi", "ok", "chốt") — before doing anything else. Required arguments: reuse EXACTLY what quote_home_cleaning already used — date, duration, address, is_premium, auto_choose_tasker, requirements, pet. Do not re-derive or re-ask any of them, and do not pass a price: the confirmation card's price is calculated by this server. If the customer changes one after quoting, call quote_home_cleaning again first, then book_home_cleaning with the new quote. Protocol: 1. Call this tool immediately after the customer's explicit price confirmation. 2. `status: "booked"` — a real booking was created. When the client renders the confirmation card, do not repeat service/time/address/price as text — just confirm the booking is set and mention a Tasker will take it on soon, phrased around the Tasker themselves accepting the job (e.g. "Tasker sẽ nhận việc của bạn") — never as bTaskee creating the booking or a Tasker being "assigned" in a passive, institutional voice. 3. `status: "verify"` — the customer's bTaskee account isn't phone-linked yet and this is their FIRST attempt today, so NO booking was created. Instead a minimal card with a single "link your account" button is shown (no task detail). Do not say the booking is confirmed; tell them to tap the button, link with phone + OTP, then confirm the booking again once done. Do not also spell the link out as text when the card is shown. 4. `status: "review"` — the customer's bTaskee account is STILL not phone-linked after already being shown `status: "verify"` once today. Instead a card with the same service/time/address/price and a deeplink+QR into the app's confirm-and-pay screen is shown. Do not say the booking is confirmed; tell the customer to tap the button (or scan the QR) to review and confirm/pay themselves. Then, as a separate note in the same reply, also give them the account-link markdown link from `message` unchanged (`link_url` carries the bare URL) — an optional second path so they can book straight from this chat next time. 5. `status: "verify"`/`"review"` are TEMPORARY, NOT a dead end: if the customer later says anything indicating they're done ("xong", "done", "rồi", "đặt đi", "ok"), do not assume success — call book_home_cleaning again with the EXACT SAME arguments as your literal next tool call and follow whatever THAT new result says. `status: "booked"` means their account got linked and this call just made the real booking. 6. When the client does not support the card (`assistant_instruction`/`message` says so), state the outcome yourself: repeat service/time/address/price so the customer has a record (`status: "verify"` has none to repeat), and give any deeplink/account-link URL as a real, unchanged link. 7. When the result has `success: false`, no card is shown. Follow its `assistant_instruction` exactly. If that instruction contains a markdown link, put that link in your reply unchanged — the customer cannot continue without it. RESTRICTIONS: - Never tell the customer booking failed or isn't possible unless this tool actually returned `success: false` — then relay that `error` verbatim. - Never claim a booking exists (`status: "booked"`) when the result says otherwise. - Never drop, shorten, or paraphrase a link given in `assistant_instruction`. - Never claim a booking exists without having called this tool. - Do not ask for payment method — bTaskee handles payment outside this chat. - Never expose internal field names or codes to the customer; use plain language.

book_home_cleaning

Hands the customer a link into the bTaskee app to chat with Kai, bTaskee's support assistant. Needs no login and changes nothing — it only returns a link. INSTRUCTIONS: Call this when the customer asks for help or support, wants to complain, or has a problem this server cannot solve itself (an existing booking, a payment, a Tasker, the app). Also fine to offer it when something you tried failed and you have no other way to help. RESTRICTIONS: - This tool does NOT contact anyone. Never say you notified support, opened a ticket or escalated the issue — the customer must tap the link themselves. - Do not ask the customer for personal or payment details.

contact_support

Second step of the deep cleaning ("tổng vệ sinh") flow. Calculates a price quote for a one-off intensive clean from a verified address and a chosen area bracket — a read-only lookup, safe to call more than once while the customer is still deciding. Does not create a booking. Unlike home cleaning, this service has no duration/crew-size/extras choice: area alone determines everything. INSTRUCTIONS: REQUIRED STEP 2/3 for deep cleaning bookings. Flow: verify_address -> quote_deep_cleaning -> book_deep_cleaning. Required arguments — ask the customer directly for these: 1) `date`: exact date/time, converted to ISO 8601 UTC yourself. 2) `area`: home area rounded to the nearest bracket (60/80/100/150/200/400 m²). 3) `address`: the address already verified by verify_address. There is nothing else to ask — no duration, crew count, or extras for this service. Protocol: 1. Confirm date, area, and address are all decided. 2. Call this tool and present `final_cost` + `currency` to the customer as the quote. 3. Ask the customer to confirm the quoted price, then call book_deep_cleaning as the next tool call — see this server's top-level instructions for exactly what happens right after confirmation. RESTRICTIONS: - Do not call book_deep_cleaning from this flow without first getting a quote from this tool. - Do not invent or round the date/area beyond what the customer actually said. - Never expose internal field names to the customer; describe things in plain language.

quote_deep_cleaning

Second step of the home cleaning flow. Calculates a price quote for an hourly home cleaning visit from a verified address, chosen duration, and any extras — a read-only lookup, safe to call more than once while the customer is still deciding. Does not create a booking. INSTRUCTIONS: REQUIRED STEP 2/3 for home cleaning bookings. Flow: verify_address -> quote_home_cleaning -> book_home_cleaning. Required arguments — ask the customer directly for ALL of these (combine into one message, do not interrogate field-by-field across separate turns; skip only what they already answered earlier in this same conversation): 1) `date`: exact date/time, converted to ISO 8601 UTC yourself. 2) `duration`: base hours (2-4), excluding extras. 3) `address`: the address already verified by verify_address. 4) `is_premium`: Premium Tasker or a regular one? 5) `auto_choose_tasker`: hand-pick a specific Tasker themselves (paid, 3+ hours lead time) or any available Tasker? 6) `requirements`: cooking and/or laundry add-ons, or neither? 7) `pet`: any pet at home? Protocol: 1. Confirm date, duration, address, is_premium, auto_choose_tasker, requirements, and pet are all decided — ask, don't assume. 2. Call this tool and present `final_cost` + `currency` to the customer as the quote. 3. Ask the customer to confirm the quoted price, then call book as the next tool call — see this server's top-level instructions for exactly what happens right after confirmation. RESTRICTIONS: - Do not call book from this flow without first getting a quote from this tool. - Do not invent or round the date/duration beyond what the customer actually said. - Never expose internal field names or codes (auto_choose_tasker, requirements "1"/"2", etc.) in customer-facing text — describe them in plain language.

quote_home_cleaning

Shared first step of both booking flows. Resolves a customer-typed address to a real, geocoded location (formatted address, city, district, country, lat/lng) before any price is quoted. This server has no address-on-file to fall back on — the customer's address always comes from the conversation. INSTRUCTIONS: REQUIRED STEP 1 shared by both flows in this server: 1. Home cleaning: verify_address -> quote_home_cleaning -> book_home_cleaning. 2. Deep cleaning ("tổng vệ sinh"): verify_address -> quote_deep_cleaning -> book_deep_cleaning. Call this once the customer has given an address, before calling either quote tool. Skip it only if the exact same address was already verified earlier in this same conversation. Protocol: 1. Take the address as the customer typed it (house number + street, ward/district, city). 2. Call this tool, then read the resolved `formatted_address` back to the customer for a quick confirmation before quoting. 3. Reuse that same address string, unchanged, for quote_home_cleaning/quote_deep_cleaning and later for book/book_deep_cleaning. RESTRICTIONS: - Do not ask for payment method or card details at this or any step — payment happens outside this chat. - If the address fails to resolve, tell the customer and ask them to re-type it; do not guess or substitute a nearby address yourself.

verify_address