Elevated AI Consulting
Website assistant implementation

Help visitors get an answer and make an inquiry.

Add an assistant to an existing compatible website. It uses approved content, provides a fallback when it cannot answer and sends inquiry details to a destination you choose.

EAC will confirm the scope, price, payment terms and availability directly.

Who it is for

A business with an existing website, approved public information and an established inquiry destination.

  • 01One website assistant answers from approved content and captures inquiries for a defined follow-up destination.

What is included

A branded assistant, approved knowledge boundaries, an inquiry form, fallback contact route, test results and editable configuration with handoff notes.

  • 01Branded embedded assistant and approved knowledge boundaries
  • 02Fallback contact route, input limits and basic rate limiting
  • 03Knowledge, unsupported-question and lead-flow test report
  • 04Editable source/configuration, provider assumptions and setup/handoff notes
  • 0520-case report: 10 knowledge answers, five unsupported questions and five inquiry-flow cases; one 30-minute handoff

Scope and limits

One English-language assistant on one website. Up to five approved public pages or text documents, totaling no more than 5,000 words. One inquiry flow with up to four fields and one existing API-accessible destination.

  • One English-language assistant on one compatible website
  • Up to five approved public pages/text documents, no more than 5,000 words
  • One inquiry flow with up to four fields and one existing API-accessible lead destination

What to prepare

Share the website platform, approved information, representative questions, expected answers and fallback contact route. Confirm the inquiry fields, required disclosures and destination.

  • Website/platform and authority to install
  • Approved content and representative questions with expected answers
  • Brand/tone and fallback contact route
  • Approved lead fields, consent/disclosure and destination documentation
  • Client-owned accounts, project-scoped access and permission to process supplied content
  • 10 representative knowledge questions with expected answers

How we review the work

The 20-case test report covers knowledge answers, unsupported questions and inquiry handling. Delivery and failure behavior are checked against the written expectations for your project.

  • 01Loads in agreed desktop/mobile checks
  • 02Agreed knowledge-answer rubric and unsupported-question fallback checks pass
  • 03Lead validation, delivery and failure-handling checks meet written expectations
  • 04No browser-exposed credentials; instructions and limitations delivered
  • 05At least 9 of 10 agreed knowledge answers meet the handoff rubric; all five unsupported-question and five inquiry-flow cases meet written expectations

Outside the scope

Appointment booking, payments, authenticated account lookup, voice, WhatsApp, bulk outreach and sensitive-data workflows are outside the base engagement.

  • New website/redesign or authenticated account/order lookup
  • Appointment scheduling, voice/WhatsApp or bulk outreach
  • CRM pipeline design, multilingual content, new admin dashboard or sensitive-data workflows
Interactive example

A useful assistant knows when to stop.

Try three synthetic inputs. This local example uses fixed rules to illustrate validation, boundaries and human review.

SAMPLE WORKSPACE LOCAL ONLY
01 / Sample input
Request
Please send details about a workflow pilot.
Contact
example@example.com
02 / Review point

Waiting for a sample

Choose an input and run it to see the decision and the reason behind it.

Illustrative demo • Synthetic data • No AI call, saved inquiry or live integration. Project behavior is tested against an agreed scope.

Delivery steps

01

Approve the information

Agree approved content, questions and lead fields

02

Build the assistant and form

Implement the assistant and bounded inquiry flow

03

Test answers and inquiry handling

Test knowledge, fallback and delivery behavior

04

Hand over the configuration and operating notes

Hand over editable configuration and operating notes

Terms and support

EAC confirms scope, price and payment terms in writing after inquiry. Billing is handled directly through EAC.

EAC confirms availability, timing and required inputs in writing before work begins.

One content, tone or behavior revision and one follow-up clarification round requested within seven calendar days. Ongoing maintenance is separate.

Client-owned accounts, hosting, subscriptions and software usage are separately funded.

Questions

How do I get started?

Send the project goal, current tools and the relevant details through the inquiry form. We’ll assess fit and confirm scope, price and availability before work begins. An inquiry does not purchase a service or reserve a session.

How are costs and payment handled?

EAC confirms the project price and payment terms in writing. Software subscriptions, hosting and usage charges are separate unless expressly included in the proposal.

How is inquiry capture checked?

We agree on the destination and expected validation, delivery and failure behavior, then test them. The demonstration on EAC’s website is a separate example, not proof of your integration.

Share the task, current tools and the result you want. We’ll review the request and discuss the scope.

Request a proposal

A clear scope and practical review

EAC confirms the task, required access and review criteria before work begins. Public demonstrations use EAC-owned or synthetic examples. Each engagement sets out its deliverables, limits and handoff.