Qualified leads before the first call. Without hiring a sales team.

Set a useful boundary around scope

Describe each service with its deliverables, typical starting point, dependencies, and exclusions. For a website project, explain whether copywriting, migration, analytics, or ongoing support is included. Do not turn a broad phrase like “full-service” into an implied promise to handle unlisted work.

On Starter and Pro, a quote request form can ask about project type, target launch window, current platform, and the page or system involved. Let a strategist review the answers; MivoChat does not calculate a fee or decide whether the agency has capacity.

Connect portfolio proof to the prospect’s problem

Group case studies by the work they demonstrate: a migration, a booking flow, a brand refresh, or a conversion experiment. Include the client-approved context and outcome, and avoid implying that every project receives the same result. A visitor who asks for comparable work can be pointed to the closest relevant example.

Quick replies such as “See ecommerce work,” “Ask about a redesign,” and “Request a project estimate” keep the first exchange focused. If the visitor needs a strategic discussion, collect contact details and hand the conversation to the partner or lead assigned to that service.

Make retainers and commercial terms easy to compare

If retainers are offered, publish what the monthly scope covers, how requests are prioritized, whether unused hours roll over, the minimum term, and how notice works. If every engagement is bespoke, say which factors shape a proposal and what information the team needs before quoting.

Keep project minimums and price ranges current if you publish them. Explain whether a range excludes taxes, third-party tools, or production costs, and route negotiation or procurement questions to a person rather than implying a discount is approved.

Route sales conversations to someone with context

Choose a handoff owner by service line or account type. The person should receive the visitor’s page, requested service, timeline, and any consented contact details, then decide whether to continue in the web inbox or connected Telegram group.

Use Insights to find repeated questions about scope, portfolio fit, or retainer terms. A cluster often points to a missing case study or an unclear service page; improving that source reduces friction for both visitors and the sales team.

An agency can define a lightweight qualification route without turning the chat into a sales form that asks for a full brief. A useful first pass might capture the service line, current platform, approximate timing, and a business email. The project lead can then decide whether to request analytics access, schedule a scoping call, or decline work outside the studio's expertise. Publish retainer inclusions and notice rules in a stable page, and have the account owner review it whenever packaging changes.

When a request is clearly outside scope, offer a courteous response based on the agency’s published service boundaries and let a partner review any unusual case. For a qualified enquiry, agree who sends the discovery-call link and who follows up if the visitor does not choose a time. This small ownership rule prevents promising a proposal that has no project lead or capacity behind it.

Example conversation: Harbor and Pine Studio (fictional)

Visitor: “Do you do store migration work for small stores?” Chat: “Yes, that is one of our listed services. The case study on our work page covers a similar project. Scope depends on the platform and integrations, so a strategist will confirm after a short brief.”

Visitor: “Can you guarantee more leads?” Chat: “I can’t guarantee results. The case studies show the outcomes each client approved for publication. If you share your goals and current analytics, a strategist can explain what we would test.”

What to hand off to the account owner

Route these to a person who can make the commercial decision:

• Negotiated pricing, custom retainers, or minimum-term changes.
• Work outside the published services, which needs a partner's review.
• Procurement, legal, NDA, or data-processing terms.
• Requests from existing clients, which belong with their account owner rather than a new-enquiry queue.

Sample knowledge pages to write first

Write the scope pages before the case studies, because scope questions decide whether a prospect is a fit.

• Each service with its deliverables, dependencies, and exclusions.
• Case studies grouped by problem: migration, booking flow, brand refresh, or conversion test.
• Retainer inclusions, request process, and notice rules.
• What a published price range excludes, such as tax, third-party tools, or production.