Wait! Before you leave...

See what an AI customer agent could answer on your website. Get a private assessment in 10 seconds.

Full crawling and production deployment require DNS domain verification.

New: Create a source-grounded AI customer agent from your verified website. Build your private preview →
Let's Chat Let's Chat
Zero-Trust Enterprise AI Agent 49 Global Languages in Portal & Chatbot

Turn Your Website Into an Authenticated AI Revenue Agent

Deploy a cryptographically verified customer resolution agent on your website that answers complex enquiries, qualifies high-intent leads, and schedules advisory meetings.

Start Free

Free plan available • No credit card required • 5-minute DNS TXT setup • Designed with reference to Singapore IMDA AI Framework (v1.5) →

DNS-Verified Ownership
Origin Restrictions
Source-Grounded Answers
Source Citations
Human Escalation (HITL)
Zero-Trust Boundaries

Instant Domain Capability Scanner

Enter your company website to test crawl readiness and generate a custom AI agent configuration.

We only scan publicly available web metadata. Zero intrusive scraping.

Ready to analyze. Input your domain on the left.

Your website has the answers. Your customers still cannot find them.

Most websites force visitors to search through pages, menus, PDFs, and forms. Conventional chatbots trap them in rigid, frustrating decision trees.

Tough Customer Enquiries

  • • Which service is right for me?
  • • How much does it cost?
  • • Can this integrate with our systems?
  • • Is this available in my country?

The Search Barrier

Visitors abandon the conversion funnel when information isn't instant. Contact forms collect details but lack context, forcing you to reconstruct historical conversations manually.

The Let's Chat Direct Route

Let’s Chat gives each visitor a direct route from question to answer—and from answer to action. We combine source-grounded answers with instant outcome workflows.

Direct Definition

What is Let’s Chat?

Let’s Chat is an AI website chatbot and customer-automation platform for businesses that want to convert more visitors and resolve more customer enquiries.

Unlike standard bots that only copy-paste script answers, Let’s Chat is a secure, origin-locked revenue and resolution agent.

Answer from approved content
Show sources behind answers
Recommend products or plans
Qualify sales opportunities
Book consultations
Create CRM & support tickets
domain_verification_rules.json

"security_mode": "dns_verified_origin_bound",

"verify_domain": "example.com",

"approved_origins": [

"https://example.com",

"https://www.example.com"

],

"enforce_sri": true,

"allowed_actions": ["lead:submit", "meeting:book"]

Let’s Chat operates only after the website domain and deployment origin have been approved.
Business Outcomes

One customer conversation can create a measurable business outcome

Stop focusing on chat message volume. Start focusing on conversion, scheduling, and ticket resolution.

Convert website visitors

Identify customer intent, recommend the relevant offering, and collect qualified lead information before they leave.

Resolve repetitive enquiries

Answer common questions using the website pages, documents, and knowledge sources you approve, safely locked.

Book meetings automatically

Collect the necessary customer information, check calendar availability, and schedule meetings automatically.

Improve customer experience

Let customers use natural language instead of searching through navigation menus or repeating themselves across channels.

Reduce service workload

Resolve routine questions and give human support agents a complete structured summary when intervention is required.

Improve the website itself

Discover questions that the website does not answer, identifying missing FAQ and content friction before conversion.

Workflow

How do you create a secure AI chatbot from your website?

01

Add your domain

Enter the website domain or subdomain you want Let’s Chat to use. We normalise and classify it.

02

Verify domain ownership

Add a unique Let’s Chat TXT record through your DNS provider. This confirms administrative authority.

03

Review knowledge & voice

Approve crawled pages, test responses, configure brand voice, and define action scopes.

04

Approve deployment origin

Specify the exact website origins (HTTP/HTTPS scheme, host, port) where the agent is authorised to load.

05

Install the loader script

Add our versioned async loader script. The agent receives a signed runtime credential on load.

06

Measure business outcomes

Track qualified leads, booked meetings, resolved enquiries, and website content gaps.

Security Differentiator

A website chatbot should prove that it belongs there

Public websites can be copied. JavaScript snippets can also be copied. That is why Let’s Chat does not treat simple possession of installation code as proof of authority.

Verified Domain Ownership

Before production crawling or publication, you prove control through a unique DNS TXT record. This prevents unauthorized indexation and official-looking spoof chatbots.

Authenticated Agent Deployment

Each production agent is bound to a verified domain, approved origin, specific workspace, controlled configuration version, and custom action permissions. Credentials are issued for short lifespans (5-15m).

Copied code is not enough

If a valid installation snippet is copied to an unapproved website, the origin does not match. No runtime credential is issued, the agent does not initialize, and the event is audited.

Website verification checklist

Verify authenticity using standard web security mechanisms:

// HTTPS-only delivery

// Versioned widget loaders

// Published subresource integrity (SRI) hashes

// Content Security Policy (CSP) configurations

Zero-Trust Platform Defense in Action

Witness Our Defense Behavior Live • Download Technical Whitepaper

Don't take vendor claims at face value. Test live threat drills—including Copied Snippet Attacks, Host Origin Spoofing, and Edge Kill-Switch Revocation—in our interactive Security Sandbox. Or download our complete 2026 Enterprise Security Whitepaper (PDF).

Tenant Boundary & Domain Isolation Namecheap DNS Anchoring <5ms Edge Revocation

Not another website chatbot. An agent that gets work done.

Most chatbots stop after providing information. Let’s Chat moves the customer towards a defined outcome.

Compare Options

Help visitors understand the difference between packages or courses based on business rules you define.

Book Consultations

Direct connection to Google Calendar, Calendly, or Outlook to secure immediate advisory calls.

CRM Sync

Automatically creates contact, lead, and activity cards in HubSpot or Odoo CRM.

Source-Grounded Answers

Give customers answers they can verify

Let’s Chat retrieves information from your approved knowledge sources before constructing an answer. You can configure it to link directly to the supporting page or policy.

Trust Mode Includes: Approved-source retrieval, claim-to-source traceability, confidence thresholds, unsupported-answer controls, topic boundaries, required disclaimers, human escalation rules, and regression testing.

Let's Chat Assistant

● Grounded in example.com

Our standard service SLA guarantees support ticket resolution within 24 hours.

Source: SLA & Refund Policy Page

Do not ask customers to trust an AI answer blindly. Give them a way to verify it.

Autonomous Agent Capabilities

Four Strategic Pillars of Customer & Revenue Automation

Beyond basic answers—Let’s Chat combines proactive sales qualification, seamless customer resolution, telemetry gap intelligence, and adaptive visitor personalisation.

Revenue Agent

Pillar 01 • Revenue Generation

Turn high-intent website questions into qualified opportunities

Visitors asking about pricing, implementation, integrations, availability, or timelines are high-intent. Let's Chat qualifies them in conversation.

Qualification fields include:

Company Role Budget Range Timeline Location Integrations
See Lead Qualification in Action Automated CRM & Calendar Handoff

Customer Resolution

Pillar 02 • Customer Resolution

Resolve customer enquiries without trapping people inside a bot

Let’s Chat answers common queries and guides customers through approved workflows. When they require a human agent, it transfers the session with full context.

The human agent receives:

• Full Conversation summary
• Urgency and sentiment
• Steps already attempted
• Recommended next action

The customer does not need to start again, and the team doesn't need to reconstruct details.

Content Intelligence

Pillar 03 • Content Intelligence

Find out what your website is failing to explain

Every customer question reveals a website, sales, or service gap. Let’s Chat identifies: frequently unanswered questions, pages with conflicting info, low-confidence topics, and products receiving the most interest.

Identifies documentation & sales gaps:

Unanswered Questions
Conflicting Page Data
Low-Confidence Topics
High-Interest Products

Use these direct customer insights to improve your copy, product positioning, sales enablement, onboarding documents, and product strategy.

Personalisation

Pillar 04 • Personalisation

Give each visitor the next best conversation

First-time visitors need education. Returning prospects need a product comparison. Active customers need support. A high-value opportunity needs immediate human handoff.

Dynamic visitor journey routing:

First-Time: Education
Prospects: Comparison
Customers: Support
High-Value: VIP Escalation

Let’s Chat adapts dynamically using the approved context and security data permissions, avoiding forcing every visitor through the same static decision trees.

Practical customer journeys

Find the conversation your customers need.

Explore practical examples for one website, a meeting workflow, an agency portfolio or a governed enterprise deployment.

Illustrative use cases. Desired outcomes depend on the configured workflow and service scope.

Answer customer questions

Useful answers and a clear next step for one website.

Independent consultants

Answer the question that comes before the call

Help prospective clients understand your services, process and published terms. Give them a useful answer and a clear route to your existing contact or scheduling page while you focus on client work.

Build my private preview
Explore five practical examples
The after-hours service-fit question

Do you help a small business redesign its operations?

The workflow: Explain the consultancy’s published service scope, cite the relevant page and link to its existing enquiry or scheduling page. If the scope is unclear, invite a human conversation.

The desired next step: A visitor understands the offer and can choose a relevant next step.

Evaluate: Supported service-fit answers and contact-link clicks.

Link to this example
The engagement-process explainer

What happens after I contact you?

The workflow: Describe the approved discovery, proposal and delivery process. Link to the process page and avoid inventing a turnaround or commitment.

The desired next step: Fewer basic process questions before a first conversation.

Evaluate: Repeat process enquiries and process-page engagement.

Link to this example
The published-fee navigator

Where can I find your package prices?

The workflow: Point to published packages and inclusions. If the project needs a custom quote, explain that boundary and link to the existing request form.

The desired next step: Clearer price expectations without an improvised quotation.

Evaluate: Pricing-link visits and clarification requests.

Link to this example
The first-call preparation guide

What should I prepare before speaking with you?

The workflow: Share the approved preparation checklist and link to a download or contact page. Keep business-specific assessment for the consultant.

The desired next step: Better-prepared prospects arriving through the existing journey.

Evaluate: Checklist clicks and preparation completeness noted by staff.

Link to this example
The existing-calendar bridge

How do I arrange an introductory call?

The workflow: Present the business’s approved external scheduling URL and explain the next step. The external scheduler handles availability and confirmation.

The desired next step: A clear route to the existing scheduling process.

Evaluate: External scheduler visits; bookings verified in that scheduler.

Link to this example

Boutique training providers

Help learners choose the right starting point

Explain your course options, published prerequisites and enrolment steps from approved content. Guide learners to the relevant course page or existing registration process before they abandon their search.

Build my private preview
Explore five practical examples
The prerequisite question

Can a beginner take this course?

The workflow: Explain the published prerequisites and learning level. Link to the course page and refer uncertain suitability questions to the provider.

The desired next step: Learners understand the stated entry requirements.

Evaluate: Prerequisite-related follow-up and relevant course-page clicks.

Link to this example
The course-comparison guide

What is the difference between your foundation and intermediate courses?

The workflow: Compare only published objectives, prerequisites and duration. Link to both course pages for the learner’s own decision.

The desired next step: A clearer starting point for course selection.

Evaluate: Comparison-to-course-page visits.

Link to this example
The public-schedule navigator

Where are the next advertised course dates?

The workflow: Use the current approved schedule page and link to registration. Do not claim live seat availability unless that is separately supported.

The desired next step: Learners find the provider’s current advertised schedule.

Evaluate: Schedule and registration-link clicks.

Link to this example
The course-fee explainer

What is included in the published course fee?

The workflow: Explain documented inclusions and payment terms. Route funding or subsidy questions to approved information or a human without promising eligibility.

The desired next step: Fewer misunderstandings about the advertised package.

Evaluate: Fee clarification requests and payment-info visits.

Link to this example
The enrolment-step guide

How do I register for this course?

The workflow: Describe the approved enrolment sequence and link to the existing form. The provider’s registration process handles acceptance and payment.

The desired next step: An accessible route from course information to registration.

Evaluate: Enrolment-link clicks and completed forms measured externally.

Link to this example

Specialist home-service businesses

Answer practical questions before the visit

Help customers find your service areas, package inclusions and preparation instructions. Direct them to your existing quote or booking process with clearer expectations about the service.

Build my private preview
Explore five practical examples
The service-area check

Do you provide this service in my area?

The workflow: Explain the published service areas and exclusions. When an address is outside the stated scope, link to a human enquiry rather than promising coverage.

The desired next step: Relevant customers can reach the appropriate request page.

Evaluate: Service-area answers and relevant enquiry-link visits.

Link to this example
The package-inclusion answer

Does the advertised package include this task?

The workflow: Summarise the approved inclusions and exclusions, cite the package page and link to the quote form for non-standard work.

The desired next step: Clearer expectations before a service request.

Evaluate: Package clarification questions and qualified form visits.

Link to this example
The visit-preparation checklist

What should I do before your team arrives?

The workflow: Show the approved preparation checklist and supporting page. Avoid adding unapproved instructions.

The desired next step: Customers find the preparation information in one place.

Evaluate: Checklist access and preparation issues noted by staff.

Link to this example
The rescheduling-policy guide

Where can I find your cancellation or rescheduling terms?

The workflow: Explain the published policy and direct the customer to the existing booking/contact channel. Do not modify appointments in the assistant.

The desired next step: Customers know how to request a change.

Evaluate: Policy-link clicks and correctly routed requests.

Link to this example
The custom-work request route

How do I ask about work outside your standard package?

The workflow: Explain what the existing quote form requests and link to it. Leave pricing, site assessment and scheduling to the business’s current process.

The desired next step: Non-standard enquiries reach the right existing channel.

Evaluate: Completed quote forms and relevance assessed by staff.

Link to this example

Small B2B suppliers

Make product information easier to find

Help trade buyers navigate published specifications, order terms and support information. Give them the source and an appropriate next step without inventing stock, compatibility or delivery promises.

Build my private preview
Explore five practical examples
The specification finder

Where can I find the dimensions and operating range?

The workflow: Find the approved specification page or document, answer the stated values and link to the source. Refer missing specifications to a person.

The desired next step: Buyers locate relevant documented product information.

Evaluate: Specification-source clicks and unanswered specification questions.

Link to this example
The documented-compatibility question

Does your documentation say this product works with this system?

The workflow: Use only approved compatibility notes. If a combination is not documented, explain that it needs confirmation and link to technical sales.

The desired next step: No invented compatibility promise during enquiry.

Evaluate: Documented answers and correctly routed compatibility questions.

Link to this example
The delivery-terms navigator

Where are your standard delivery terms?

The workflow: Explain published delivery conditions and link to the relevant page. Separate standard terms from a live dispatch date or order status.

The desired next step: Buyers understand the documented ordering process.

Evaluate: Delivery-policy visits and basic delivery enquiries.

Link to this example
The warranty-process guide

How do I request warranty support?

The workflow: Describe the approved support-request process and link to the existing channel. Do not decide whether a particular claim is covered.

The desired next step: Customers find the correct support route.

Evaluate: Correctly routed requests and repeated process questions.

Link to this example
The trade-account enquiry route

How do I ask about a trade account?

The workflow: Explain published trade-enquiry requirements and link to the existing form. Account approval and negotiated terms remain with the supplier.

The desired next step: Trade enquiries reach the intended business process.

Evaluate: Trade-form completions measured by the supplier.

Link to this example

Independent design and creative studios

Help clients understand the project before the brief

Explain your project types, deliverables and review process using approved website content. Help prospective clients find the right portfolio example and submit a clearer brief through your existing enquiry form.

Build my private preview
Explore five practical examples
The deliverable-scope explainer

What files and deliverables are included in this package?

The workflow: Describe the approved deliverable list and link to the package page. Refer custom requirements to the existing enquiry form.

The desired next step: Clients understand the stated package before briefing.

Evaluate: Scope questions and relevant brief-form visits.

Link to this example
The project-type navigator

Do you handle projects like the one I have in mind?

The workflow: Explain the studio’s published project types and point to relevant portfolio examples. Do not promise acceptance or timing.

The desired next step: Prospects can judge the studio’s documented fit.

Evaluate: Portfolio-to-enquiry visits.

Link to this example
The review-process answer

How do the review and revision stages work?

The workflow: Explain the approved stages and stated revision terms. Link to the process page for details.

The desired next step: Fewer mismatched expectations about project delivery.

Evaluate: Repeat process questions and clarification before proposals.

Link to this example
The handover-information guide

What should our team expect at handover?

The workflow: Share the published handover information and file formats. Direct custom production requirements to a person.

The desired next step: Clients understand the documented handover approach.

Evaluate: Handover-page engagement and clarification requests.

Link to this example
The project-brief route

What information should I include in my enquiry?

The workflow: List the studio’s approved briefing prompts and link to its existing form. The form and team handle submission and project qualification.

The desired next step: More complete briefs through the existing channel.

Evaluate: Brief completeness assessed by the studio.

Link to this example

Review current plan scope and allowances before selecting your deployment. Explore current plans

Qualify and book meetings

Prepare the enquiry and complete the configured meeting workflow.

Business consultancies

Turn a service enquiry into a prepared discovery meeting

Help prospective clients explain their challenge, identify the relevant service and arrange a discovery meeting. Give your team useful context for the conversation through the configured qualification and calendar workflow.

See a Growth workflow
Explore five practical examples
The challenge-to-discovery workflow

Can someone discuss our operating challenges with us?

The workflow: Explain the relevant service, collect agreed qualification details, show a summary for confirmation and offer the configured discovery calendar. Pass approved context to the responsible team.

The desired next step: A discovery meeting with a clearer starting point.

Evaluate: Qualified bookings, held meetings and context completeness.

Link to this example
The service-stream routing workflow

Should we speak with your strategy or implementation team?

The workflow: Use approved service descriptions and routing rules, clarify the business need and offer the relevant configured meeting or human route.

The desired next step: Enquiries reach a suitable team for the stated need.

Evaluate: Routing accuracy and reassigned enquiries.

Link to this example
The timeline-and-scope conversation

We need support this quarter; where do we begin?

The workflow: Collect agreed scope and timing fields, explain the next step and book an appropriate scoping meeting. Leave delivery commitments and proposals to the team.

The desired next step: A more useful scoping discussion.

Evaluate: Held scoping meetings and proposal-ready enquiries.

Link to this example
The procurement-question handoff

Who can answer our implementation and procurement questions?

The workflow: Answer from approved implementation material, identify unresolved questions and route a confirmed summary to the relevant human meeting.

The desired next step: A handoff with the unanswered buying questions intact.

Evaluate: Handoff completeness and follow-up resolution.

Link to this example
The business-case meeting route

Can we discuss the expected business value for our project?

The workflow: Explain the documented evaluation approach and gather the approved context for a discovery call. Avoid inventing savings or a guaranteed ROI.

The desired next step: A business-case conversation grounded in the prospect’s situation.

Evaluate: Qualified business-case meetings and accepted next steps.

Link to this example

Corporate training providers

Turn learning questions into a useful advisory meeting

Help HR teams and learners explain the skills they need, compare approved programmes and arrange a relevant advisory conversation. Bring the learning requirements into the configured calendar and CRM workflow.

See a Growth workflow
Explore five practical examples
The team-skills advisory route

Can you help our team learn practical AI skills?

The workflow: Explain relevant approved programmes, collect agreed team and objective fields, confirm the summary and offer the advisory calendar.

The desired next step: A training adviser receives a useful team brief.

Evaluate: Qualified advisory bookings and brief completeness.

Link to this example
The course-level advisory meeting

Which programme should our employees discuss with an adviser?

The workflow: Compare published prerequisites and outcomes, note uncertainties and arrange a human advisory meeting rather than deciding competence from a short chat.

The desired next step: A suitable conversation about learning level.

Evaluate: Held advisory meetings and programme-fit review.

Link to this example
The private-cohort enquiry

Can we discuss a private course for our organisation?

The workflow: Collect the agreed audience, delivery preference and timing fields. Pass a confirmed brief into the configured meeting/CRM process for human scoping.

The desired next step: Private-cohort enquiries arrive with relevant requirements.

Evaluate: Complete cohort briefs and qualified meetings.

Link to this example
The manager-and-learner alignment call

Can our manager discuss the course outcomes before enrolment?

The workflow: Explain approved outcomes and gather the questions for a scheduled adviser conversation. Do not promise certification or job outcomes beyond published terms.

The desired next step: Stakeholders can discuss the documented learning goals.

Evaluate: Outcome-focused meetings and clarified expectations.

Link to this example
The delivery-format scoping meeting

Can we discuss online versus on-site delivery?

The workflow: Explain published delivery options, collect relevant constraints and schedule a scoping discussion for availability and commercial confirmation.

The desired next step: An informed delivery-format discussion.

Evaluate: Qualified format enquiries and held scoping meetings.

Link to this example

Cybersecurity service providers

Make the first security conversation more useful

Help business buyers understand your published services, explain their requirements and reach the appropriate specialist. Prepare a confirmed enquiry summary and a relevant meeting without replacing technical assessment.

See a Growth workflow
Explore five practical examples
The service-fit specialist meeting

Should we discuss monitoring or a security assessment?

The workflow: Explain the published services, collect the approved organisational context and offer the relevant specialist meeting. A human determines the technical recommendation.

The desired next step: A better-informed first security conversation.

Evaluate: Qualified specialist meetings and routing accuracy.

Link to this example
The assessment-scope enquiry

Can we speak about an assessment for our business?

The workflow: Gather approved scope and timing fields, explain the assessment enquiry process and book a scoping meeting. Avoid treating chat input as an assessment finding.

The desired next step: An assessment discussion with useful context.

Evaluate: Complete scope briefs and held meetings.

Link to this example
The managed-service discovery route

Can someone explain your monitoring service?

The workflow: Answer from approved service descriptions, clarify the agreed commercial requirements and route to the configured discovery calendar.

The desired next step: A structured managed-service enquiry.

Evaluate: Qualified discovery meetings and accepted follow-up.

Link to this example
The evidence-question handoff

Who can answer questions about your service controls?

The workflow: Point to approved evidence material, collect unresolved questions and pass a confirmed summary to the appropriate human team.

The desired next step: Buying questions are preserved for accountable follow-up.

Evaluate: Evidence questions resolved and handoff completeness.

Link to this example
The procurement scoping conversation

We need a proposal; what information should we discuss first?

The workflow: Collect the permitted buying context and arrange a human scoping call. Pricing, commitments and service acceptance remain with the provider.

The desired next step: More proposal-ready conversations.

Evaluate: Held procurement calls and completeness of requirements.

Link to this example

B2B SaaS companies

Give your demo team the context behind the request

Help prospects explore approved product information, explain their requirements and arrange a relevant demonstration. Connect the confirmed enquiry to your configured calendar and CRM workflow.

See a Growth workflow
Explore five practical examples
The use-case-to-demo request

Can you show how your product fits our workflow?

The workflow: Explain documented product capabilities, collect approved use-case fields, confirm the summary and offer a relevant demo slot.

The desired next step: A demonstration with an agreed focus.

Evaluate: Qualified demos, attendance and agenda completeness.

Link to this example
The integration-question meeting

Does your documentation cover our integration requirement?

The workflow: Answer from approved integration documentation, flag gaps and include the unresolved requirement in a confirmed specialist/demo handoff.

The desired next step: Integration questions reach the right person.

Evaluate: Correctly sourced answers and specialist follow-up.

Link to this example
The plan-fit conversation

Which plan should our team discuss with sales?

The workflow: Compare published plan capabilities and limits, collect agreed context and offer a sales conversation for requirements outside standard plans.

The desired next step: More informed plan discussions.

Evaluate: Qualified plan enquiries and meeting relevance.

Link to this example
The implementation-readiness call

What should we prepare before an implementation discussion?

The workflow: Share the approved preparation guidance and gather relevant constraints for a configured implementation meeting.

The desired next step: A more complete implementation brief.

Evaluate: Brief completeness and held implementation calls.

Link to this example
The regional demo-booking route

Can I arrange a demo at a suitable time?

The workflow: Use the configured calendar’s actual availability and operating rules, obtain confirmation and book the meeting through the authorised workflow.

The desired next step: A confirmed demonstration through the configured calendar.

Evaluate: Successful genuine bookings and attendance.

Link to this example

Commercial equipment and maintenance providers

Prepare the service discussion before the site assessment

Help commercial buyers explain equipment, site and service needs before speaking with your team. Guide relevant enquiries into a configured scoping meeting while your specialists retain responsibility for assessment and quotation.

See a Growth workflow
Explore five practical examples
The equipment-service scoping route

Can we discuss maintenance for our equipment?

The workflow: Explain approved service scope, collect agreed equipment and site context, confirm the summary and schedule a scoping meeting. Leave technical assessment to the specialist.

The desired next step: A more complete commercial service brief.

Evaluate: Qualified scoping meetings and brief completeness.

Link to this example
The planned-maintenance enquiry

Can someone discuss a maintenance programme with us?

The workflow: Use published programme information, collect approved needs and timing fields and arrange a service-planning conversation.

The desired next step: A useful starting point for programme scoping.

Evaluate: Held programme discussions and accepted next steps.

Link to this example
The replacement-versus-support discussion

Who can discuss our options for this equipment?

The workflow: Explain the documented service categories and route the prospect’s confirmed context to a human. Do not determine technical suitability from chat alone.

The desired next step: The right specialist receives the question.

Evaluate: Routing accuracy and complete handoffs.

Link to this example
The multi-site project enquiry

Can our team discuss requirements for several locations?

The workflow: Collect the approved project summary and schedule a human scoping meeting. Multiple locations in an enquiry do not imply multiple website deployments under one plan.

The desired next step: A consolidated brief for a multi-location project.

Evaluate: Complete project briefs and held meetings.

Link to this example
The time-sensitive business enquiry

How do we contact your team about a time-sensitive service need?

The workflow: Follow the provider’s approved urgency and human-contact rules, gather permitted context and route appropriately. Do not promise emergency response or unverified availability.

The desired next step: Time-sensitive requests reach the approved channel.

Evaluate: Correct routing and follow-up time recorded by the business.

Link to this example

Review current plan scope and allowances before selecting your deployment. Explore current plans

Manage client websites

A scoped recurring conversation service for an established portfolio.

Web design and development agencies

Keep delivering value after the website goes live

Add a scoped conversation service to the client websites you already maintain. Manage authorised client agents through the agency offer and give clients an ongoing service with clear ownership and support responsibilities.

Request an agency walkthrough
Explore five practical examples
The post-launch managed service

What useful ongoing service can we offer maintained clients?

The workflow: Select two authorised client sites, configure relevant Growth-level workflows, agree support duties and review the Agency bundle before portfolio rollout.

The desired next step: An ongoing service with a demonstrable client use case.

Evaluate: Active paying client sites and service contribution.

Link to this example
The repeatable client onboarding

How do we onboard the next client consistently?

The workflow: Use a documented verification, approved-content, testing and handover checklist within the quoted agency configuration.

The desired next step: A more consistent rollout across the client portfolio.

Evaluate: Time to authorised activation and onboarding exceptions.

Link to this example
The branded service presentation

How can clients recognise the service as part of our offer?

The workflow: Configure the contracted white-label/domain options and show an actual client workflow. Align the branding and support promise with the agency’s service terms.

The desired next step: A coherent agency service presentation.

Evaluate: Branding acceptance and client adoption.

Link to this example
The client-access handover

What should our clients be able to view or manage?

The workflow: Apply agreed role permissions, demonstrate authorised client access and document who handles changes and escalation.

The desired next step: Clear client and agency responsibilities.

Evaluate: Access review results and support ownership clarity.

Link to this example
The content-maintenance review

How can we keep the assistant’s approved answers current?

The workflow: Review authorised content and permitted conversation evidence, test changes in the agreed staging workflow and obtain client approval before release.

The desired next step: A repeatable content-quality service.

Evaluate: Reviewed updates and recurring unresolved questions.

Link to this example

SEO and content agencies

Help content visitors find the answer and next step

Extend approved website content into useful conversations across your client portfolio. Help visitors reach relevant information and enquiries, then use permitted conversation evidence to improve the content you manage.

Request an agency walkthrough
Explore five practical examples
The search-visitor enquiry path

How can this visitor find the relevant service after reading our content?

The workflow: Use the client’s approved content to answer the question and offer the configured relevant next step. Keep each client’s knowledge and routing separate.

The desired next step: A clearer journey from useful content to an enquiry.

Evaluate: Relevant enquiry actions and held meetings where configured.

Link to this example
The missing-FAQ editorial review

Which questions should we address in the next content update?

The workflow: Review permitted client conversation evidence, identify questions not covered by approved content and validate proposed FAQ updates with the client.

The desired next step: Content priorities informed by real visitor questions.

Evaluate: Approved FAQ updates and repeated unanswered topics.

Link to this example
The content-to-service bridge

Which service page should a reader visit next?

The workflow: Explain the approved relationship between the topic and the client’s services. Link or route only to relevant documented offerings.

The desired next step: Visitors can find a suitable commercial next step.

Evaluate: Service-page visits and qualified enquiry progression.

Link to this example
The regional-content consistency check

How do we keep local answers aligned with approved pages?

The workflow: Review the client’s local-language sources and examples, test the configured response and obtain local approval before release.

The desired next step: Consistent answers for the supported regional content.

Evaluate: Reviewed language examples and correction requests.

Link to this example
The policy-update publishing workflow

How do we avoid showing outdated answers after content changes?

The workflow: Update the approved sources, test affected questions and obtain client approval within the agreed content/staging process.

The desired next step: A documented route for content changes.

Evaluate: Update turnaround and regression-test results.

Link to this example

Digital marketing and performance agencies

Carry the enquiry beyond the campaign click

Offer clients a configured conversation-to-enquiry workflow alongside campaign services. Keep client routing, reporting and usage responsibilities clear while measuring relevant downstream actions.

Request an agency walkthrough
Explore five practical examples
The campaign-to-qualified-meeting route

How do we help a campaign visitor explain what they need?

The workflow: Answer from the client’s approved landing content, gather agreed qualification details and use the configured meeting or human workflow.

The desired next step: A more useful downstream enquiry.

Evaluate: Qualified enquiries, held meetings and follow-up outcomes.

Link to this example
The separate-client CRM route

How do enquiries reach the correct client team?

The workflow: Configure and test the contracted client-specific CRM routing with approved sample data. Review tenant boundaries before launch.

The desired next step: Client enquiries reach their intended destination.

Evaluate: Routing-test results and misrouted enquiries.

Link to this example
The white-label outcome review

How do we explain the service’s results to a client?

The workflow: Use contracted reporting plus the client’s verified sales data. Distinguish visitor actions, held meetings and sales instead of claiming all uplift is caused by the assistant.

The desired next step: A more accountable client performance discussion.

Evaluate: Report completeness and agreed outcome definitions.

Link to this example
The portfolio-usage review

How should we manage uneven demand across clients?

The workflow: Review actual client usage against the contracted pool and authorisation rules. Agree changes with the client and platform rather than assuming automatic unlimited capacity.

The desired next step: Usage expectations match the portfolio’s demand.

Evaluate: Pool utilisation, overage authorisation and support load.

Link to this example
The campaign-change release check

How do we update a workflow when a campaign offer changes?

The workflow: Review the new approved offer, test affected questions and routing, and secure client approval before publishing the update.

The desired next step: A controlled change to campaign-facing conversations.

Evaluate: Change-test results and offer mismatch incidents.

Link to this example

CRM and automation agencies

Connect the conversation to the client’s agreed workflow

Add a customer-facing conversation layer to the CRM and calendar workflows you implement. Scope each client connection, confirm the handoff and keep access, usage and support ownership clear.

Request an agency walkthrough
Explore five practical examples
The HubSpot enquiry handoff

How can a confirmed website enquiry reach our client’s HubSpot process?

The workflow: Configure the supported connection and approved fields, test the confirmed handoff with safe sample data and agree ownership of failed deliveries.

The desired next step: A consistent, scoped enquiry handoff.

Evaluate: Successful confirmed handoffs and field completeness.

Link to this example
The Odoo CRM conversation route

How do we prepare a useful enquiry for our client’s Odoo CRM?

The workflow: Use the supported configured connection, confirm relevant enquiry fields and validate the client’s agreed routing and follow-up process.

The desired next step: Odoo enquiries arrive with usable context.

Evaluate: Correct routing and complete enquiry records.

Link to this example
The client-calendar implementation

How do we add an authorised booking workflow for a client?

The workflow: Configure the permitted calendar connection and operating rules, test booking and confirmation, and document change/support responsibilities.

The desired next step: A working client-specific meeting workflow.

Evaluate: Successful real bookings and connection reliability.

Link to this example
The form-to-conversation pilot

Can a conversation prepare a better enquiry than our current form?

The workflow: Run an agreed pilot for one client, compare confirmed enquiry completeness and follow-up, and retain the existing route where appropriate.

The desired next step: Evidence for whether the workflow improves enquiry quality.

Evaluate: Comparable brief completeness and qualified follow-up.

Link to this example
The BYOAI configuration evaluation

Can we evaluate an approved model provider for a client?

The workflow: Scope the contracted BYOAI configuration, credentials, external costs and content tests before a controlled evaluation. Confirm support boundaries before rollout.

The desired next step: A documented model-configuration decision.

Evaluate: Accepted test results and understood operating costs.

Link to this example

Regional full-service agencies

Deliver a consistent service across local client portfolios

Help regional clients present useful website conversations in their approved languages and service context. Combine local review with the contracted agency controls, reporting and client-support responsibilities.

Request an agency walkthrough
Explore five practical examples
The local-language client rollout

How do we launch a useful conversation for this local client?

The workflow: Select authorised local content, review real customer questions with a local reviewer and test the configured response and next step before deployment.

The desired next step: A reviewed conversation journey for the client’s audience.

Evaluate: Local test results and active client adoption.

Link to this example
The regional-offer boundary

How do we keep answers within each client’s local offer?

The workflow: Separate approved client sources and local service terms, test ambiguous questions and define the appropriate human route.

The desired next step: Answers stay aligned with the documented client offer.

Evaluate: Source-scope tests and corrected regional mismatches.

Link to this example
The local-client access model

Who should handle content changes and client review?

The workflow: Configure the contracted client/team roles and document local approvals, platform administration and escalation.

The desired next step: Clear regional delivery responsibilities.

Evaluate: Access reviews and approval turnaround.

Link to this example
The shared-capacity planning review

Can our portfolio fit the quoted conversation pool?

The workflow: Review actual demand and expected onboarding against the contracted pool. Agree expansion and spend authorisation before promising coverage.

The desired next step: A portfolio plan with understood capacity and cost.

Evaluate: Active-site occupancy and usage versus the agreed pool.

Link to this example
The joint client-outcome story

How can we show a useful local result to the next prospect?

The workflow: Select a verified, permissioned client example, define the measured outcome and present the agency’s actual service responsibilities.

The desired next step: Credible local proof for relevant prospects.

Evaluate: Qualified partner-sourced enquiries and evidence completeness.

Link to this example

Review current plan scope and allowances before selecting your deployment. Explore current plans

Evaluate governed deployment

A defined workflow with accountable operation and agreed evidence.

Financial services institutions

Help customers find approved information with a clear human route

Scope a customer-facing information journey around approved product and process content. Define the source boundaries, accountable human next steps and evaluation evidence needed for your enterprise deployment.

Discuss an enterprise use case
Explore five practical examples
The public-product information guide

Where can I find your published business account information?

The workflow: Answer only from approved public product material, show the source and route personalised suitability or eligibility questions to authorised staff.

The desired next step: Customers find information without an automated advisory decision.

Evaluate: Correctly sourced answers and appropriate human routing.

Link to this example
The application-process navigator

What are the published steps for making an application?

The workflow: Explain the approved process and link to the institution’s existing application channel. Do not collect sensitive documents or promise approval in this scenario.

The desired next step: A clearer route to the institution’s existing process.

Evaluate: Process-link visits and correct boundary handling.

Link to this example
The specialist-enquiry route

Who can discuss our organisation’s requirements?

The workflow: Gather only the permitted enquiry context, show the confirmed next step and route to the scoped authorised specialist workflow.

The desired next step: A specialist enquiry with appropriate context.

Evaluate: Qualified specialist enquiries and handoff completeness.

Link to this example
The regional-information boundary

Which published information applies in this market?

The workflow: Use the approved market-specific sources and explain uncertainty when scope is unclear. Escalate instead of transferring terms from another market.

The desired next step: Information remains within the documented regional scope.

Evaluate: Regional-source accuracy in acceptance tests.

Link to this example
The operator-governance evaluation

How will authorised teams review and manage the deployment?

The workflow: Evaluate the contracted operator identity, approval and audit arrangements using an agreed test plan. Public visitors are not assumed to require operator SSO.

The desired next step: Evidence for accountable operation of the workflow.

Evaluate: Accepted access, approval and audit tests.

Link to this example

Insurance providers

Explain the process while keeping decisions with people

Help visitors navigate approved product documents and service processes. Scope human escalation and deployment controls so policy decisions, claims adjudication and personalised advice remain in the appropriate authorised process.

Discuss an enterprise use case
Explore five practical examples
The policy-document navigator

Where is the public document that explains this product?

The workflow: Locate the approved public product document and explain where the relevant section is. Refer personalised coverage interpretation to authorised staff.

The desired next step: Visitors find the document and the appropriate human route.

Evaluate: Document-source visits and correct escalation.

Link to this example
The service-request process guide

How do I begin a service request?

The workflow: Describe the approved service steps and link to the provider’s existing channel. Do not change policy records in this illustrative workflow.

The desired next step: A clear starting point for a service request.

Evaluate: Correct process routing and repeated process enquiries.

Link to this example
The claims-process information route

Where can I find the published claims submission steps?

The workflow: Explain the public process and link to the existing claims channel. Do not assess, approve or predict a claim outcome.

The desired next step: Visitors reach the authorised submission process.

Evaluate: Correct claims-process links and boundary handling.

Link to this example
The corporate-insurance enquiry

Who can discuss an organisation’s requirements?

The workflow: Collect permitted business-enquiry context and route to the scoped human specialist process with confirmation.

The desired next step: A business enquiry reaches an accountable specialist.

Evaluate: Qualified corporate enquiries and complete handoffs.

Link to this example
The controlled-language evaluation

How do we verify that translated process answers preserve meaning?

The workflow: Test approved local-language examples with authorised reviewers, preserve source references and define escalation for ambiguity within the contracted scope.

The desired next step: Evidence that local information stays within approved boundaries.

Evaluate: Accepted local-language tests and review exceptions.

Link to this example

Multinational corporate groups

Keep the right answer within the right business context

Scope website conversations around approved brands, markets and business units. Give visitors a relevant next step while your authorised teams retain clear control over content, deployment and operational changes.

Discuss an enterprise use case
Explore five practical examples
The market-to-business-unit guide

Which business unit should I contact in this market?

The workflow: Use approved brand and market content to explain the relevant unit and direct the visitor to the scoped contact/workflow. Escalate uncertain matches.

The desired next step: Visitors reach the relevant business context.

Evaluate: Correctly routed enquiries and market-source test results.

Link to this example
The brand-source separation test

How do we prevent one brand’s information from appearing as another’s offer?

The workflow: Test the agreed domain/source boundaries with approved examples and adversarial cross-brand questions before release.

The desired next step: Evidence that configured answers respect the agreed scope.

Evaluate: Accepted source-boundary tests and exceptions.

Link to this example
The regional-policy information journey

Which published policy page applies to this location?

The workflow: Locate the approved regional source, show the relevant page and defer interpretations outside the configured scope.

The desired next step: Visitors can identify the applicable published information.

Evaluate: Source selection accuracy and escalation quality.

Link to this example
The operator-access lifecycle

How should teams gain, review and remove deployment access?

The workflow: Evaluate the contracted operator identity and role lifecycle, including joiner/mover/leaver tests where provisioned. Keep public visitor access separate.

The desired next step: An accountable operator-access process.

Evaluate: Accepted access lifecycle tests.

Link to this example
The approved-change release trail

Who approved this content or workflow change?

The workflow: Define the contracted approval and audit evidence for a controlled content/workflow release and verify the agreed records.

The desired next step: A traceable operational change process.

Evaluate: Complete approved releases and audit evidence.

Link to this example

Universities and training networks

Guide enquiries across a complex learning organisation

Help prospective learners and corporate partners navigate approved programmes and service information. Scope the sources, human routes and operational responsibilities across your institution’s departments or campuses.

Discuss an enterprise use case
Explore five practical examples
The programme-and-department guide

Which department can answer my programme question?

The workflow: Explain the approved programme information and direct the visitor to the relevant scoped adviser or contact route. Admission decisions remain with the institution.

The desired next step: Prospective learners reach the appropriate department.

Evaluate: Routing accuracy and qualified adviser enquiries.

Link to this example
The corporate-learning partnership route

Who can discuss a learning partnership with our organisation?

The workflow: Gather permitted organisational context and route a confirmed enquiry to the authorised partnership team.

The desired next step: Corporate enquiries arrive with a useful starting brief.

Evaluate: Qualified partnership enquiries and handoff completeness.

Link to this example
The published-entry information navigator

Where can I find the stated entry requirements?

The workflow: Link to current approved requirements and explain what the page says. Do not infer acceptance or determine individual eligibility.

The desired next step: Applicants find the institution’s stated requirements.

Evaluate: Source accuracy and appropriate human referrals.

Link to this example
The campus-service information route

Which campus or service team should I contact?

The workflow: Use approved campus and service content to identify the scoped contact channel, while escalating ambiguous requests.

The desired next step: Visitors find the relevant institutional service.

Evaluate: Correct service routing and repeated navigation questions.

Link to this example
The governed programme-update workflow

How do we review answers after a programme changes?

The workflow: Assign the authorised content owner, test affected questions and verify the contracted approval/release record before publishing.

The desired next step: A controlled update to programme-facing information.

Evaluate: Approved update turnaround and regression-test results.

Link to this example

Enterprise technology vendors and MSSPs

Support complex buying journeys with accountable control

Help business buyers explore approved solutions and reach the appropriate specialist. Scope the content, model configuration and operational evidence for a governed deployment across your enterprise sales journey.

Discuss an enterprise use case
Explore five practical examples
The enterprise-solution specialist route

Who can discuss our solution requirements across markets?

The workflow: Explain approved solution content, collect permitted business context and route to the scoped specialist process with confirmation.

The desired next step: Complex enquiries reach an accountable specialist.

Evaluate: Qualified specialist enquiries and complete handoffs.

Link to this example
The documented-integration boundary

What does your published documentation establish about this integration?

The workflow: Answer from approved integration material, preserve the source and route undocumented requirements to a specialist instead of asserting compatibility.

The desired next step: Buyers receive information with a clear evidence boundary.

Evaluate: Correctly sourced answers and resolved specialist questions.

Link to this example
The channel-partner enquiry

Who should discuss a proposed partner relationship?

The workflow: Use the approved partner information, collect permitted organisational context and route the confirmed enquiry to the authorised partner team.

The desired next step: Partner enquiries enter the appropriate process.

Evaluate: Qualified partner enquiries and handoff completeness.

Link to this example
The contracted-model evaluation

How do we evaluate an approved model configuration for this deployment?

The workflow: Test the contracted BYOAI/provider configuration, content boundaries and external cost responsibilities against an agreed acceptance plan.

The desired next step: Evidence for the scoped model decision.

Evaluate: Accepted response tests and understood operating costs.

Link to this example
The enterprise-operation evidence review

What evidence should the business and security owners accept before rollout?

The workflow: Review the contracted identity, audit, change and escalation controls using an agreed pilot. Match production promises to the signed scope.

The desired next step: A documented decision to expand the deployment.

Evaluate: Accepted control tests and signed operational responsibilities.

Link to this example

Review current plan scope and allowances before selecting your deployment. Explore current plans

ASEAN Positioning

Built for customer journeys across Singapore and ASEAN

Let’s Chat is designed for businesses operating across regional markets and languages. We preserve customer meaning, commercial intent, and local context instead of just doing simple literal translations.

English
Chinese
Malay
Indonesian
Thai
Vietnamese
Tagalog
Burmese
Khmer & Lao
Local ASEAN Currency Support

Stripe-backed native direct billing and automatic reconciliation across Southeast Asian sovereign currencies:

SGD (S$) MYR (RM) IDR (Rp) THB (฿) VND (₫) PHP (₱) BND (B$) KHR (៛) LAK (₭) MMK (K)

Regional Capabilities

  • • Mixed-language conversations: Seamlessly handle multi-lingual code-switching inside single chats.
  • • Local terminology: Incorporate region-specific definitions, jargon, and spelling.
  • • Country-specific content: Display regional policies, addresses, and pricing.
  • • Customer retention & governance: Custom data boundaries respecting PDPA and regional laws.
Middle East & GCC Positioning

Engineered for GCC Enterprises & Arabic Language Journeys

Native bidirectional Right-to-Left (RTL) script rendering, localized conversational etiquette, and enterprise data controls across the Gulf and Levant.

العربية (Arabic • RTL)
فارسی (Persian • RTL)
اردو (Urdu • RTL)
עברית (Hebrew • RTL)
Kurdî (Kurdish)
Türkçe (Turkish)
Local Middle Eastern Currencies

Direct Stripe processing in sovereign GCC and Middle Eastern currencies with 3-decimal dinar accounting:

AED (AED) SAR (SAR) QAR (QR) KWD (KD) BHD (BD) OMR (OMR) JOD (JD) ILS (₪) TRY (₺) EGP (E£)

Middle East Capabilities

  • • Bidirectional RTL Typography: Native Right-to-Left styling across chat widgets, forms, and admin consoles.
  • • Localized Etiquette: Culturally attuned dialogue flow respecting regional courtesies and greeting styles.
  • • GCC Operating Schedules: Configurable business hours and holiday calendars tailored to Sunday–Thursday weeks.
  • • High-Precision Dinar Accounting: Strict 3-decimal accounting support for KWD, BHD, and OMR.
Europe & Central Asia Positioning

Pan-European Multilingual AI with Enterprise GDPR Sovereignty

Comprehensive coverage across 24 European and Central Asian languages with zero-trust tenant isolation, strict origin attestation, and transparent European payment processing.

Deutsch
Français
Español
Italiano
Polski
Nederlands
Svenska
Čeština
16+ Others
European Multi-Currency Support

Direct Stripe invoicing across Pan-European currencies with automatic VAT compliance:

EUR (€) GBP (£) CHF (CHF) PLN (zł) SEK (kr) NOK (kr) DKK (kr.) CZK (Kč) HUF (Ft) RON (lei)

European Enterprise Governance

  • • Strict GDPR Data Privacy: No cross-tenant model training or external knowledge leakage.
  • • Cryptographic Origin Attestation: Origin-locked agent delivery preventing third-party script hijacking.
  • • EU VAT Invoicing: Compliant digital service taxation and structured Stripe billing receipts.
  • • Localized Number Formatting: Respects European decimal comma notation and regional address standards.
Integrations

Connect customer conversations to the tools your team already uses

HubSpot CRM
Odoo CRM
Google Calendar
Microsoft 365 Calendar
Custom Webhooks (Make & Zapier)
Secure Webhooks & APIs
Comparison

How Let’s Chat Compares with Industry Baselines

Compare security architecture, regional Asian language support, onboarding velocity, and transparent USD pricing.

Capabilities Rule-Based Decision Tree Bots Standard GenAI Embed Widgets (Q1 2026 Baseline) Let's Chat
1. Security Architecture & Zero-Trust Governance
Cryptographic DNS TXT Origin Attestation Requires public DNS TXT record proof before agent initializes No No (Script embed only) Mandatory
Sub-5ms Edge Revocation Enforcement In-memory edge termination gating all bootstrap & chat requests (<5ms local edge denial; DNS propagation per TTL) No Standard DNS TTLs (60s–300s) Sub-0.1ms Edge Denial
Closed Shadow DOM Style & Tree Encapsulation Encapsulates styles & DOM nodes to eliminate CSS collisions; all authentication and authorization remain server-side No Standard DOM injection Encapsulated DOM (Server-Auth)
Domain-Scoped Knowledge Isolation Refuses to serve proprietary business knowledge or vector embeddings to unauthorized origins N/A Unrestricted Origin Access Strict Domain Boundary
Interactive Security Sandbox & Threat Drills Interactive sandbox to test origin attacks, revoked IDs, and DNS invalidation No Gated Demo / Contact Sales Live at /sandbox
Regulatory AI Governance Alignment Human-in-the-loop (HITL) confirmation modals & audit trajectory logging None Standard Terms Only Designed with reference to IMDA v1.5
High-Concurrency Low-Latency Database Engine Non-blocking concurrent reads & writes with optimized memory cache and WAL journaling Legacy table locks Shared multi-tenant cloud DB Dedicated WAL Engine
2. Language Support & Asian Regional Localization (49 Locales)
Total Native Locales Supported Full portal console, chatbot agent personas, error handling, and RAG knowledge synthesis across 49 locales English only 4–5 Regional dialects 49 Native Locales
Multi-Language Tier Availability Access to multilingual conversational intelligence Expensive add-on Locked to $149/mo Team tier Included on ALL plans
ASEAN Regional Language Coverage (9 Locales) English (EN), Bahasa Melayu (MS), Bahasa Indonesia (ID), Thai (TH), Tiếng Việt (VI), Tagalog (TL), Khmer (KM), Lao (LO), Burmese (MY) No ID / TH partial only 100% Native Support (9/9)
East Asian Language Coverage (4 Locales) Simplified Chinese (ZH-CN), Traditional Chinese (ZH-TW), Japanese (JA), Korean (KO) No Partial Chinese 100% Native Support (4/4)
South Asian & Himalayan Regional Coverage (7 Locales) Hindi (HI), Tamil (TA), Bengali (BN), Urdu (UR), Nepali (NE), Sinhala (SI), Tibetan (BO) No No 100% Native Support (7/7)
Middle Eastern & Semitic Coverage with RTL (5 Locales) Arabic (AR), Persian/Farsi (FA), Hebrew (HE), Turkish (TR), Kurdish (KU) — with native right-to-left layout No RTL support Basic Arabic only Full Bidirectional RTL (5/5)
European & Central Asian Official Locales (24 Locales) Bulgarian (BG), Croatian (HR), Czech (CS), Danish (DA), Dutch (NL), Estonian (ET), Finnish (FI), French (FR), German (DE), Greek (EL), Hungarian (HU), Irish (GA), Italian (IT), Latvian (LV), Lithuanian (LT), Maltese (MT), Polish (PL), Portuguese (PT), Romanian (RO), Slovak (SK), Slovenian (SL), Spanish (ES), Swedish (SV), Mongolian (MN) No 1–2 European languages 100% Native Support (24/24)
3. Ease of Use & Autonomous Setup
Setup Velocity & Onboarding Time required to index website and generate a working agent Days of rule configuration Manual URL entry (capped at 20–50) 10s Scan + 5-min Crawler
Staging Preview Sandbox (*.preview.letschat.gg) Dedicated sandbox subdomains to safely test crawled knowledge, prompt changes, and agent personas before production deployment No (Direct live production testing; risks customer disruption) No dedicated sandbox (Paid staging add-on only) Included (*.preview.letschat.gg isolated sandbox on paid plans)
Source-Grounded Answers with Citations Clickable source badges directly referencing verified documentation URLs Rigid scripts Text summaries (no source links) Verified Citations
4. Pricing & Total Cost of Ownership (USD)
Free Evaluation Plan ($0 Forever) 1 verified domain, 10 conversations/mo, 0 MB knowledge storage, no credit card required No Free Plan 14-Day Trial Only Free Forever ($0)
Starter / Solo Tier (Annual Rate) Entry plan for small businesses & website customer service $40–$80 USD / mo $29 USD / mo ($37/mo monthly) $21.75 USD / mo Save $87/yr
Growth / Team Tier (Annual Rate) Active sales qualification, CRM sync, and multi-origin routing $150–$300 USD / mo $119 USD / mo ($149/mo monthly) $74.25 USD / mo Save 25% ($297/yr)
Agency & Enterprise Solutions Master multi-tenant dashboard, pooled quotas, white-labeling, BYOAI & custom SLA Custom / Contact Sales $499+ / mo Custom
Annual Subscription Discount Savings when opting for annual billing commitment 10%–15% 20% Discount 25% Discount
Usage & Conversation Quotas 30-day billing predictability with transparent conversation allowances and overage blocks Per-agent seat charges Strict 200 credits ($5/100 top-up) 10 (Free) / 60 (Starter) / 90 (Growth) / 900+ Pooled (Agency) / Unlimited (Enterprise)
Knowledge Base File Storage Dedicated storage for PDF, DOCX, XLSX, MD, and TXT documents Add-on storage charges Limited file uploads 10 MB on Starter, 25 MB on Growth (250 MB Pooled on Agency, Custom/TB on Enterprise)

*Market comparison based on publicly documented feature sets and standard architectural baselines of leading embed widgets as of Q1 2026. Specific vendor implementations may vary.

Pricing Plans

Start with a private preview. Upgrade when your agent starts working.

1 Plan = 1 Verified Domain & 1 AI Agent (Single-Site Plans)

All subscription pricing is in USD and can be paid in certain local currencies. Monthly quotas operate on a 30-day recurring cycle. Annual plans operate for 360 calendar days billed upfront, saving 25% on all paid tiers. Single-site plans (Free, Starter, Growth) cover 1 verified website each, while the Agency Plan starts from 10 client websites with pooled quotas.

Free

Evaluate Let’s Chat on 1 verified website.

$0 USD / 30-days
Free forever evaluation
  • • 1 verified domain & 1 AI agent
  • • Full website content indexing
  • • Grounded answers with citations
  • • 10 chat conversations / 30-days
  • • Let's Chat Agent Branding
  • • Browser-based preview simulator (Public crawl evaluation only)
Start Free

Starter

Ideal for customer support.

$29 USD / 30-days
Billed every 30 days ($29 USD)
$21.75 USD / mo
Billed $261 USD/year (equivalent to $21.75/month) $348 Save $87 vs 12 monthly cycles
  • Everything in Free, plus:
  • • 60 chat conversations / 30-days
  • • Overage: US$6 / block of 30 conversations
  • • Custom branding
  • • Daily automated sync with manual re-indexing
  • • 10 MB knowledge base storage
  • • 1 Dedicated staging subdomain (*.preview.letschat.gg)
  • • External scheduling link (Calendly, Cal.com URL)
  • • Email notifications
Choose Starter
POPULAR

Growth

For active sales and support teams.

$99 USD / 30-days
Billed every 30 days ($99 USD)
$74.25 USD / mo
Billed $891 USD/yr $1,188 Save $297
  • Everything in Starter, plus:
  • • 90 chat conversations / 30-days
  • • Overage: US$12 / block of 30 conversations
  • • 25 MB knowledge base storage
  • • Native 2-way Calendar Integration (Microsoft 365 & Google Workspace API slot sync)
  • • 1 Dedicated staging subdomain (*.preview.letschat.gg)
  • • Advanced lead qualification
  • • CRM integrations
  • • Custom workflows
  • • Human routing
  • • Conversion analytics
Choose Growth
AGENCY PARTNER

Agency

For digital agencies managing multiple client websites, CRM, and SEO assets.

Custom
  • Start with 10x Growth Bundle + Agency Platform:
  • • Master Multi-Tenant Agency Dashboard
  • • Full White-Labeling & Custom Domain
  • • Pooled Client Quotas (900 pooled chat conversations)
  • • Independent Multi-CRM Routing
  • • Client Role-Based Access Control
  • • White-Label Performance Reports
  • • Priority Agency Partner Program
  • • BYOAI (Bring Your Own AI LLM) Option
  • and more...
ENTERPRISE

Enterprise

For high-volume corporations, financial institutions, and regulated enterprises.

Custom
  • Governance & Dedicated Scale:
  • • Unlimited Chat Conversations
  • • Custom Knowledge Base Storage
  • • Enterprise Single Sign-On (SSO)
  • • Immutable Security Audit Trails
  • • Custom Deployment Options
  • • Enterprise SLA & Escalation
  • • BYOAI (Bring Your Own AI LLM) Option
  • and more...
FAQ

Frequently asked questions about Let’s Chat

Get direct answers about website training, domain verification, agent authentication, and human handoff.

General 1. What is Let’s Chat?
Let’s Chat is an AI website chatbot and customer-automation SaaS platform. It turns approved website content into an AI revenue and customer-resolution agent that can answer questions, qualify leads, book meetings, create support requests and escalate conversations to humans.
General 2. How is Let’s Chat different from a basic website chatbot?
Let’s Chat is designed to complete customer outcomes rather than only generate replies. It combines source-grounded answers, lead qualification, appointment booking, approved actions, human handoff, domain ownership verification and authenticated website deployment.
General 3. What is an AI revenue and customer-resolution agent?
An AI revenue and customer-resolution agent is a customer-facing system that helps visitors find answers, select products or services, complete sales steps and resolve common enquiries. It can also bring in a human when the conversation is sensitive, complex or outside its authority.
General 4. Do I need a developer to install Let’s Chat?
Most customers should be able to install Let’s Chat using a short versioned script or supported website-platform instructions. A developer may be helpful for strict Content Security Policy environments, custom integrations or advanced action workflows.
General 5. What is the Staging Preview Sandbox and which plans include it?
The Staging Preview Sandbox provides an isolated, dedicated subdomain (*.preview.letschat.gg) where you can safely test crawled website knowledge, prompt changes, and workflows before deploying to your live production website. Starter and Growth plans include 1 dedicated staging subdomain, while Agency and Enterprise plans offer custom multi-domain and dedicated VPC sandbox arrangements. Free plans include a browser-based evaluation simulator on your live website—upgrade to Starter or Growth to unlock your isolated staging preview subdomain.
General 6. Which languages are supported by the Let's Chat chatbot agent and administration portal?
Let's Chat provides comprehensive multilingual capabilities across 49 global and regional languages. The administration portal and chat widget UI are natively localized in 49 languages with right-to-left (RTL) script support. Our 3-stage conversational decision pipeline (GLiNER 2.5 Multi-Decide and Laya Multilingual) powers intent recognition, entity extraction, and source-grounded RAG synthesis across global and regional Asian languages including English, Chinese, Malay, Indonesian, Thai, Vietnamese, Japanese, Korean, Tagalog, Hindi, Arabic, and more. Audio/voice interaction is available on custom enterprise arrangements.
AI Grounded Truth 7. How does Let’s Chat learn from my website?
After you verify the domain, Let’s Chat crawls the website pages you permit. It extracts and structures relevant information such as products, services, pricing, frequently asked questions, policies and support content for retrieval during customer conversations.
AI Grounded Truth 8. Will Let’s Chat make up answers?
Let’s Chat is designed to answer from approved knowledge sources. When it cannot find sufficient supporting information, it can state that the answer cannot be verified, ask a clarifying question or offer human assistance.
AI Grounded Truth 9. Can the chatbot show where an answer came from?
Yes. Let’s Chat can display or retain links to the website page, document or approved source supporting an answer, depending on the customer’s configuration.
Security 10. Why do I need to verify my website domain?
Domain verification confirms that you have administrative authority over the website. This helps prevent unauthorised users from creating, indexing or publishing an official-looking agent for a website they do not control.
Security 11. How does DNS domain verification work?
Let’s Chat gives you a unique TXT record to add through your DNS provider. The platform queries the DNS record, verifies the unique token and then binds the verified domain to your workspace.
Security 12. Can I remove the DNS TXT record after verification?
Initial domain verification is performed using a unique DNS TXT record. Once verified, domain attestation remains active with continuous periodic background checks (re-verification cycle every 30 days, or a 72-hour grace period if the DNS record is temporarily unreachable). For permanent zero-trust attestation and to avoid automated re-verification prompts, we recommend keeping the DNS TXT record published.
Security 13. Can someone copy my chatbot code to another website?
They may be able to see or copy the public installation snippet, but the snippet alone does not authorise the agent. Let’s Chat checks the website origin and issues a signed runtime credential only for approved deployments on verified domains.
Security 14. How does the agent authenticate itself?
The Let’s Chat agent uses a signed deployment certificate and a short-lived runtime token. These credentials bind the active session to a specific workspace, agent, verified domain, approved website origin, configuration version and permission set.
Security 15. How does my website know that the Let’s Chat agent is authentic?
Your website can load a versioned Let’s Chat script over HTTPS and optionally validate it using a published Subresource Integrity hash. The deployment can also use signed configuration information and a restricted Content Security Policy.
Security 16. What happens if the chatbot is installed on an unapproved website?
The agent will not receive valid runtime authority. It should not initialise, retrieve customer knowledge or execute actions, and the failed origin check can be recorded as a security event.
Revenue & Bookings 17. Can Let’s Chat qualify sales leads?
Yes. Let’s Chat can collect information such as business requirements, company size, existing solution, budget range, purchasing timeline, location and preferred next step.
Revenue & Bookings 18. Can Let’s Chat book meetings via Calendar Integration?
Yes. Available for Growth and higher subscription plans (Growth, Agency, and Enterprise), Let’s Chat integrates natively with Microsoft 365 (via Microsoft Graph) and Google Workspace (via Google Calendar API v3). The AI chatbot checks live available slots against your custom operating hours, verifies visitor emails with a 10-minute numeric TOTP, and automatically books confirmed meetings with Microsoft Teams or Google Meet video links and reminders. Starter plans support external appointment booking redirection (Calendly or Cal.com scheduling URLs).
Revenue & Bookings 19. Which subscription plans include Calendar Integration and how does it work?
Native two-way Calendar Integration is exclusively available for Growth and higher subscription plans (Growth, Agency, and Enterprise). It connects directly to Microsoft 365 (via Microsoft Graph) and Google Workspace (via Google Calendar API v3). Customers configure custom calendar names, weekly availability windows, and meeting durations (30 min, 45 min, or 1 hour) with automated CRUD testing. Starter plans provide direct external scheduling links (Calendly, Cal.com, or Google Calendar booking URLs).
Revenue & Bookings 20. Which local currencies are supported for subscription billing and Stripe checkout?
Let's Chat supports over 40 presentment currencies with real-time conversion through Stripe Adaptive Pricing. Supported local billing currencies include USD, EUR, GBP, AUD, CAD, SGD, MYR, IDR, THB, VND, PHP, JPY, KRW, CNY, HKD, TWD, INR, KHR, LAK, MMK, BHD (Bahrain), KWD (Kuwait), OMR (Oman), QAR (Qatar), SAR (Saudi Arabia), AED (UAE), ILS (Israel), JOD (Jordan), LBP (Lebanon), TRY (Turkey), EGP (Egypt), CZK (Czechia), DKK (Denmark), HUF (Hungary), PLN (Poland), RON (Romania), SEK (Sweden), MNT (Mongolia), MOP (Macau), BND (Brunei), AFN (Afghanistan), BDT (Bangladesh), MVR (Maldives), NPR (Nepal), PKR (Pakistan), and LKR (Sri Lanka). Note that restricted or embargoed currencies such as Iraqi Dinar (IQD), Syrian Pound (SYP), and Bhutanese Ngultrum (BTN) are excluded per international payment processing standards.
Revenue & Bookings 21. How does conversation usage billing, monthly resets, overage rounding, and spending authorization work?
A conversation is counted as an initiated visitor chat session with your AI agent during the 30-day billing cycle. Quotas operate on a strict 30-day recurring cycle from subscription activation and automatically reset to zero at the start of each period (unused allowances do not roll over). The Free Plan has a hard stop at 10 conversations. For Starter (60 conversations) and Growth (90 conversations) plans, volume exceeding monthly allowances is rounded up and billed in predictable blocks of 30 conversations (US$6/block on Starter, US$12/block on Growth, or local currency equivalent). Subscribers can configure conversation overage spending authorization in portal -> plans & configurations settings to prevent unexpected charges. Conversation overage is disabled by default. Single-site plans (Free, Starter, Growth) cover 1 verified website each, while the Agency Plan starts from 10 client websites with 900 pooled chat conversations. Annual plans operate for 360 calendar days billed upfront (equivalent to 12 monthly 30-day cycles with 25% discount), with conversation quotas refreshing automatically every 30 days throughout the 360-day period.
Human Escalation 22. Can customers speak to a real person?
Yes. Visitors can request human assistance, and the agent can also escalate automatically based on low confidence, negative sentiment, repeated failure, high-value sales intent, sensitive topics or configured business rules.
Human Escalation 23. What information does the human agent receive?
The human agent can receive the conversation transcript, customer details, issue category, urgency, steps already attempted, relevant sources and an AI-generated summary. This reduces the need for the customer to repeat the entire conversation.
Agency & Enterprise 24. How does the Agency Plan work for digital marketing and web agencies?
The Agency Plan provides a unified Master Multi-Tenant Agency Dashboard where agencies can manage all client AI agents in one place. It includes 10 Annual Growth Plans bundled with a monthly platform fee (enjoying 25% annual discount), pooled quotas (900+ conversations and 250 MB document storage across clients), full white-labeling with custom CNAME domains, independent multi-CRM routing, and 15 team accounts with Client Role-Based Access Control (Agency Admin, Account Manager, and Client View-Only).
Agency & Enterprise 25. What capabilities and compliance guarantees are included in the Enterprise Plan?
The Enterprise Plan is tailored for high-volume, regulated organizations. It features unlimited monthly chat conversations, custom knowledge base storage, Enterprise Single Sign-On (SAML 2.0, Okta, Azure AD) with SCIM provisioning, immutable audit trails, dedicated or customer-provided infrastructure, and an enterprise SLA with 99.99% uptime and <1-hour critical response escalation.
Agency & Enterprise 26. Can Agency and Enterprise subscribers Bring Their Own AI LLM (BYOAI)?
Yes. Both Agency and Enterprise tiers offer Bring Your Own AI (BYOAI) support conforming to industry-standard OpenAI (/v1/chat/completions) and Anthropic (/v1/messages) API specifications. Clients and agencies can plug in their own API keys, proxy gateways, Azure OpenAI instances, or private self-hosted models (such as Ollama or vLLM), ensuring zero vendor lock-in, data sovereignty, and custom model control.

Your next customer may already be on your website

Do not make them search another page. Do not make them wait for a reply. Do not send them into another generic contact form. Give them a direct path:

Question Verified Answer Approved Action Customer Outcome

Turn your verified website into an AI revenue and customer-resolution agent.

Domain verification is required before production publication. Review and approve the agent before it goes live.