Asklane

Use this when the user asks a specific question about the vendor whose Asklane code they pasted. Answers only from the vendor's own published content and returns no answer when that content doesn't cover the question.

answer_vendor_question

Used only by the Asklane inquiry card itself to get its one-time send link. Not for the assistant; it sends nothing.

get_send_token

After the user sent an inquiry with the Asklane card: returns which of the vendor's qualifying questions the inquiry already answers and which are still open (ids q1 to q5), for the follow-up code that prepare_inquiry gave you. Support requests and account-manager requests have no follow-up questions; the result says so.

get_followup_questions

Use this when the user wants current information about a vendor whose Asklane code they pasted (what it does, pricing, what happens after an inquiry, what to prepare, which kinds of request it takes). Needs the code from the vendor's line; without it there's nothing to look up.

get_vendor_profile

Use this when the user pastes a line from a vendor's website with an Asklane code, or asks to send that vendor an inquiry or demo request. Takes the code, the ref and the inquiry fields known from the conversation. Shows the vendor's own inquiry card, filled in and editable. This tool sends nothing; the user reviews the card and sends it from there to that one vendor. Some vendors take more than one kind of request, each called a path: buy (a sales inquiry, the default), help (a support request from an existing customer) and account (a request for the customer's account manager). get_vendor_profile and prepare_inquiry say which paths a vendor has; offer only those. Picking the path: if the chat makes it clear, use that path. If it's unclear, confirm in one sentence first, for example "Sounds like a support case, right?". If the chat is blank, ask one question first that names only the vendor's paths. A hint from the vendor's website is only a hint. If the user's message names the page they came from ("I was on …"), read that page to help pick the path. For help, first try to solve the problem from the vendor's docs and the chat, and prepare a support request only if that didn't work or the problem is specific to the user's account (billing, a bug, their data). On a help question, answer it first from the vendor's docs. If the answer shows the problem comes from the customer's plan (a feature not in their plan, a seat or usage limit), say so plainly and offer once, as one optional line, to pass a request to the vendor's account team ("this depends on your plan; want me to ask them?"): only when the docs or the vendor's plan info support it, never on every support visit, no sales language. If a vendor doesn't take support requests, give its support page instead and prepare nothing. Never put passwords, API keys, tokens, or card or bank numbers into a request; tell the user to leave them out.

prepare_inquiry

Saves answers to the vendor's open follow-up questions (from get_followup_questions) and returns the next open question. Answers must come from the user or this conversation. When no question is left open, the vendor gets the inquiry together with these answers in one email (if the request already went out after 10 minutes, as one short follow-up).

answer_qualifying_questions