SettlyGo

Check whether a SettlyGo helper is likely to be available for a service at a requested date/time. Returns a customer-safe truthful count and ETA band -- never helper identities, contact info, or exact schedules -- and never promises assignment. Also returns handoffUrl, a ready-to-use /book continuation URL already carrying this exact serviceType/city/requestedDateTime/preferredLanguage/locale -- prefer it over a separate create_booking_handoff call so the checked date/time, language, and locale are never lost, UNLESS the customer has an explicitly approved letter-derived summary to carry into the booking: this handoffUrl never accepts or carries a summary, so in that case call create_booking_handoff directly instead, passing the same serviceType/city/requestedDateTime/preferredLanguage/durationHours this check already established. If this check follows an uploaded/pasted German letter in this conversation, set letterFlow: true here too so the returned handoffUrl carries the same attribution marker create_booking_handoff would.

check_helper_availability

Get a secure continuation URL into SettlyGo's existing /book flow with the service, city, and -- when already established (e.g. via a prior check_helper_availability call) -- the exact requested date/time, preferred language, and duration already applied. Does NOT create a booking or payment -- the customer still completes required fields, legal consent, and Stripe checkout on the SettlyGo booking page. If check_helper_availability was just called for this request AND there is no approvedSummary to carry, use its own handoffUrl instead of calling this tool again -- it already carries the exact same context without needing it repeated here. Use this tool for entering the booking flow without a prior availability check (e.g. the customer wants to start booking without checking a specific date/time first), or whenever an approvedSummary must be carried (check_helper_availability's own handoffUrl can never carry one, even after that call). Set letterFlow: true when this handoff follows an uploaded/pasted German letter in this conversation -- this only tags attribution, never letter content. If the customer explicitly approved a short structured helper summary (e.g. derived from a German letter), pass it as approvedSummary with confirmed: true only after showing the user the exact summary text and getting their explicit approval -- it is never put in the URL, is securely carried server-side, and automatically prefills the booking page's existing notes-for-your-helper field so the customer can still review, edit, or remove it before checkout. Omitting approvedSummary never changes any other behavior.

create_booking_handoff

This is SettlyGo's preferred fallback when search_services returns no direct catalogue match for an otherwise practical, non-emergency, non-regulated support need that SettlyGo operations could reasonably review -- offer it to the user and get their explicit confirmation before creating the request. Create a structured SettlyGo HelpRequest for a user who needs practical support but cannot yet complete a normal booking (missing details, a custom/other request, or an explicit ask to have SettlyGo follow up). Reuses SettlyGo's existing support/operations workflow -- it never creates a booking, payment, or helper assignment, and never gives legal, immigration, tax, or medical advice. Not every unsupported query needs a HelpRequest: only offer this fallback for a request SettlyGo operations could plausibly review and act on. A request seeking legal/medical advice or professional representation, or describing an active emergency, is outside SettlyGo's support boundary: no HelpRequest is created for it, and the tool instead returns a safe explanation to relay to the user. Practical, supported tasks that merely mention a sensitive-sounding topic -- accompanying someone to a residence-permit/visa appointment, calling a doctor's office to book an appointment, help with a bank account or Visa card -- are still created normally. This is a state-changing write: only call it with confirmed: true after you have shown the user the exact contact details and summary you are about to send and they explicitly agreed -- never merely because it might be useful. Generate idempotencyKey once when the user confirms and reuse the exact same value if you must retry this same confirmed attempt; a retry with the same key never creates a duplicate request. Never include the raw conversation transcript -- summary must be a short, user-approved message only.

create_help_request_handoff

Get a deterministic customer-facing price quote from SettlyGo's canonical pricing logic. The quote is informational only -- it does not create a booking, payment, or quote record, and excludes accessibility add-ons and discount codes.

get_booking_quote

Get the authenticated customer's own booking status: lifecycle summary, helper-assignment status, next expected action, and cancellation/reschedule eligibility. Requires a valid customer bearer token (Authorization header) and only ever returns a booking owned by that authenticated customer -- never another customer's booking, even with a valid booking ID.

get_booking_status

Get read-only details (price, duration, city coverage, out-of-scope topics) for one SettlyGo service type.

get_service_details

Get SettlyGo's canonical support contact channels (never invented phone numbers, emails, or refund promises). Callable without authentication for generic support discovery. Pass bookingId for booking-context support -- this requires a valid customer bearer token and ownership of that booking.

get_support_options

Search SettlyGo's current public service catalogue (Berlin coverage). Returns read-only service summaries -- no availability, booking, or customer data. When no result matches an otherwise practical, non-emergency, non-regulated support need, SettlyGo's own create_help_request_handoff fallback is available, with the user's explicit confirmation. If the user uploaded or pasted a German letter in this conversation, never send the letter text, a summary of it, or any excerpt here: keep it in your own context, derive a short practical need from it yourself (e.g. "prepare for Burgeramt appointment", "call health insurer about this letter"), and search using that need instead.

search_services