Intent Mapping is one of the most powerful ways to build smarter conversational flows in Leadoo AI. With our latest platform updates including Custom Intent Fields and Real-time API calls you can now direct users to precise pathways and surface live product data effortlessly.

Read our Leadoo AI Product Update: Custom Intent & Real-time API Updates to see how these features work in action (especially for eCommerce), or follow the 5 core steps below to start mapping your own intents.

1. Define the Unique Commercial Boundary

Before writing utterances, ask: “What is the singular business goal of this intent?” Every intent must have a clear, non-overlapping purpose.

• The Rule: If two intents share the same outcome (e.g., Sales Demo vs Pricing Quote), combine them into one intent and use Meta Fields to capture the distinction.

2. Supply High-Variance Utterances (Quality Over Quantity)

NLU engines learn best from varied phrasing patterns rather than minor keyword tweaks.

• Do this: Include short questions, full sentences, action-oriented commands, and common colloquial phrases.
• Avoid: Adding 10 phrases that only swap out one word (e.g., “I want a demo”, “I want a fast demo”, “I want a quick demo”).

3. Establish Clear Exclusion Logic in Guidance

Since users often mix context in open-ended text fields, system guidance must explicitly state what NOT to match.

• Define negative phrases directly in the AI Guidance block (e.g., “Do NOT trigger if the user asks about job openings”).
• This prevents cross-firing between adjacent intents like Sales Demos (prospects) and Platform Training (existing clients).

4. Decide on Gating (Required vs. Optional Triggering)

Identify whether an intent should execute immediately or wait for critical information.

• Immediate Trigger: General FAQs, store hours, or basic routing.
• Gated Trigger: High-value lead paths (e.g., B2B Recruitment or Sales Quotes) where you must collect key data (like Role Title or Industry) via slot-filling before opening the final submission form.

5. Leverage Meta Fields for Silent Context Passing

Meta fields prevent your bot from repeating questions the user has already answered in their opening message.

• Use Meta Fields as entity extractors (e.g., storing “Sofa” or “IT Specialist”).
• Pass these variables directly to your CRM, webhook, or team notification email so sales reps receive fully qualified context.

Intent Configurations for Leadoo.com

1. Recruitment / Job Seekers (recruitment_job_seeker)

Triggers strictly when a visitor wants to work for Leadoo or apply for a role.

Example Utterances

• “Are you hiring software engineers right now?”
• “Where can I send my CV to join the Leadoo team?”
• “I want to apply for a job at Leadoo.”
• “Do you have open positions in sales or marketing?”
• “I’d love to work for Leadoo, how do I apply?”
• “Who do I contact regarding open vacancies?”
• “Is Leadoo hiring in Helsinki, London, or remotely?”

AI Guidance

Plaintext

TRIGGER CONDITIONS:
– Trigger ONLY when the visitor is personally looking for a job, career opportunity, internship, or open vacancy at Leadoo.
– Extract any mentioned department or role title into the `desired_role` meta field.

DO NOT TRIGGER IF:
– The user represents a business looking to recruit staff using Leadoo’s conversion tools (route to Sales).
– The user is asking platform/support questions or asking for sales demos.

ACTION:
– Route to the Careers page link or candidate application form node.

Meta Field Description

• desired_role (Type: String, Optional)
  “The job title, role, or department mentioned by the job applicant (e.g., Senior Developer, Sales Executive, Marketing Intern, Customer Success Manager).”

2. Customer Support (customer_support_platform)

Triggers when an existing customer reports an issue, bug, or needs technical help with the Leadoo backend or live widgets.

Example Utterances

• “My chatbot script isn’t firing on our website.”
• “I can’t log in to my Leadoo backend dashboard.”
• “Why isn’t our lead notification email sending to Hubspot?”
• “How do I edit an active InpageBot flow?”
• “I think we found a bug in the AI Intent mapper.”
• “How do I add a new user to our Leadoo organization account?”
• “Where do I set up our Google Analytics 4 integration?”

AI Guidance

Plaintext

TRIGGER CONDITIONS:
– Trigger when an existing user asks technical support, bug report, login, integration, or configuration questions about the Leadoo platform.
– Extract the affected feature or technical topic into the `support_topic` meta field.

DO NOT TRIGGER IF:
– The user wants a product demo or sales quote (route to Sales).
– The user is looking to sign up for platform training (route to Platform Training).

ACTION:
– Route to the Support Desk / Knowledge Base lookup node or trigger a technical support ticket form.

Meta Field Description

• support_topic (Type: String, Optional)
  “The specific technical feature, module, or issue reported by the customer (e.g., Hubspot Integration, Login Issue, Bot Script Error, Analytics/Reporting, User Permissions).”

3. Platform Training Sign-Up (platform_training_signup)

Triggers when a customer wants to learn how to use Leadoo better, join a user training session, or book onboarding.

Example Utterances

• “Where can I sign up for Leadoo user training?”
• “I want to register for the next Leadoo platform onboarding workshop.”
• “Do you offer training sessions for new bot builders?”
• “How can my team get certified on Leadoo?”
• “I want to join the live product walkthrough for existing clients.”
• “Where are the recordings for the bot building masterclass?”

AI Guidance

Plaintext

TRIGGER CONDITIONS:
– Trigger when a user explicitly asks to sign up, register, or join a Leadoo platform training session, academy, or masterclass.
– Extract any mentioned skill level or session topic into `training_focus`.

DO NOT TRIGGER IF:
– The user wants a pre-purchase product demo (route to Sales).
– The user is asking about marketing webinars aimed at prospective leads (route to Marketing).

ACTION:
– Route to the Training Registration / Leadoo Academy sign-up form node.

Meta Field Description

• training_focus (Type: String, Optional)
  “The level or specific module requested for training (e.g., Beginner Onboarding, Advanced Intent Mapping, Conversion Analytics Masterclass).”

4. Sales / Demo & Quote (sales_demo_quote)

Triggers when a prospect shows commercial buying intent, asks for pricing, or requests a product demo.

Example Utterances

• “I want to see a live demo of Leadoo for our website.”
• “How much does Leadoo cost per month?”
• “Can someone contact me with a custom pricing proposal?”
• “We’re looking for a conversational marketing tool and want to talk to sales.”
• “How does Leadoo compare to Drift or Intercom in pricing?”
• “I’d like to book a meeting with a Leadoo account executive.”

AI Guidance

Plaintext

TRIGGER CONDITIONS:
– Trigger when a prospective customer requests a demo, asks for pricing, requests a quote, or wants to discuss purchasing Leadoo.
– Extract any mentioned budget, company size, or goals into the `lead_context` meta field.

DO NOT TRIGGER IF:
– The user is an existing customer needing technical help (route to Customer Support).
– The user is looking for a job (route to Recruitment).

ACTION:
– Collect key lead qualification fields and open the Calendar Scheduler / Sales Contact Form node.

Meta Field Description

• lead_context (Type: String, Optional)
  “Key commercial details mentioned during the query (e.g., Pricing Inquiry, Demo Request, Competitor Comparison, Enterprise Plan).”

5. Marketing / Webinar & Event Sign-Up (marketing_webinar_event)

Triggers when a visitor wants to attend a marketing event, download a report, or register for a webinar.

Example Utterances

• “How do I register for your upcoming marketing webinar?”
• “I want to join the live event on conversational conversion trends.”
• “Where can I sign up for the conversion optimization masterclass?”
• “Can I get a link to register for the next Leadoo online talk?”
• “Are there any upcoming marketing events hosted by Leadoo?”

AI Guidance

Plaintext

TRIGGER CONDITIONS:
– Trigger when a user asks to sign up for, attend, or receive information about Leadoo’s external marketing webinars, industry events, or live panel discussions.
– Extract the event name into `event_name`.

DO NOT TRIGGER IF:
– The user is asking for product-specific user training for existing clients (route to Platform Training).
– The user wants a 1-on-1 sales demo (route to Sales).

ACTION:
– Route to the Webinar Registration form or Event Calendar node.

Meta Field Description

• event_name (Type: String, Optional)
  “The name or topic of the webinar or marketing event mentioned by the user (e.g., Conversion Masterclass Q4, B2B Lead Gen Webinar).”