Start with the conversation you keep missing

Look at recent enquiries before choosing a tool. Which questions arrive repeatedly? Which need a quick explanation? Which get passed between people? A useful first workflow might help a shopper choose a product, explain a SaaS plan or collect the details an architecture practice needs before a consultation.

The assistant needs reliable answers and a clear next action. If you rarely receive enquiries, first investigate visibility and the offer itself. An agent can help existing visitors get answers; installing one does not create demand.

Website voice, chat or a telephone line?

These are different entry points. Website chat lets someone read and reply at their own pace. Website voice supports a spoken conversation through their browser. A telephone agent answers calls through a connected number and requires its own telephony configuration.

I start with the channel customers already use. For my website starter, voice and chat are included. A phone line, an existing CRM or a more complex workflow is scoped separately. Your proposal should identify every connection and who owns each account.

Define the useful handoff

Write down what the team needs at the end of a conversation. For a service business, that might be the customer’s goal, location, timing and preferred contact method. For software, it might be team size, the workflow they need and the question that needs a specialist.

  1. Answer: use approved product, service and policy information.
  2. Clarify: ask only for missing details that change the recommendation.
  3. Confirm: check contact or appointment details before saving an action.
  4. Hand over: make the context available to the right person.

For bookings, a real calendar must be connected and tested. A conversation that says “you’re booked” without creating a verified appointment is an incomplete workflow.

Test the awkward moments

Try a vague question, an interrupted sentence, an unavailable time and an answer that is missing from the knowledge base. Then test silence, a muted microphone and a blocked speaker. The assistant should ask a focused clarification or offer another route without repeatedly talking over someone.

Decide when a person takes over. Complaints, unusual exceptions and unsupported requests need an agreed response. Keep access limited to the information required for the job, and explain how conversations are processed and stored.

Budget for setup and operation

My focused website starter begins at $1,495 USD one-time: one agreed journey, approved knowledge, structured lead capture, one calendar connection, testing and handover. Voice, API and hosting usage are additional. Existing CRM integrations, phone lines and custom workflows are quoted separately.

Before committing, ask for a usage estimate based on expected conversation volume and length. Also decide who reviews unanswered questions and keeps policies current. An improvement review for an existing assistant is included within the defined Growth monthly scope; the initial build is separate.

Measure whether it is doing the job

Start with answer accuracy, useful enquiries, completed handoffs and correctly confirmed bookings. Review a sample of conversations with appropriate permission. An increase in conversations is only useful when the team can act on them.

Start with a bounded job and a measurable definition of success. Use observed conversations to decide which responsibilities can be automated and which need your team, then expand from what you learn.