cancel_service_plan_subscription
ChatGPTCancel a customer's service plan subscription and stop billing them. This cancels the Stripe subscription first, then marks it cancelled in BlueSuite — doing only the second would leave the customer being charged every cycle. If Stripe refuses, nothing is changed and an error comes back; report that to the user rather than assuming billing stopped. Confirm with the user before calling: this stops a recurring payment.
complete_contact_task
ChatGPTMark a follow-up task done, or reopen one. For a repeating reminder this affects only the single occurrence, leaving the rest of the series in place.
complete_equipment_task
ChatGPTMark a maintenance task done, or reopen it. For repeating servicing this affects only the single occurrence.
convert_request
ChatGPTTurn a request into a job, quote or invoice. Use this rather than creating the record yourself: it carries over the client and property and marks the request converted in one step. Jobs and quotes retain a source-request link. Invoices do not retain a source-request link; record the returned invoice ID separately if you need to trace the conversion. Creating a job or quote by hand leaves the request sitting in the queue as if nobody had dealt with it. Ask which they want if the user just says "convert this" — a quote prices the work first, a job schedules it, an invoice bills for it directly.
create_contact
ChatGPTCreate a new contact
create_contact_property
ChatGPTAdd a property (service address) to a contact
create_contact_task
ChatGPTAdd a follow-up task or reminder to a client. Use this for anything the user wants to remember about a specific client that is not itself billable work — "follow up next week", "chase the deposit", "annual service due in March". For work that gets done and paid for, create a job instead.
create_equipment
ChatGPTAdd a piece of company equipment — a truck, trailer, tool or machine the business owns. Leave name off and it is derived from year/make/model, falling back to the serial number and then the category. Setting replacement_date automatically creates a "Replace <name>" reminder task.
create_equipment_note
ChatGPTRecord work done on a piece of company equipment — a repair, a service, an inspection result, or a plain note. This is the equipment history, so record what happened here rather than only completing the task.
create_equipment_task
ChatGPTAdd a maintenance task to a piece of company equipment — an oil change, an inspection, a repair to book. Use recurrence for scheduled servicing that repeats.
create_event
ChatGPTCreate a new event. Three kinds: an APPOINTMENT is a visit for an existing job or request, a TASK is a to-do on the calendar, an EVENT is a standalone calendar entry. Recurrence (recurrence_type="recurring") applies to tasks and events only — appointments cannot repeat on their own. For repeating visits, put the job on a recurring schedule with setup_recurring_job, which also sets the job type and billing settings.
create_installed_equipment
ChatGPTRecord a unit installed at a customer's property. property_id is required — a unit is always installed somewhere. Leave name off and it is derived from make and model, then the equipment type. Setting warranty or replacement dates schedules reminders automatically.
create_installed_equipment_note
ChatGPTRecord work done on an installed unit — a service, a repair, an inspection result. This is the unit's history at that property and outlives any one job.
create_installed_equipment_reminder
ChatGPTSchedule a one-off reminder about an installed unit. Do NOT create warranty or replacement reminders this way — those are generated and kept in step automatically from the unit's dates, so a hand-made one duplicates them. Use this for anything else, and note it can go to the customer, the team, or both.
create_invoice
ChatGPTCreate a new invoice
create_job
ChatGPTCreate a new job
create_job_expense
ChatGPTCreate a new expense for a job. Expenses track costs such as materials, subcontractor fees, permits, etc. Provide a receipt via receipt (a user-attached file from the chat) or attachment (a storage path from a prior upload_file call).
create_new_lead
ChatGPTCreate a brand-new lead in one call: contact + optional property + request, atomically linked. Use this for the common "new inquiry" happy path where all three records are new. For existing contacts, existing properties, or adding another request/property to an existing contact, use the per-entity tools instead (create_contact, create_contact_property, create_request). Property is optional — omit it if the inquiry has no specific service address; the request will be created without a property link. Returns the created contact_id, property_id (or null), request_id, plus the full created request for follow-up calls.
create_payment
ChatGPTRecord money already received against an invoice or quote. For "mark invoice paid", set object_type="invoice", category="payment", settle_remaining=true and omit amount. The server records only the outstanding balance, accounting for existing payments and deposits, and then updates the invoice status. Repeating settlement of an already covered balance creates no payment. For a specific partial payment, supply amount. Omitted method defaults to other. Supply created_at only when the user gives a payment date. This records a manual payment; it does not charge a card.
create_quote
ChatGPTCreate a new quote
create_quote_from_template
ChatGPTCreate a new draft quote from an existing quote template. The new quote inherits the template's line items, pricing, discounts, deposits, tax rate, message, and payment instructions. Requires the quotes:write scope.
create_quote_template
ChatGPTCreate a new quote template. Templates store line items, pricing, discounts, deposits, tax rates, and messages that can be reused when creating new quotes.
create_request
ChatGPTCreate a new service request
create_service
ChatGPTCreate a new saved product or service. Once created, it can be used as a line item on quotes, jobs, and invoices.
create_service_plan
ChatGPTCreate a recurring service plan customers can subscribe to. This defines the offer — price, how often it bills, how often visits happen — and bills nobody by itself. New plans start as drafts; publish with update_service_plan_status. Note billing cycle and visit frequency are independent: a plan can bill monthly and visit quarterly.
create_tag
ChatGPTCreate a new tag for one kind of record. Check list_tags first — tags are matched by ID, not name, so creating a second "Urgent" tag splits the records between them.
create_tax_rate
ChatGPTCreate a new tax rate preset. Once created, it can be applied to quotes, jobs, and invoices.
create_time_entry
ChatGPTLog time against a job, quote, request or service plan. Durations are in MINUTES — record two hours as 120, not 2. Defaults to the signed-in user; pass user_id to log time for a crew member.
delete_contact
ChatGPTDelete a client. Their properties, follow-up tasks, notes and saved payment methods cascade away with them. Jobs, quotes and invoices remain but are left without a client. Confirm with the user first, especially when the client has live work — there is no undo.
delete_contact_property
ChatGPTDelete a property from a contact
delete_contact_task
ChatGPTDelete a follow-up task. To record that it was done rather than remove it, use complete_contact_task — deleting loses the history.
delete_equipment
ChatGPTDelete a piece of company equipment, along with its tasks and service log. To take something out of service without losing its history, set status to "retired" or "sold" instead.
delete_equipment_note
ChatGPTDelete an entry from a piece of equipment's service log.
delete_equipment_task
ChatGPTDelete a maintenance task. To record that it was done, use complete_equipment_task instead — deleting loses the history.
delete_event
ChatGPTDelete an event by ID
delete_installed_equipment
ChatGPTDelete an installed unit and its service history. To record that it was taken out or swapped, set status to 'removed' or 'replaced' instead — that keeps the history for the property.
delete_installed_equipment_note
ChatGPTDelete an entry from an installed unit's service history.
delete_installed_equipment_reminder
ChatGPTDelete a scheduled reminder on an installed unit.
delete_invoice
ChatGPTDelete an invoice by ID
delete_job
ChatGPTDelete a job and everything that hangs off it. Every appointment cascades away, including completed visits, along with expenses and change orders; invoices and time entries survive but lose their link to the job. For a recurring job this destroys the whole visit history — to stop repeating work use end_recurring_job_schedule, which keeps the past and only removes visits after a cutoff. Confirm with the user first; there is no undo.
delete_job_expense
ChatGPTDelete an expense from a job
delete_payment
ChatGPTDelete a payment. This will automatically recalculate the parent object status (e.g., invoice may revert from "paid" to "partially_paid" or "sent").
delete_quote
ChatGPTDelete a quote by ID
delete_quote_template
ChatGPTDelete a quote template by ID. Deleting a quote template will not affect existing quotes that use it.
delete_request
ChatGPTDelete a service request by ID
delete_service
ChatGPTDelete a product or service by ID
delete_service_plan
ChatGPTDelete a service plan. Archive it instead if anyone has ever subscribed — archiving stops new signups and keeps the history.
delete_tag
ChatGPTDelete a tag. This removes it from every record it is currently applied to.
delete_tax_rate
ChatGPTDelete a tax rate preset by ID
delete_time_entry
ChatGPTDelete a time entry by ID
delete_upload
ChatGPTRemove a file attachment from its parent entity. If the underlying file is not linked to any other entity, the file is also permanently deleted from storage.
end_recurring_job_schedule
ChatGPTStop a job's recurring schedule from a given date. Use this when the user says to stop, cancel or end repeating work — do NOT delete the job, which would take its history with it. This is a cutoff, not a delete: visits after the date are removed, while visits on or before it, and anything already completed or invoiced, are kept. Confirm the date with the user, since "stop after this month" and "stop immediately" remove different visits.
get_contact
ChatGPTGet a single contact by ID with expanded details (properties, activity)
get_entity_tags
ChatGPTGet the tags currently applied to one record (a job, quote, invoice, request or contact).
get_equipment
ChatGPTGet one piece of company equipment with its details and assignee.
get_event
ChatGPTGet a single event by ID with expanded details
get_help_article
ChatGPTFetch a BlueSuite product help article by the guide ID returned from list_help_guides. Use its content to answer the user and cite its source link.
get_installed_equipment
ChatGPTGet one installed unit with its property, client and details.
get_invoice
ChatGPTGet a single invoice by ID with expanded details, including the payments recorded against it and amount_due — what the client still owes. Use amount_due for balance questions rather than subtracting from total yourself; it is derived from the line items, and the stored total can be stale.
get_job
ChatGPTGet a single job by ID with expanded details
get_job_expense
ChatGPTGet a single expense by ID for a job
get_payment
ChatGPTGet a single payment by ID
get_quote
ChatGPTGet a single quote by ID with expanded details
get_quote_template
ChatGPTGet a single quote template by ID with expanded details (tax rate, line items, creator)
get_request
ChatGPTGet a single service request by ID with expanded details
get_service
ChatGPTGet a single product or service by ID
get_service_plan
ChatGPTGet one service plan with its pricing, billing cycle and visit schedule.
get_service_plan_subscription
ChatGPTGet one subscription with its plan, customer, status and billing details.
get_started
ChatGPTPersonalized starting point for a user who has just connected BlueSuite and does not know what to do next. Call this on the first BlueSuite exchange of a conversation when the user only greets you, confirms the connection, asks what BlueSuite can do, or seems unsure how to begin. Returns suggested first actions based on what is actually in their account. Do not call it when the user has already asked for something specific.
get_tax_rate
ChatGPTGet a single tax rate preset by ID
get_timesheet
ChatGPTGet a single timesheet by ID with expanded details
get_upload
ChatGPTGet a single upload link with a fresh signed URL. The link_id is the ID returned by upload_file or list_files.
get_workspace
ChatGPTGet basic information about the current BlueSuite workspace — name, industry, country, currency, timezone, and about blurb. Use this when the user asks about their business or workspace.
hold_job
ChatGPTPlace a job on hold with a reason, optional notes, and an optional follow-up date. Confirm whether upcoming unstarted appointments should be cancelled to release their time slots or kept booked. Completed and in-progress visits are preserved. Existing invoices and payments are unaffected. The person placing the hold receives email and dashboard follow-ups when due. For recurring jobs, cancel_appointments=true also pauses new visits; false keeps existing appointments and continues normal generation. Service plans are not supported.
link_installed_equipment_to_job
ChatGPTLink an installed unit to a job, recording that the job worked on it.
list_contact_properties
ChatGPTList all properties (service addresses) for a contact
list_contact_tasks
ChatGPTList the follow-up tasks and reminders on a client — things like "call back Thursday" or "annual service due". Filter by status to see what is still outstanding.
list_contacts
ChatGPTList contacts with optional pagination and search
list_equipment
ChatGPTList the company's own equipment — vehicles, trailers, tools and machines the business owns. This is NOT equipment installed at a customer's property.
list_equipment_notes
ChatGPTRead the service log for a piece of company equipment: notes, maintenance, repairs and inspections.
list_equipment_tasks
ChatGPTList maintenance tasks on a piece of company equipment — services, inspections, and the automatic replacement reminder.
list_events
ChatGPTList events (appointments, tasks, visits) with optional pagination, search, and filters
list_files
ChatGPTList files attached to a parent entity (contact, request, quote, job, invoice, event, or timesheet). Returns paginated upload links with fresh signed URLs.
list_help_guides
ChatGPTIndex of BlueSuite product help articles. Use it to find guides relevant to a user's how-to question before fetching the best match.
list_installed_equipment
ChatGPTList equipment installed at customers' properties — furnaces, water heaters, irrigation controllers and so on. This is NOT the company's own trucks and tools; use list_equipment for those. Filter by property or contact to see what is installed for one client.
list_installed_equipment_jobs
ChatGPTList the jobs that have touched an installed unit — its service history by job.
list_installed_equipment_notes
ChatGPTRead the service history for an installed unit: notes, maintenance, repairs and inspections.
list_installed_equipment_reminders
ChatGPTList the scheduled reminders on an installed unit. Warranty and replacement reminders are maintained automatically from the unit's dates; custom ones are added by hand.
list_invoices
ChatGPTList invoices with optional pagination, search, and filters
list_job_expenses
ChatGPTList expenses for a job. Expenses track costs associated with jobs (materials, subcontractors, permits, etc.).
list_jobs
ChatGPTList jobs with optional pagination and search
list_payments
ChatGPTList payments with optional filtering by parent object (invoice/quote), status, and pagination.
list_properties
ChatGPTList properties (service addresses) across the workspace with optional search by street, city, state, or zip code. Returns linked contact IDs.
list_quote_templates
ChatGPTList quote templates. Templates are reusable starting points for creating new quotes with pre-filled line items, pricing, and messages.
list_quotes
ChatGPTList quotes with optional pagination and search
list_requests
ChatGPTList service requests with optional pagination and search
list_review_requests
ChatGPTReview requests that have gone out and what came back — star rating, written feedback, and whether the client clicked through to a review platform. Use this to answer how the reviews are going, and to check whether a client has been asked recently before asking again.
list_service_plan_subscriptions
ChatGPTList customers subscribed to service plans, with their status and billing amount. Use this to answer who is on a plan, who is paused, and who cancelled.
list_service_plans
ChatGPTList the recurring service plans the business offers — maintenance agreements, seasonal packages. These are templates customers subscribe to, not the subscriptions themselves.
list_services
ChatGPTList saved products and services. These are reusable line items that can be added to quotes, jobs, and invoices.
list_tags
ChatGPTList the tags defined for one kind of record. Call this before tagging something, to find the tag IDs and to avoid creating a duplicate of a tag that already exists.
list_tax_rates
ChatGPTList tax rate presets for the workspace. These can be applied to quotes, jobs, and invoices.
list_time_entries
ChatGPTList time entries with optional pagination and filters
list_timesheets
ChatGPTList timesheets with optional pagination and filters
list_users
ChatGPTList workspace team members. Use this to resolve user names to IDs for assignment operations (e.g., assigning a job to "Bob").
request_review
ChatGPTAsk a client to leave a review. Sends immediately over whichever channels the workspace has turned on (email, SMS) and the client can actually receive. Confirm with the user before calling — this puts a message in front of their customer. Mention the appointment with event_id when the request is about one specific visit: it switches to a message that names the visit and the crew who attended, which lands far better than a generic ask. BlueSuite also asks automatically after jobs complete or invoices are paid if the workspace set that up, so check whether a recent request already went out before adding another.
resume_job
ChatGPTResume an on-hold job. For recurring jobs whose hold_cancel_appointments is true and whose schedule has not been explicitly ended, resume_on is required: visits restart on the original recurrence pattern from that date without catch-up visits. If all schedules have been explicitly ended, omit resume_on; resuming clears the hold without restarting them. If hold_cancel_appointments is false, omit resume_on; appointments continue unchanged. End dates and occurrence limits stay unchanged. Read the current job first and pass its held_at timestamp so a stale request cannot resume a newer hold. Status is recalculated from existing work. Cancelled records stay in history. Recurring visits are generated again from resume_on; one-off appointments must be scheduled separately.
send_notification
ChatGPTSend a transactional customer-facing notification (email + SMS where configured). Use this to send a quote to a customer, send an invoice, or send an appointment reminder. The "type" determines both the message template and the target module: quote_to_customer→quotes, invoice_to_customer→invoices, appointment_reminder→events. "module_id" is the ID of that parent entity. Channel selection (email vs SMS) is automatic — it follows the workspace customer-notification settings and the contact's SMS opt-in. Email goes through AWS SES; SMS through Twilio. Set reminder=true for quote_to_customer or invoice_to_customer to send a "(Reminder)" prefixed message with reminder-friendly language instead of the initial send. Reminders do NOT change entity status. Without reminder (or reminder=false), invoice_to_customer transitions the invoice status to "sent" and quote_to_customer transitions to "awaiting_response". Does not currently support arbitrary internal messages to workspace users.
setup_recurring_job
ChatGPTPut a job on a recurring appointment schedule — weekly lawn care, quarterly maintenance, and so on. Use this rather than create_event for anything tied to a job: it marks the job recurring, saves the billing settings the completion flow reads, and creates the appointment series in one step. A recurring job created without this stays unscheduled and never generates visits. Confirm the billing_type with the user first, since per_visit sends real invoices to their client after every visit.
unlink_installed_equipment_from_job
ChatGPTRemove the link between a job and an installed unit.
update_contact
ChatGPTUpdate an existing contact
update_contact_property
ChatGPTUpdate a property for a contact
update_equipment
ChatGPTUpdate a piece of company equipment. Send only the fields that change — the server merges them over the existing record, so a status change on its own will not disturb the name or other details.
update_equipment_note
ChatGPTEdit an entry in a piece of equipment's service log.
update_equipment_task
ChatGPTEdit a maintenance task. To mark one done use complete_equipment_task, which for repeating servicing completes only that occurrence.
update_event
ChatGPTUpdate an existing event. For an occurrence of a recurring appointment, set update_scope to say whether the change applies to just this visit, all future visits, or should rebuild the upcoming schedule.
update_event_status
ChatGPTUpdate only the status of an event. Use this instead of update_event when changing status, as status transitions may trigger business logic.
update_installed_equipment
ChatGPTUpdate an installed unit. Send only what changes — the server merges it over the existing record, so a status change alone will not disturb the name or which property it is at. Changing warranty or replacement dates re-syncs the automatic reminders.
update_invoice
ChatGPTUpdate an existing invoice
update_invoice_status
ChatGPTRecord a change to an invoice's status. This does NOT email anyone — marking an invoice "sent" sets its due date and notifies the business internally, but the client receives nothing. To actually deliver an invoice to the client, use send_notification with type="invoice_to_customer", which emails and texts the client according to the workspace notification settings and moves the invoice to sent. Use this tool for cancelling an invoice or correcting a status. To mark an invoice paid, use create_payment with object_type="invoice", category="payment", and settle_remaining=true. A paid status update is rejected if the invoice still has an outstanding balance.
update_job
ChatGPTUpdate an existing job. For an in-progress job that requires change orders, line items, discounts, and taxes cannot be changed here; create a change order in the dashboard. Omit line_items when only updating job details. Setting status here applies the same completion rules as update_job_status (for example, required forms must be filled in before a job can be completed), so prefer that tool when status is the only change.
update_job_expense
ChatGPTUpdate an existing expense for a job. Provide a new receipt via receipt (a user-attached file from the chat) or attachment (a storage path from a prior upload_file call). Pass attachment: "" to clear the existing receipt.
update_job_status
ChatGPTChange a job's status with completion rules enforced. Use hold_job and resume_job to manage holds. Draft, Scheduled and Ongoing are derived from the job's appointments and cannot be set by hand. Use "reopen" to bring a completed or cancelled job back; the correct status is then re-derived from its appointments.
update_payment
ChatGPTUpdate an existing payment. Changing amount or status will automatically recalculate the parent object status.
update_quote
ChatGPTUpdate an existing quote
update_quote_status
ChatGPTRecord a change to a quote's status. This does NOT email anyone. To actually deliver a quote to the client, use send_notification with type="quote_to_customer", which delivers it and moves the quote to awaiting response. Use this tool for bookkeeping: marking a quote accepted, declined or archived after hearing back some other way.
update_quote_template
ChatGPTUpdate an existing quote template. Modifying a quote template will not affect existing quotes that use it.
update_request
ChatGPTUpdate an existing service request
update_request_status
ChatGPTUpdate only the status of a service request. Use this instead of update_request when changing status, as status transitions may trigger business logic.
update_service
ChatGPTUpdate an existing product or service
update_service_plan
ChatGPTUpdate a service plan. Send only what changes — the server merges it over the existing plan. Changing the price affects new subscribers; anyone already subscribed keeps billing at the terms they signed up under, since their charge lives in Stripe.
update_service_plan_status
ChatGPTPublish, unpublish or archive a service plan. This is the template's own status: archiving a plan stops new signups but does NOT cancel or stop billing anyone already subscribed to it.
update_service_plan_subscription
ChatGPTReassign a subscription: which client it belongs to, which property it covers, or who manages the account. Price and billing cadence cannot be changed here — those live on the plan and in Stripe, and editing them in BlueSuite alone would disagree with what the customer is actually charged. There is also no way to CREATE a subscription from here: signing someone up requires collecting a payment method, which has to happen in the dashboard.
update_tag
ChatGPTRename a tag, change its color, or edit its description. A tag's record type cannot be changed — create a new tag instead.
update_tax_rate
ChatGPTUpdate an existing tax rate preset
update_time_entry
ChatGPTUpdate an existing time entry
update_timesheet_status
ChatGPTUpdate only the status of a timesheet. Use this for approval workflows (draft → pending → approved/rejected).
update_upload
ChatGPTUpdate the name, description, or category of an existing upload link. The underlying file bytes cannot be replaced — delete the link and re-upload to change the file itself.
upload_file
ChatGPTAttach a file (receipt, photo, PDF, document, video, audio) to a parent entity (contact, request, quote, job, invoice, event, or timesheet). Also used to upload line item images: pass module_type="workspace", module_id = workspace ID (call get_workspace first if needed), category="line_item", is_public=true, then use the returned path and id as image_path/image_id in a quote/invoice/job line item. Provide the file via file (a user-attached file from the chat — preferred when available), source_url (a URL to fetch), or base64_data (raw bytes). Max file size is 100 MB. Allowed MIME types: image/jpeg, image/png, image/webp, image/gif, image/avif, application/pdf, Word/Excel/PowerPoint docs, CSV, plain text, video (mp4/avi/mov), audio (aac/mp3/wav).