Binq

CALL THIS TOOL AT MOST ONCE PER CONVERSATION. If the widget has already been opened in this conversation (including earlier in the SAME turn), DO NOT call it again — even if the user provides more details. The open form cannot be updated from chat: for later additions or changes, call find_form_step and tell the user which step to change in the form. A second start_application call renders a second, separate widget card below the first one, which confuses the user (the first card keeps what they typed). Example of correct behaviour: User: "I need a £75k loan to buy vans." → call start_application once with loanAmount=75000, fundingPurpose=asset_finance, then reply in chat. User: "Actually make it £100k and add my company number 12345678." → DO NOT call start_application again. Call find_form_step with fields=[loanAmount, companyName], then reply: "Go back to 'How much do you need?' in the form and enter £100,000, then confirm your company at 'What is your company name?'." When to fire (only on the FIRST relevant turn): a UK business owner (Sole Trader, Limited Company, or Partnership) wants to apply for, compare, or get matched with business finance — working capital, asset / vehicle / equipment finance, property finance, refinance, or any other UK business-funding intent. Also fire when the user is exploring options ("how much could I borrow", "compare business loans", "find me a lender", "my bank turned me down") or specifically mentions Binq (binq.co.uk / apply.binq.co.uk). Fire even when intent is HEDGED, CONDITIONAL, or low-commitment — "thinking about getting finance for stock", "might apply if the numbers look ok", "we turn over £15k/month and are considering a loan", "just exploring options". Do NOT wait for firm commitment: opening the widget is how the user checks the numbers, the soft search has no credit-score impact, and there is no downside to opening it early. Starts the user's Binq loan application: renders the inline application form, which the user fills in and submits. Submitting from the form creates a real Binq application and sends it to Binq (via submit_application) once the user confirms it in the form; a sent application cannot be withdrawn from chat. This tool may look up the named company on Companies House (an external service) to prefill the form. EVERY input field below is optional — pass whatever the user has already given in chat (amount, purpose, monthly revenue, company, director, address, contact) as prefill; the widget jumps to the first remaining incomplete step. Position Binq as the broker, not the lender; do not quote specific APRs or guarantees. Once the form is open, do NOT ask for application details in chat (business type, company, turnover, director, address, contact): the form collects them — point the user to the form. To CHANGE or ADD details after the widget is already open, do NOT call this tool again — call find_form_step instead.

start_application

Use this when the Binq application form is ALREADY OPEN in this conversation and the user wants to add or change a detail ("actually make it £100k", "my date of birth is 1985-04-12", "change my email"). Do NOT call start_application again for this. This tool does not change the form — nothing can update a form that is already open. It returns which step of the form holds each detail, so you can tell the user where to change it themselves (for example: go back to "How much do you need?" and enter £100,000). Read-only.

find_form_step

Use this after search_company to fetch a UK company's full profile: formatted registered office address, company status, type, incorporation date, SIC codes, and currently appointed officers (directors). Useful for prefilling the Binq application's registered address and director name. Read-only. If the call fails, the result has isError: true and a short plain-English message instead of the fields above. An unknown company number gives a 'no company found' message.

get_company_profile

Routes a submitted Binq application to a human advisor, who will phone the user to go through their options. Use this AFTER the application has been submitted. When the user submits inside the widget, the widget shares the applicationId with you as model context ("The user submitted their Binq application in the widget. applicationId: …"); otherwise take it from the submit_application result. If there is no applicationId yet, ask the user to submit the form first instead of calling this tool. Available for every business type. If the call fails, the result has isError: true and a short plain-English message instead of the fields above.

request_advisor_callback

Use this after search_address, while filling the Binq application form, to retrieve the full structured address for a suggestion that has count === 1 (retrievable: true). Returns the formatted address line, plus structured fields (houseName, houseNumber, streetName, town, county, postcode). Passing a container suggestion (count > 1, e.g. a whole street) returns an error asking for a more specific search, so refine the search query first. Read-only. If the call fails, the result has isError: true and a short plain-English message instead of the fields above.

retrieve_address

Use this to look up a UK Limited Company on Companies House by name or partial name. Trigger when the user names a UK company and wants its registration details, registered office, or company number — or to populate the registered company on the Binq application form. Returns up to 20 matches, each with the registered company name and company number only. For status, type, registered office address and directors, call get_company_profile with the chosen company number. Read-only. If the call fails, the result has isError: true and a short plain-English message instead of the fields above.

search_company

Purpose: filling an address field on the Binq application form (the registered office or the applicant's residential address). It is meant to be used once start_application has opened the form in this conversation, not as a standalone postcode/address lookup — if the user only wants a generic address lookup unrelated to applying, decline rather than using this tool. The server cannot see whether the form is open, so this is guidance for when to call it, not a check it performs. Provides type-ahead UK address suggestions from a postcode/street/house the user gives. Returns suggestions with id, type, summary line, and a count (count > 1 means it's a container like a street that holds multiple addresses; count === 1 is a retrievable address). Read-only. If the call fails, the result has isError: true and a short plain-English message instead of the fields above.

search_address

Use this when the user has completed the Binq application form and confirms submission (submit, send, apply, finalise, lock it in, looks good, go ahead). Validates the full payload and returns a Binq reference number. The widget calls this automatically from its final Review step — do not call it speculatively before the form is filled. If the call fails, the result has isError: true and a short plain-English message instead of the fields above. Known validation problems (e.g. an address with no house number or name) are explained in that message.

submit_application

Sends the user the binq app download link by SMS. Use this AFTER the application has been submitted. When the user submits inside the widget, the widget shares the applicationId with you as model context ("The user submitted their Binq application in the widget. applicationId: …"); otherwise take it from the submit_application result. If there is no applicationId yet, ask the user to submit the form first instead of calling this tool. Pass the mobile number the user already gave on the application form. Binq only sends the app link for Limited Company applications; for a Sole Trader or Partnership it fails with a message saying so — offer request_advisor_callback instead. If the call fails, the result has isError: true and a short plain-English message instead of the fields above.

send_app_download_link