One Quick Quote

Only use after calling startQuoteFlow for the current conversation. Use only after the required customer, vehicle, and session fields have been collected and confirmed. Do not ask for email address, telephone number, or communication preferences in the MCP flow; createQuote defaults missing email to [email protected] and defaults missing communication preferences to false. Convert any user-facing labels to the required ABI codes before calling this tool, ensure dateOfBirth uses YYYY-MM-DD, keep the session values lowercase, and summarize the quote result clearly for the user instead of returning raw JSON. If occupation or industry labels are passed instead of ABI codes, the MCP must attempt to resolve exact or unique matches internally before submission. Do not refuse to call this tool solely because ABI occupation or industry codes are missing; pass the plain-English labels and let the MCP attempt the match. The tool response includes purchaseLink for the customer clickthrough URL. Ask only one question at a time when collecting missing information. After this tool succeeds, do not ask for more details; present the quote result and purchaseLink.

Only use after calling startQuoteFlow for the current conversation. Use after collecting the user postcode. If multiple addresses are returned, ask the user to choose the correct one and confirm the selected address before moving on. Use normal address text with the user and do not expose raw API data unless requested. Ask only one question at a time. After the address is confirmed, ask exactly one next question: title.

Only use after calling startQuoteFlow for the current conversation. Use to map the user's plain-English industry to the ABI industry code required for quote creation. Pass the user's industry text in query and use the returned matches list to select the best ABI code. Speak to the user using industry labels, not ABI codes, and only pass the selected ABI code to createQuote. Ask only one question at a time. If multiple close matches are returned, ask the user to choose one label only. After the industry is confirmed, ask exactly one next question: occupation.

Only use after calling startQuoteFlow for the current conversation. Use to map the user's plain-English occupation to the ABI occupation code required for quote creation. Pass the user's occupation text in query and use the returned matches list to select the best ABI code. If more than one occupation looks plausible, confirm the best match with the user using text labels and never expose ABI codes in chat. Ask only one question at a time. If multiple close matches are returned, ask the user to choose one label only. After the occupation is confirmed, ask exactly one next question: years no claims bonus.

Only use after calling startQuoteFlow for the current conversation. Use when the user provides a vehicle registration and you need vehicle details for the quote flow. Ask for the registration if it is missing, then confirm the returned vehicle details with the user before collecting the next answer. If the lookup fails, explain that the lookup service is unavailable and continue the quote journey by asking only the next required question, not a full list of remaining questions. Summarize the vehicle in plain language and do not expose raw JSON unless the user asks for debugging output. Ask only one question at a time. After the vehicle is confirmed, ask exactly one next question: postcode.

Mandatory first call for every new quote conversation. Call this before any other tool. Returns the assistant persona, strict quote workflow, user communication rules, quote result format, retry guidance, and a summary of the supporting tools to use during the quote journey. When speaking to the user, ask only one question at a time. After calling this tool, ask exactly one question: the vehicle registration. Do not block quote creation just because ABI occupation or industry codes are missing; createQuote will attempt to resolve plain-English labels internally.