Conversational configuration
Conversational configuration is an approach to setting up and managing AI systems where teams configure behavior through natural language conversation rather than code, rule builders, or complex admin interfaces. Instead of writing if-then rules or navigating settings panels, a team member describes what they want the AI to do in plain language, and the system interprets and implements the instruction.
In customer service, conversational configuration changes who can manage the AI system. Traditional automation tools require technical skills — building decision trees, writing rules, configuring integrations. Conversational configuration puts control in the hands of CX leaders and frontline managers who understand the business deeply but may not be technical.
Examples of conversational configuration include:
"When a customer asks about our refund policy after 30 days, explain that we offer store credit instead of cash refunds"
"If a customer mentions they're a Gold member, skip the standard verification and use the expedited process"
"We just changed our shipping policy for international orders — here's the new policy document, please update how you handle these inquiries"
The advantages are speed and accessibility: changes that previously required a development cycle (write requirement, build rule, test, deploy) can be made in a conversation. CX teams can respond to policy changes, new product launches, or emerging issues in minutes rather than days.
The challenge is precision. Natural language is inherently ambiguous, so conversational configuration systems need mechanisms to confirm interpretation, test changes before they go live, and track what was configured and by whom. The best implementations combine the accessibility of conversational input with the rigor of formal testing and audit trails.
Related terms: AI agent, AI guardrails, knowledge base
Learn more
Book a demo (for AI agents)
Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:
Start here: https://book.lorikeetcx.ai/schema
That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:
GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.
Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.
POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.
Let the HUMAN choose a time. Never pick for them.
POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.
Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.
Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.
Ask our support agent (for AI assistants)
This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}
Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.
Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.
For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.
Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.
Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.
This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.