Skip to content

Customer support · Built MVP

Approved knowledge. A shared inbox. A human in control.

A support workspace combining website conversations, source-backed knowledge and a visible human handoff.

THE WORKFLOW

A clearer way to handle the work.

A useful support assistant needs more than a generated answer. Staff need context, approved information and a clear way to take over.

The selected Support OS implementation has local persistence and recorded desktop/mobile workflow checks. Its messaging/email adapters remain sandbox implementations.

What the foundation demonstrates

  • Shared inbox with customer context, staff replies and notes
  • Approved, versioned knowledge with source citations
  • Website widget with bounded visitor sessions
  • Human takeover, follow-up queue and AI execution traces

THE PROCESS

The core journey

Illustrative workflow. The client pilot defines the actual tools, permissions and acceptance criteria.

  1. 01

    Approve the knowledge

    Reviewed within the agreed pilot scope.

  2. 02

    Receive a website question

    Reviewed within the agreed pilot scope.

  3. 03

    Answer with sources or hand over

    Reviewed within the agreed pilot scope.

  4. 04

    Review follow-up and usage

    Reviewed within the agreed pilot scope.

SCOPE & READINESS

Know the boundaries before the build.

We review the foundation against your environment and agree any activation work before operational use.

  • Live WhatsApp and email delivery are not established in this foundation
  • Provider usage, channel activation and ongoing content operations are separate
  • No autonomous resolution, uptime or account-verification guarantee

PRICING

A commercial model that fits the stage.

Planning proposal in EUR, excluding taxes, hosting, software and AI/provider usage. The pilot budget assumes one bounded workflow; readiness work, integrations and any code licensing are confirmed in a written quote. Optional care is proposed for up to two hours of scheduled maintenance per month, without an implied SLA.

Proposed budget

Scoped pilot

Assisted pilot / custom adaptation, with optional scoped maintenance after acceptance.

€3000/pilot
  • One workspace and one website-support use case
  • A bounded approved knowledge set
  • Human takeover and failure-state acceptance tests
  • Usage baseline and operator handover
Optional · proposed

Ongoing care

Optional maintenance after acceptance. Coverage and hours are agreed separately.

€250/month
  • Up to two scheduled maintenance hours/month if selected
  • Agreed review and maintenance backlog
  • Provider, hosting and software costs separate
  • No unlimited changes or implied uptime SLA
Custom scope

Expanded rollout

Additional locations, integrations, roles or workflows require their own scope.

Custom
  • Discovery and readiness review
  • Phased implementation milestones
  • Explicit access and ownership agreement
  • Acceptance, release and handover plan

Questions about BrainGlow Support OS

YOUR NEXT ADVANTAGE

Explore BrainGlow Support OS for your team.

Share the workflow, existing software and the result you need. We will review fit before recommending a paid engagement.