Conversion: qualified enquiry

Structured intake with consent, scored against your qualification rules and delivered to your CRM.

An enquiry is the right conversion when a customer needs a conversation before saying yes. Instead of a free-text message, the agent fills a structured intake: the need, timing, location, an optional budget, contact details and explicit consent. AGORA scores it against your qualification rules, merges duplicates from the same contact within seven days, and delivers it to your CRM.

Set it up

1. Enable inquiry (it is on by default in the general pack).
2. Review the intake fields. The general pack asks for need, timing, location, budget (optional), contact and consent; an industry pack can add fields, and fields marked confidential never reach logs or prompts.
3. Set the qualification rules and connect your CRM. The demo delivers to a CRM stand-in.

What an agent does

Fetch the intake schema, collect the answers from the customer, and submit the enquiry with consent. The answer says whether it was qualified and what happens next, so the agent can tell the customer honestly.

Applies to

Endpoints in this build

MCP tools

Besides the read tools every merchant server has, a business that enables Qualified enquiry exposes:

• search_services: Search services
• get_people: Get people
• get_credentials: Get credentials
• get_fees: Get fees
• request_consultation: Request consultation

Events

Delivered as webhooks:

Source: docs/portal/docs/conversions/inquiry.md + KIND_CONVERSION_MATRIX + registered routes + MCP tool registry