Sigo Seguros car insurance quotes

Reviewed 1d ago.

• tools: 12 tools scanned
• metadata: scanned

No findings.

Tools (12)

• list_available_states

  Before the flow, optional: where Sigo quotes. The flow itself is next_question, then start_quote once, then get_quote. The US states Sigo Seguros is licensed to sell car insurance in, and what Sigo is. Ask this before collecting details, so a customer elsewhere is not taken through a full quote. The state a policy is rated in comes from where the car is kept overnight, not from where the customer lives or works. Read `state_is_decided_by` before asking for a ZIP: a car kept outside these states is not quoted on a ZIP inside them, however close the customer commutes. Sigo is an agency: it sells policies that carriers issue. The carrier pays it a commission, and in almost every state where it sells, the customer pays a one-time broker fee for the agency's service — in Florida there is none. Where there is one it is real and is itemised before anyone pays, in Sigo's own flow. Asked what Sigo charges — which customers ask before there is any quote — that is the answer, with no amount: s

• next_question

  Step 1 of 3: call it until ready_to_quote is true, sending back the collected it returns each time and each answer under answer_as.key. Then start_quote. Returns the one question to put to the customer now, in their language, with the options to offer when the field has a fixed set. Call it before each question and again after every answer, until `ready_to_quote` is true, then call `start_quote`. Send only what the customer said this turn, in `answered`, together with the `collected` from the last call. The connector keeps the record of the conversation, so nothing is repeated and an answer given before its turn is not lost. When `ready_to_quote` turns true, `summary` is what the customer has said: read it back and let them correct it before quoting. It exists so the order and the pace are the connector's rather than a matter of judgement: Sigo's customers are working people, often quoting on a phone, and a turn that asks for four things at once is where they give up. Once a ZIP is

• find_occupation

  Second-round helper, outside the three steps: turns the customer's words into the occupation code start_quote takes. Turns what the customer said they do into the carrier's own occupation codes. Call it before sending `occupation` on a driver: the catalogue is written in trade names and customers answer in their own, so the code is never something to guess at. Pick the entry that matches what they described and send its code. An empty list means ask them another way rather than settle for the nearest thing.

• start_quote

  Step 2 of 3: call it once, with the collected next_question returned when ready_to_quote was true. It returns a quote_id for get_quote. If it answers quote_in_progress, do not call it again: read the quote_id you already have. Retrying the same call, after a timeout say, is safe: while its rating runs, the retry starts no second one and answers quote_in_progress. Asks Sigo's carriers for car insurance estimates. Carriers answer over tens of seconds, so this returns a quote_id straight away rather than waiting; read the prices with get_quote. Estimates are not binding: this does not select a policy, take payment or bind coverage. No browser is needed to get them: they come back in these tool calls, and the link in each one is where the customer continues if they want to buy. Call it once the details are gathered. Gather them a step at a time in conversation — listing every field up front reads as a form and loses people before the first answer. For a customer who already has a quote

• get_quote

  Step 3 of 3: read the quote_id start_quote returned, after poll_after_seconds, until more_carriers_pending is false. Never start_quote again to refresh a result. Reads the estimates for a quote_id returned by start_quote. Carriers answer at different speeds: when more_carriers_pending is true the list is not final and poll_after_seconds says how long to wait before asking again. The list closes within a minute either way, with whatever arrived — a carrier that did not answer is not a price, and there is none to go looking for. Once it is closed, to_final_quote.next_call is what to do next. No price here is final, in any round: the final quote is calculated by Sigo in the link, after the carrier's questions.

• resolve_application_link

  Outside the three steps: for a customer who arrives with a Sigo link they already have. Says what a Sigo link points at, how far that application has got, and the one thing the customer has to do next. Call it when someone shows up with a link — from an email, a text, or their own notes — and asks for help finishing. Pass only the Sigo link or code they shared. It resolves the short link, the long one and a bare code. It reads only: it opens nothing on the customer's behalf, and asking twice changes nothing. It reports no price, carrier or personal detail, because Sigo does not send any — whoever holds a link gets this same answer, so there is nothing here that identifies its owner. Say the `message` as given rather than composing one.

• carrier_questions

  After the three steps, when to_final_quote.next_call names it: the questions of the estimate the customer picked. Then answer_carrier_questions. Once the customer has picked an estimate, this returns the questions that carrier asks in their state — attestations and disclosures the carrier words itself. Say `preamble` first, then ask one `ask_together` block per turn, each question exactly as it is worded; they are not Sigo's questions to reword. Send the answers with `answer_carrier_questions`. `can_answer_here` is false where that carrier does not finish online, and then a Sigo agent takes it from there. Either way the customer keeps the link: they can finish on the web at any point without losing what they have answered.

• answer_carrier_questions

  After carrier_questions: file the answers, passing answers_so_far back each time, until the set is complete. Saves what the customer answered against their application, which is what moves it towards a final quote. Send every answer under the code it came back with, and only what the customer actually said. This does not take payment, sign anything or bind coverage. Those happen in Sigo's own flow, through the link that comes back here. The carrier takes its questions as a set, so answers are held until every one has been given. Pass the `answers_so_far` from the previous call back in, and only the new answer needs to go in `answers`.

• other_carrier_questions

  Only when get_quote's cover_first, or answer_carrier_questions, names it: after the one option shown could not be the answer (declined, not available, or an answer it does not take), or when the customer wants to compare a confirmed price. Then answer_other_carrier_questions. Returns the questions of the other carriers in the customer's state, once for all of them and minus whatever the customer already answered anywhere (pass the `answers_so_far` answer_carrier_questions handed back, when it did). Say `preamble` first, then ask one `ask_together` block per turn, each question exactly as it is worded. No price comes with these: a Sigo agent confirms the final offer through the link. `can_answer_here` is false when nobody priced the customer, and then a Sigo agent takes it from there.

• answer_other_carrier_questions

  After other_carrier_questions: file the answers, passing answers_so_far back each time, until the set is complete. Saves what the customer answered against their application. Once every required question has an answer the whole pass is filed, Sigo selects the cheapest of the other carriers, and a Sigo agent confirms the final offer with the customer. Send every answer under the code it came back with, and only what the customer actually said. This shows no price and does not take payment, sign anything or bind coverage.

• commercial_next_question

  Commercial auto, step 1 of 2: call it until ready_to_submit is true, sending back the collected it returns each time and each answer under answer_as.key. Then submit_commercial_application. For a vehicle a business owns or uses for its work: a contractor's pickup, a delivery van, a box truck, a tow truck, a fleet. It takes the short intake Sigo's commercial form opens with, one question at a time in the customer's language, and a Sigo agent quotes it with the carriers afterwards. There is no estimate and no price here, and none to give: say any quote is subject to underwriting, eligibility and state filing. Its first question tells a business apart from someone who drives only for Uber, Lyft, DoorDash or Uber Eats. That is personal auto: route_to_personal turns true, nothing commercial is sent, and next_question takes it from there. When it is not clear which kind of customer this is, start here. Ask `ask` as the website words it, with its options, and wait for the answer. It never

• submit_commercial_application

  Commercial auto, step 2 of 2: call it once, with the collected commercial_next_question returned when ready_to_submit was true. Do not call it again after it answers: a repeat is usually answered with the earlier request and already_received: true, but that is not guaranteed, and a second call can file a second request. Sends the intake to Sigo, where a licensed agent reviews it and follows up by email. It is a request for a quote, not a quote: it returns no price, selects no policy, takes no payment and binds no coverage. Say `message` and `disclaimer` as written, and offer `form_url` with `form_note` for a customer who wants to add their vehicles and drivers now. A refusal comes back with a code, a message for the customer and a next_step for you. One that says the request did not reach Sigo carries form_url: never tell the customer it was received.