Phone + Website Agent

    One intake assistant across phone and website

    A shared AI assistant for callers and website visitors. Not a generic chatbot: one intake logic, channel-specific behavior, and a clean handoff into your CRM, inbox, or callback queue.

    or email max@vasthavm.com

    Target customer

    Trades, restaurants, hospitality, clinics, local service businesses, and sales-led SMBs that get enquiries through both phone and website and need one intake system.

    Pricing indication

    35,000-95,000 SEK ex VAT + 3,500-8,500 SEK/month baseline

    The bundle setup depends on channels, scenarios, CRM depth, and handoff rules. Website-only add-ons can start around 12,500-35,000 SEK ex VAT when the phone agent already exists. Monthly baseline covers hosting, monitoring, small adjustments, and operating support; usage and provider pass-through costs stay separate.

    Pain points

    • Phone and web enquiries land in different places
    • Website chat becomes a dead-end widget instead of a real handoff
    • Staff ask the same qualifying questions across channels
    • No single view of what the customer asked for

    What Max can build

    • Answer phone calls with a voice agent
    • Run website intake through a web assistant or embedded agent
    • Reuse the same business context and qualification logic
    • Adapt behavior by channel: spoken conversation on phone, concise forms/chat on web
    • Create one structured handoff into CRM, inbox, or callback queue

    Deliverables

    • Phone agent setup and website assistant setup
    • Shared business context and qualification schema
    • Channel-specific scripts and escalation rules
    • CRM/inbox handoff fields
    • Runbook for routing, fallback, provider costs, and ownership

    Process

    • Define the shared intake model
    • Build phone flow and website flow separately
    • Test channel-specific scenarios
    • Connect handoff and callback logic
    • Launch with monitoring and tuning window

    Shared intake

    Same assistant logic. Different channel behavior.

    Phone callers and website visitors should not be forced through the same exact interaction. The reusable part is the business context, qualifying questions, escalation rules, and handoff schema.

    Phone caller flow

    Natural conversation, interruption handling, confirmation of contact details, and transfer/callback options.

    Website visitor flow

    Shorter prompts, visible options, form-like capture when useful, and fewer spoken confirmations.

    Shared handoff schema

    Intent, urgency, contact details, source, transcript/summary, and next action land in one place.

    No fake continuity

    Cross-channel memory is implemented deliberately; it is not assumed just because both channels use AI.

    Demo examples

    How the value shows up in real calls.

    Website visitor flow

    A visitor lands after hours and wants to know whether you can help with a specific job.

    • Asks the same qualifying questions your team needs anyway
    • Captures contact details and preferred next step
    • Routes qualified requests to CRM or callback queue

    Escalation: Human review for unclear scope, urgent requests, sensitive details, or visitor preference.

    After the call: Lead source, request type, qualification answers, urgency, contact details, and recommended follow-up.

    Phone caller flow

    A caller rings while the team is busy and would otherwise hit voicemail.

    • Answers naturally and confirms caller details
    • Captures job, booking, or support context
    • Transfers, schedules callback, or logs the request

    Escalation: Transfer or callback when the caller asks, confidence is low, or escalation rules trigger.

    After the call: Call summary and transcript link attached to the same CRM or inbox flow as website enquiries.

    FAQ

    Is this just a chatbot plus a phone bot?+
    No. The point is one shared intake system. Phone and website behavior differ, but the qualifying logic and handoff structure should match.
    Can it reuse the same agent context?+
    Often yes, but channel behavior still needs separate scripts, prompts, and testing. Spoken calls and web intake fail in different ways.
    Can visitors continue a phone conversation on the website?+
    Only if that continuity is implemented deliberately with identity, consent, and storage. I do not sell that as magic default behavior.
    What does the monthly baseline cover?+
    Monitoring, hosting/runtime support, small scenario adjustments, and operating support. Usage and telephony/provider costs stay separate.
    How is GDPR and security handled?+
    The audit identifies personal data, processors, access patterns, retention, and model-provider choices before build. Sensitive flows get least-privilege access and human approval where needed.
    When should we not use an AI agent?+
    Do not use an agent when deterministic rules are enough, the data is too poor to evaluate, the action is high risk without approval, or nobody can own the process after launch.

    Related practices

    AI Phone Agent
    AI Agents
    Lead-to-CRM Capture

    Cookies. Privacy