YANDEE SUPPORT / PRICING

A clear scope.
A clear quote.

Start with the support work you need to improve. Build a core workspace, add the right workflows, and agree the cost before your pilot begins.

Tailored quotes · Telegram-first scoping · Human review

YOUR SERVICE, IN LAYERS
03
Your connectionsCustom scope when needed
02
Your workflowsDefined tasks and evidence
01
Your foundationKnowledge, inbox and people

One agreed scope. A visible next step.

START SMALL. ADD WHAT MATTERS.

A foundation. Then the right extensions.

Core is the starting point. Specialist workflows and custom integrations extend it when your operating needs call for them.

THE FOUNDATION

Core pilot

Give your team a clear place to review the next conversation.

Quoted for your scope

Workspace, people, setup and usage agreed together.

  • Inbox and assisted draft review
  • Approved knowledge and source context
  • Team roles and human handover
  • Telegram-first connection planning
Scope the foundation

Assisted pilot. Your team reviews what is sent. Live setup is verified before launch.

OPTIONAL EXTENSION

Specialist workflows

Bring the right evidence into a specific, repeatable support task.

Quoted for your scope

Added to Core after the workflow is defined.

  • A clear task and permitted data source
  • Read-only lookups where supported
  • Evidence and a defined handover path
  • Case testing before rollout
Scope a workflow

Integration dependent. Backend compatibility and permissions are checked first.

OPTIONAL EXTENSION

Custom integration

Connect an operating requirement that needs its own implementation.

Quoted for your scope

A separately agreed build, connected to Core.

  • API and access feasibility review
  • Written implementation boundaries
  • Test cases and acceptance criteria
  • Hosting and maintenance scope
Discuss a connection

Scope and acceptance come before the build. Compatibility is never assumed.

ROOM TO ADAPT

Add to the scope, with the terms in view.

Quote these items separately when you need them. Amounts, units and service periods are agreed before activation.

More team members

Define who needs access and how seats are counted.

Usage allowance

Agree the billable unit, included usage and overage rules.

Additional workspaces

Scope each brand’s knowledge, channel and permitted team.

Backend connector

Assess the source, access, testing and ongoing upkeep.

Bank and slip verification remain planned capabilities, not ready-to-buy add-ons. Each needs separate scoping and integration validation before live use.

YOUR FIRST SCOPE

What does your next shift look like?

Give us a starting point for the conversation. This planner prepares a scope summary, not a price or a capacity commitment.

BEFORE YOU SAY YES

The details belong in the quote.

Agree on what you are buying and what happens next. Your written quote should make these items explicit.

  1. 01

    Setup and service period

    Onboarding, knowledge migration, launch requirements and the service dates.

  2. 02

    People and workspaces

    Seat definitions, team access, brands and channel scope.

  3. 03

    Usage and extra usage

    Billable unit, allowance, expiry or rollover, and any overage process.

  4. 04

    Infrastructure and integrations

    Hosting, model usage, connector setup and maintenance fees.

  5. 05

    Currency and payment

    Currency, applicable taxes, payment method and payment schedule.

  6. 06

    Acceptance and readiness

    Test cases, sign-off, support responsibilities and the conditions for going live.

PAYMENT, WITH THE SCOPE AGREED

Confirm the method before activation.

Available payment methods are confirmed in your quote. Crypto payments are under review; no wallet or live crypto checkout is offered here.

This is payment for Yandee’s support service. It does not collect or handle player deposits, withdrawals or gaming balances.

THE PRACTICAL QUESTIONS

Know what you’re agreeing to.

Why is pricing quote-based?

The pilot depends on your workspaces, team, knowledge, usage, hosting and integration needs. We agree the scope and commercial terms in writing before activation. No fixed public rates or included capacities are offered on this page.

What counts toward usage?

Your quote defines the billable unit and what is included. The planner asks for expected support cases to size the work; it is not a count of AI replies or a billing calculation. Human replies, customer messages and model usage must not be assumed to share one unit.

Does unused usage expire? What if we need more?

The quote must state the service period, any expiry or rollover, and how extra usage is approved and charged. There is no public top-up pack or automatic overage rate on this page.

Is setup included?

We list onboarding, knowledge preparation, hosting and connector work in the quote so you can see what is included and what is separate. Custom work has an agreed scope and acceptance criteria before implementation.

Can we manage several brands?

We scope a workspace for each brand, with its own knowledge and permitted team access. Count each person once in the planner, even if they need several workspaces. The final quote defines seat counting; a unified cross-brand customer inbox is a later capability.

Can we pay with crypto?

Crypto is under review. We have not activated a merchant wallet or checkout. The available provider, supported currencies, network, fees and payment terms must be confirmed before any payment instructions are issued.

Does a quote or payment make the service live?

No. The live channel, backend permissions, hosting, knowledge and handover flow still need to be connected and verified. The current product is an assisted workflow: your staff review drafts and decide what to send.

START WITH THE WORK

Bring your busiest shift.
We’ll map the first step.

Keep passwords, tokens and customer records out of email. We’ll agree a secure setup process.